diff options
author | babolivier <babolivier@users.noreply.github.com> | 2021-06-17 17:57:10 +0000 |
---|---|---|
committer | babolivier <babolivier@users.noreply.github.com> | 2021-06-17 17:57:10 +0000 |
commit | b66f149e6b30051821c51e7c86c54b32ca654bfb (patch) | |
tree | e48ffe62efec91acc451e9b4e037147ad268b5e8 /develop/setup | |
parent | deploy: 76f9c701c3920d83c0fe8f08b9197e2e92e12dad (diff) | |
download | synapse-b66f149e6b30051821c51e7c86c54b32ca654bfb.tar.xz |
deploy: 08c84693227de9571412fa18a7d82818a370c655
Diffstat (limited to 'develop/setup')
-rw-r--r-- | develop/setup/installation.html | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/develop/setup/installation.html b/develop/setup/installation.html index c17198d851..3d4be48ce1 100644 --- a/develop/setup/installation.html +++ b/develop/setup/installation.html @@ -524,10 +524,7 @@ each line). The relevant lines are like this:</li> <li> <p>You will also need to uncomment the <code>tls_certificate_path</code> and <code>tls_private_key_path</code> lines under the <code>TLS</code> 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 <a href="docs/ACME.html">ACME.md</a>.</p> +provisioning of these certificates yourself.</p> <p>If you are using your own certificate, be sure to use a <code>.pem</code> file that includes the full certificate chain including any intermediate certificates (for instance, if using certbot, use <code>fullchain.pem</code> as your certificate, not |