From 843e51823db5346b08640ada8e813229541778b7 Mon Sep 17 00:00:00 2001 From: H-Shay Date: Thu, 30 Jun 2022 16:22:17 +0000 Subject: deploy: 8330fc9953032f21eb4c7d5f0627c1e6aba2459c --- develop/setup/forward_proxy.html | 4 ++-- develop/setup/installation.html | 18 +++++++++++------- 2 files changed, 13 insertions(+), 9 deletions(-) (limited to 'develop/setup') diff --git a/develop/setup/forward_proxy.html b/develop/setup/forward_proxy.html index b3019a645f..034bd7b78f 100644 --- a/develop/setup/forward_proxy.html +++ b/develop/setup/forward_proxy.html @@ -217,8 +217,8 @@ will apply blacklisting of IP addresses.

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.

+

To deactivate the certificate validation, the following setting must be added to +your homserver.yaml.

use_insecure_ssl_client_just_for_testing_do_not_use: true
 
diff --git a/develop/setup/installation.html b/develop/setup/installation.html index afddc631fe..a6d8ad7e28 100644 --- a/develop/setup/installation.html +++ b/develop/setup/installation.html @@ -420,11 +420,11 @@ over HTTPS.

Alternatively, you can configure Synapse to expose an HTTPS port. To do so, you will need to edit homeserver.yaml, as follows:

-
  - port: 8448
+
listeners:
+  - port: 8448
     type: http
     tls: true
     resources:
@@ -432,9 +432,13 @@ each line). The relevant lines are like this:
 
  • -

    You will also need to uncomment the tls_certificate_path and -tls_private_key_path lines under the TLS section. You will need to manage -provisioning of these certificates yourself.

    +

    You will also need to add the options tls_certificate_path and +tls_private_key_path. to your configuration file. You will need to manage provisioning of +these certificates yourself.

    +
  • +
  • +

    You can find more information about these options as well as how to configure synapse in the +configuration manual.

    If you are using your own certificate, be sure to use a .pem file that includes the full certificate chain including any intermediate certificates (for instance, if using certbot, use fullchain.pem as your certificate, not -- cgit 1.4.1