From b66f149e6b30051821c51e7c86c54b32ca654bfb Mon Sep 17 00:00:00 2001
From: babolivier <babolivier@users.noreply.github.com>
Date: Thu, 17 Jun 2021 17:57:10 +0000
Subject: deploy: 08c84693227de9571412fa18a7d82818a370c655

---
 develop/setup/installation.html | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

(limited to 'develop/setup/installation.html')

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
-- 
cgit 1.5.1