Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
synapse
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Timo Ley
synapse
Commits
95ab2eb4
Unverified
Commit
95ab2eb4
authored
5 years ago
by
Richard van der Hoff
Committed by
GitHub
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Fix notes about well-known and acme (#5357)
fixes #4951
parent
d53faa40
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
changelog.d/5357.doc
+1
-0
1 addition, 0 deletions
changelog.d/5357.doc
docs/MSC1711_certificates_FAQ.md
+5
-6
5 additions, 6 deletions
docs/MSC1711_certificates_FAQ.md
with
6 additions
and
6 deletions
changelog.d/5357.doc
0 → 100644
+
1
−
0
View file @
95ab2eb4
Fix notes about ACME in the MSC1711 faq.
This diff is collapsed.
Click to expand it.
docs/MSC1711_certificates_FAQ.md
+
5
−
6
View file @
95ab2eb4
...
...
@@ -145,12 +145,11 @@ You can do this with a `.well-known` file as follows:
1.
Keep the SRV record in place - it is needed for backwards compatibility
with Synapse 0.34 and earlier.
2.
Give synapse a certificate corresponding to the target domain
(
`customer.example.net`
in the above example). Currently Synapse's ACME
support
[
does not support
this
](
https://github.com/matrix-org/synapse/issues/4552
)
, so you will have
to acquire a certificate yourself and give it to Synapse via
`tls_certificate_path`
and
`tls_private_key_path`
.
2.
Give Synapse a certificate corresponding to the target domain
(
`customer.example.net`
in the above example). You can either use Synapse's
built-in
[
ACME support
](
./ACME.md
)
for this (via the
`domain`
parameter in
the
`acme`
section), or acquire a certificate yourself and give it to
Synapse via
`tls_certificate_path`
and
`tls_private_key_path`
.
3.
Restart Synapse to ensure the new certificate is loaded.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment