diff options
| author | Brendan Abolivier <babolivier@matrix.org> | 2021-06-17 19:56:48 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-06-17 18:56:48 +0100 |
| commit | 08c84693227de9571412fa18a7d82818a370c655 (patch) | |
| tree | c9282621794ea74e2a5c764f444b70a48f26470f /INSTALL.md | |
| parent | Update MSC3083 support per changes in the MSC. (#10189) (diff) | |
| download | synapse-08c84693227de9571412fa18a7d82818a370c655.tar.xz | |
Remove support for ACME v1 (#10194)
Fixes #9778 ACME v1 has been fully decommissioned for existing installs on June 1st 2021(see https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430/27), so we can now safely remove it from Synapse.
Diffstat (limited to 'INSTALL.md')
| -rw-r--r-- | INSTALL.md | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/INSTALL.md b/INSTALL.md index 3c498edd29..b0697052c1 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -442,10 +442,7 @@ so, you will need to edit `homeserver.yaml`, as follows: - You will also need to uncomment the `tls_certificate_path` and `tls_private_key_path` lines under the `TLS` section. You will need to manage - provisioning of these certificates yourself — Synapse had built-in ACME - support, but the ACMEv1 protocol Synapse implements is deprecated, not - allowed by LetsEncrypt for new sites, and will break for existing sites in - late 2020. See [ACME.md](docs/ACME.md). + provisioning of these certificates yourself. If you are using your own certificate, be sure to use a `.pem` file that includes the full certificate chain including any intermediate certificates |