diff options
| author | anoadragon453 <anoadragon453@users.noreply.github.com> | 2021-07-15 11:48:16 +0000 |
|---|---|---|
| committer | anoadragon453 <anoadragon453@users.noreply.github.com> | 2021-07-15 11:48:16 +0000 |
| commit | fc24a06cadabef29bef17981c1da4487f764c172 (patch) | |
| tree | 4a797ca3dc0517064482e343a9b9472a34bedd50 /develop/federate.html | |
| parent | deploy: 5ecad4e7a57610baa55f64f1389b92d483716155 (diff) | |
| download | synapse-fc24a06cadabef29bef17981c1da4487f764c172.tar.xz | |
deploy: c1414550490355aa9c4e2bf80fa4d13bd06e28d1
Diffstat (limited to 'develop/federate.html')
| -rw-r--r-- | develop/federate.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/develop/federate.html b/develop/federate.html index 2527bb450b..2532944fd8 100644 --- a/develop/federate.html +++ b/develop/federate.html @@ -194,7 +194,7 @@ server (via port 8448). This is easy to set up and will work provided you set the <code>server_name</code> to match your machine's public DNS hostname.</p> <p>For this default configuration to work, you will need to listen for TLS connections on port 8448. The preferred way to do that is by using a -reverse proxy: see <a href="reverse_proxy.html">reverse_proxy.md</a> for instructions +reverse proxy: see <a href="reverse_proxy.html">the reverse proxy documentation</a> for instructions on how to correctly set one up.</p> <p>In some cases you might not want to run Synapse on the machine that has the <code>server_name</code> as its public DNS hostname, or you might want federation @@ -202,7 +202,7 @@ traffic to use a different port than 8448. For example, you might want to have your user names look like <code>@user:example.com</code>, but you want to run Synapse on <code>synapse.example.com</code> on port 443. This can be done using delegation, which allows an admin to control where federation traffic should -be sent. See <a href="delegate.html">delegate.md</a> for instructions on how to set this up.</p> +be sent. See <a href="delegate.html">the delegation documentation</a> for instructions on how to set this up.</p> <p>Once federation has been configured, you should be able to join a room over federation. A good place to start is <code>#synapse:matrix.org</code> - a room for Synapse admins.</p> @@ -218,8 +218,8 @@ servers in the room could not access yours. (Joining a room over federation is a complicated dance which requires connections in both directions).</p> <p>Another common problem is that people on other servers can't join rooms that you invite them to. This can be caused by an incorrectly-configured reverse -proxy: see <a href="reverse_proxy.html">reverse_proxy.md</a> for instructions on how to correctly -configure a reverse proxy.</p> +proxy: see <a href="reverse_proxy.html">the reverse proxy documentation</a> for instructions on how +to correctly configure a reverse proxy.</p> <h3 id="known-issues"><a class="header" href="#known-issues">Known issues</a></h3> <p><strong>HTTP <code>308 Permanent Redirect</code> redirects are not followed</strong>: Due to missing features in the HTTP library used by Synapse, 308 redirects are currently not followed by |