lovely-projects/synapse
lovely-projects/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2025-03-14 09:45:51 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge acb34314b9 into fda1ffe5b8

Browse source
This commit is contained in:
David von Oheimb 2025-03-11 10:35:22 +00:00 • committed by GitHub
commit 5f777021ea
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.rst
View file

@ -56,6 +56,8 @@ It is recommended to put a reverse proxy such as
`relayd <https://man.openbsd.org/relayd.8>`_ in front of Synapse. One advantage of
doing so is that it means that you can expose the default https port (443) to
Matrix clients without needing to run Synapse with root privileges.
Another important advantage is that such a reverse proxy is better suited for
handling TLS, in particular for managing the needed credentials (certificate etc.).
For information on configuring one, see `the reverse proxy docs
<https://element-hq.github.io/synapse/latest/reverse_proxy.html>`_.

5
docs/reverse_proxy.md
View file

@ -7,8 +7,9 @@ It is recommended to put a reverse proxy such as
[HAProxy](https://www.haproxy.org/) or
[relayd](https://man.openbsd.org/relayd.8) in front of Synapse. One advantage
of doing so is that it means that you can expose the default https port
(443) to Matrix clients without needing to run Synapse with root
privileges.
(443) to Matrix clients without needing to run Synapse with root privileges.
Another important advantage is that such a reverse proxy is better suited for
handling TLS, in particular for managing the needed credentials (certificate etc.).
You should configure your reverse proxy to forward requests to `/_matrix` or
`/_synapse/client` to Synapse, and have it set the `X-Forwarded-For` and