Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update MSC1711 FAQ to be explicit about well-known #4584

Merged
merged 4 commits into from Feb 7, 2019
Merged
Changes from 1 commit
Commits
File filter...
Filter file types
Jump to…
Jump to file or symbol
Failed to load files and symbols.
+2 −4
Diff settings

Always

Just for now

Prev

cleanups

  • Loading branch information...
richvdh committed Feb 7, 2019
commit 7cadc4c918c207a574ea15bd1e3793d8a48b7beb
@@ -112,7 +112,7 @@ _matrix._tcp.example.com. IN SRV 10 5 8000 customer.example.net.

In this situation, you have three choices for how to proceed:

#### Option 1: give Synapse (or a reverse-proxy) a certificate for your matrix domain
#### Option 1: give Synapse a certificate for your matrix domain

Synapse 1.0 will expect your server to present a TLS certificate for your
`server_name` (`example.com` in the above example). You can achieve this by
@@ -123,8 +123,7 @@ doing one of the following:
and `tls_private_key_path`, or:

* Use Synapse's [ACME support](./ACME.md), and forward port 80 on the
`server_name` domain to your Synapse instance, or:

`server_name` domain to your Synapse instance.

### Option 2: run Synapse behind a reverse proxy

@@ -133,7 +132,6 @@ your domain, you can simply route all traffic through the reverse proxy by
updating the SRV record appropriately (or removing it, if the proxy listens on
8448).


#### Option 3: add a .well-known file to delegate your matrix traffic

This will allow you to keep Synapse on a separate domain, without having to
ProTip! Use n and p to navigate between commits in a pull request.
You can’t perform that action at this time.