From 6b78680875d9e721d46e4f3d34047c6a3fbd2f33 Mon Sep 17 00:00:00 2001 From: DMRobertson Date: Mon, 1 Nov 2021 11:36:20 +0000 Subject: deploy: ece84f2c450d986e54acc80971225fb02f4e1d05 --- develop/reverse_proxy.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'develop/reverse_proxy.html') diff --git a/develop/reverse_proxy.html b/develop/reverse_proxy.html index d83219a722..e2f8fea6b9 100644 --- a/develop/reverse_proxy.html +++ b/develop/reverse_proxy.html @@ -222,7 +222,7 @@ to proxied traffic.)

Reverse-proxy configuration examples

NOTE: You only need one of these.

nginx

-
server {
+
server {
     listen 443 ssl http2;
     listen [::]:443 ssl http2;
 
@@ -301,7 +301,7 @@ matrix.example.com {
 }
 

Apache

-
<VirtualHost *:443>
+
<VirtualHost *:443>
     SSLEngine on
     ServerName matrix.example.com
 
@@ -326,7 +326,7 @@ matrix.example.com {
 

NOTE: ensure the nocanon options are included.

NOTE 2: It appears that Synapse is currently incompatible with the ModSecurity module for Apache (mod_security2). If you need it enabled for other services on your web server, you can disable it for Synapse's two VirtualHosts by including the following lines before each of the two </VirtualHost> above:

-
<IfModule security2_module>
+
<IfModule security2_module>
     SecRuleEngine off
 </IfModule>
 
-- cgit 1.5.1