From 1f38e5a58919adb725d9e01f035a87e8f3568e1f Mon Sep 17 00:00:00 2001
From: clokep /health
endpoint which always r
/_synapse/admin
. These require authentication through an access token of an
admin user. However as access to these endpoints grants the caller a lot of power,
we do not recommend exposing them to the public internet without good reason.
You can use Synapse with a forward or outbound proxy. An example of when +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.
+The http_proxy
, https_proxy
, no_proxy
environment variables are used to
+specify proxy settings. The environment variable is not case sensitive.
http_proxy
: Proxy server to use for HTTP requests.https_proxy
: Proxy server to use for HTTPS requests.no_proxy
: Comma-separated list of hosts, IP addresses, or IP ranges in CIDR
+format which should not use the proxy. Synapse will directly connect to these hosts.The http_proxy
and https_proxy
environment variables have the form: [scheme://][<username>:<password>@]<host>[:<port>]
Supported schemes are http://
and https://
. The default scheme is http://
+for compatibility reasons; it is recommended to set a scheme. If scheme is set
+to https://
the connection uses TLS between Synapse and the proxy.
NOTE: Synapse validates the certificates. If the certificate is not +valid, then the connection is dropped.
+Default port if not given is 1080
.
Username and password are optional and will be used to authenticate against +the proxy.
+Examples
+NOTE: +Synapse does not apply the IP blacklist to connections through the proxy (since +the DNS resolution is done by the proxy). It is expected that the proxy or firewall +will apply blacklisting of IP addresses.
+The proxy will be used for:
+It will not be used for:
+If a proxy server is used with TLS (HTTPS) and no connections are established, +it is most likely due to the proxy's certificates. To test this, the validation +in Synapse can be deactivated.
+NOTE: This has an impact on security and is for testing purposes only!
+To deactivate the certificate validation, the following setting must be made in +homserver.yaml.
+use_insecure_ssl_client_just_for_testing_do_not_use: true
+
This document explains how to enable VoIP relaying on your Home Server with TURN.
@@ -1240,7 +1315,7 @@ turn_allow_guests: True... and then reload any clients (or wait an hour for them to refresh their settings).
-The normal symptoms of a misconfigured TURN server are that calls between devices on different networks ring, but get stuck at "call connecting". Unfortunately, troubleshooting this can be tricky.
@@ -2829,7 +2904,7 @@ be sent. See the delegation documentation for instruOnce federation has been configured, you should be able to join a room over
federation. A good place to start is #synapse:matrix.org
- a room for
Synapse admins.
You can use the federation tester to check if your homeserver is configured correctly. Alternatively try the JSON API used by the federation tester. -- cgit 1.5.1