From b2984148ca2f704f6ba8713104f742c321929c3f Mon Sep 17 00:00:00 2001
From: Jorik Schellekens
@@ -24,26 +24,6 @@ export default ({ onClickACME, onClickTLS, onClickNoTLS }) =>
need a TLS cert. You can use ACME, provide your own certs, or let the reverse
proxy handle the TLS certs instead. (You can also not use TLS but that's not recommended)
- ACME is
- If you wish to use ACME you will need access to port 80 which usually requires
- root privileges. Do not run Synapse as root. Use a Reverse Proxy or Authbind
-
- If you have your own TLS certs for the domain you can specify a path
- to them or you can upload them for synapse to use.
- TLS
- ACME
-
- a super cool initiative a protocol that allows TLS
- certificates to be requested automagically. Synapse supports ACME by requesting
- certs from Let's Encrypt. This is the easiest way to manage your certs because
- once you set it up you don't need to manage it.
-
- Provide your own
-
-
ReverseProxy
@@ -67,7 +47,27 @@ export default ({ onClickACME, onClickTLS, onClickNoTLS }) =>
configuration templates later. Easy breasy.
- More information in the docs. + More information about Reverse Proxies in the docs. +
+
+ ACME is a super cool initiative a protocol that allows TLS
+ certificates to be requested automagically. Synapse supports ACME by requesting
+ certs from Let's Encrypt. This is the easiest way to manage your certs because
+ once you set it up you don't need to manage it.
+
+ If you wish to use ACME you will need access to port 80 which usually requires + root privileges. Do not run Synapse as root. Use a Reverse Proxy or Authbind +
++ If you have your own TLS certs for the domain we'll ask you for the path + to them or you can upload them for synapse to use.