From f47c09ea6bdcf145f408f488a9a5a29fe53e702b Mon Sep 17 00:00:00 2001 From: MadLittleMods Date: Tue, 22 Jul 2025 15:36:23 +0000 Subject: [PATCH] deploy: 98f84256e9bea3e10191e52a9b274fe63b66ad43 --- develop/print.html | 44 +++++++++++++++++-- develop/schema/synapse-config.schema.json | 31 +++++++++++++ develop/searchindex.js | 2 +- develop/searchindex.json | 2 +- develop/setup/forward_proxy.html | 20 +++++++-- .../configuration/config_documentation.html | 24 ++++++++++ 6 files changed, 113 insertions(+), 10 deletions(-) diff --git a/develop/print.html b/develop/print.html index 4fe29e5f88..4f550c219f 100644 --- a/develop/print.html +++ b/develop/print.html @@ -1149,8 +1149,20 @@ this is necessary is in corporate environments behind a DMZ (demilitarized zone) Synapse supports routing outbound HTTP(S) requests via a proxy. Only HTTP(S) proxy is supported, not SOCKS proxy or anything else.

Configure

-

The http_proxy, https_proxy, no_proxy environment variables are used to -specify proxy settings. The environment variable is not case sensitive.

+

The proxy settings can be configured in the homeserver configuration file via +http_proxy, +https_proxy, and +no_proxy_hosts.

+

homeserver.yaml example:

+
http_proxy: http://USERNAME:PASSWORD@10.0.1.1:8080/
+https_proxy: http://USERNAME:PASSWORD@proxy.example.com:8080/
+no_proxy_hosts:
+  - master.hostname.example.com
+  - 10.1.0.0/16
+  - 172.30.0.0/16
+
+

The proxy settings can also be configured via the http_proxy, https_proxy, +no_proxy environment variables. The environment variable is not case sensitive.