From 442da5fbddb5acc243d8d25e97783dc0392005ef Mon Sep 17 00:00:00 2001
From: Jorik Schellekens
You will need access to {servername}'s domain zone DNS records. This method also requires the synapse install's server to provide @@ -73,7 +73,7 @@ export default ({ servername, skip, onClick }) => { again, we'll print the SRV record out for you later.)
{servername} provides the url
https://{servername}/.well-known/matrix/server which gives
diff --git a/synapse_topology/view/webui/js/components/ReverseProxy.jsx b/synapse_topology/view/webui/js/components/ReverseProxy.jsx
deleted file mode 100644
index ce8806fabb..0000000000
--- a/synapse_topology/view/webui/js/components/ReverseProxy.jsx
+++ /dev/null
@@ -1,38 +0,0 @@
-import React, { useState } from 'react';
-
-import ContentWrapper from '../containers/ContentWrapper';
-
-import {
- REVERSE_PROXY_TYPES
-} from '../actions/constants'
-
-
-export default ({ onClick }) => {
- const defaultValue = REVERSE_PROXY_TYPES.NGINX;
- const [reverseProxy, setReverseProxy] = useState(defaultValue);
-
- const onChange = event => {
- console.log("trigered")
- console.log(event.target)
- setReverseProxy(event.target.value);
- }
-
- return
- Please choose the reverse proxy you're using. This is just so we can provide
- you with a template later, if you already know how you're going to set yours
- up don't worry too much about this.
-
- I was going to make a TLS joke but it
- was making me insecure..
-
- TLS keeps the communication between homeservers secure. To enable TLS you'll
- need a TLS cert. You can use ACME, provide your own certs, or let the reverse
- proxy handle the TLS certs instead.
-
- It is a good idea to use Synapse behind a reverse proxy such as Apache, Caddy, HAProxy, or NGiNX.
-
- The main benefit to this is that the reverse proxy can listen on the privilaged port
- 443 (which clients like riot expect to connect to) on behalf of synapse. The incoming traffic
- is then forwarded to Synapse on a non privilaged port.
-
- If you choose to use a Reverse Proxy (good for you) we'll provide you with
- configuration templates later. Easy breasy.
-
- More information about Reverse Proxies in the docs.
-
- 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 we'll ask you for the path
- to them or you can upload them for synapse to use.
-
+ Synapse uses TLS to ensure communication between homeservers is
+ secure. To use TLS, you’ll need a TLS certificate. Synapse supports
+ ACME, providing your own certificates, or reverse proxy handling TLS
+ certificates.
+
+ It is recommended to run Synapse behind a reverse proxy such as Apache, Caddy, HAProxy, or NGiNX.
+
+ The main benefit to this is that the reverse proxy can listen on
+ the privileged port 443 (which clients like Riot expect to connect
+ to) on behalf of synapse. The incoming traffic is then forwarded
+ to Synapse on a non privileged port.
+
+ You need root to listen on ports 0 to 1024 inclusive and running
+ synapse with root privileges is strongly discouraged.
+ Reverse proxies are more secure, run with root and pass things on
+ like nobody's business.
+
+ (Note: you can also have synapse use a non privileged port by
+ using one of the delegation methods mentioned earlier.)
+
+ If you choose to use a Reverse Proxy we'll provide you with
+ configuration templates later.
+ More information about Reverse Proxies
+
+ in the docs.
+
+ Please choose the reverse proxy you're using. This is just so we can provide
+ you with a template later, if you already know how you're going to set yours
+ up don't worry too much about this.
+
+ ACME is a protocol that allows TLS certificates to be requested
+ automagically. Synapse supports ACME by requesting certs from
+ Let's Encrypt, which is one of the easiest ways to manage your
+ certificates.
+
+ 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
+
+ Specify a path to or upload TLS certs for the domain.
+ Please enter {certPathInvalid ? "a valid" : "the"} path to the cert Please enter {certKeyPathInvalid ? "a valid" : "the"} path to the cert's key Upload a cert file. Upload the cert's private key file.
- If you have a tls cert on your server you can provide a path to it here.
- The cert needs to be a `.pem` file that includes the
- full certificate chain including any intermediate certificates.
- Please enter {certPathInvalid ? "a valid" : "the"} path to the cert Please enter {certKeyPathInvalid ? "a valid" : "the"} path to the cert's key Upload a cert file. Upload the cert's private key file.Reverse Proxy
- TLS
-
- ReverseProxy
-
-
- You need root to listen on ports 0 to 1024 inclusive and
- running synapse with root privileges is strongly discouraged.
- Reverse proxies are more secure, run with root and pass things on like nobody's business.
-
- (Note: you can also have synapse use a non privilaged port
- by using one of the delegation methods mentioned earlier.)
-
- 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 TLS certs
-
- OR..
+ Upload a TLS cert
+ Testing the cert paths.
Uploading Certs
TLS Path
- OR..
- Upload a TLS cert
-