You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Description:
In a setup where there is the synapse server (machine B) behind a reverse proxy (machine A), the two being on two different machines, and the machine running synapse not having direct internet access (but only via proxy) it should be possible to proxy the federation connections.
Just as is done e.g. for notifications.
-- reverse proxy (machine A) -- synapse (machine B, access to internet only via proxy)
There was already an issue on this (#4198) although the implementation which resulted out of that (#6239) explicitly does not support proxy support for federation.
The text was updated successfully, but these errors were encountered:
Description:
In a setup where there is the synapse server (machine B) behind a reverse proxy (machine A), the two being on two different machines, and the machine running synapse not having direct internet access (but only via proxy) it should be possible to proxy the federation connections.
Just as is done e.g. for notifications.
-- reverse proxy (machine A) -- synapse (machine B, access to internet only via proxy)
There was already an issue on this (#4198) although the implementation which resulted out of that (#6239) explicitly does not support proxy support for federation.
The text was updated successfully, but these errors were encountered: