Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Fix notes about well-known and acme #5357

Merged
merged 3 commits into from
Jun 5, 2019
Merged

Fix notes about well-known and acme #5357

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b52f89f
Fix notes about well-known and acme
richvdh Jun 5, 2019
3c472eb
changelog
richvdh Jun 5, 2019
a3fdaa7
Update docs/MSC1711_certificates_FAQ.md
richvdh Jun 5, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/5357.doc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Fix notes about ACME in the MSC1711 faq.
9 changes: 4 additions & 5 deletions docs/MSC1711_certificates_FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,11 +146,10 @@ You can do this with a `.well-known` file as follows:
with Synapse 0.34 and earlier.

2. Give synapse a certificate corresponding to the target domain
richvdh marked this conversation as resolved.
Show resolved Hide resolved
(`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`.
(`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.

Expand Down