From 6cc257a0178f3e9a2ce738c033d1ec22412d571e Mon Sep 17 00:00:00 2001 From: mrplow87 Date: Wed, 27 Mar 2019 09:13:02 +0100 Subject: [PATCH] add server_port variable to well-known redirects if Nextcloud is used on a custom HTTPS port, the well-known redirects do not work, because the server port is not included in the redirect. --- admin_manual/installation/nginx.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/admin_manual/installation/nginx.rst b/admin_manual/installation/nginx.rst index 36359ee2e..21a3ebfce 100644 --- a/admin_manual/installation/nginx.rst +++ b/admin_manual/installation/nginx.rst @@ -42,7 +42,7 @@ webroot of your nginx installation. In this example it is listen [::]:80; server_name cloud.example.com; # enforce https - return 301 https://$server_name$request_uri; + return 301 https://$server_name:443$request_uri; } server { @@ -95,10 +95,10 @@ webroot of your nginx installation. In this example it is # rewrite ^/.well-known/webfinger /public.php?service=webfinger last; location = /.well-known/carddav { - return 301 $scheme://$host/remote.php/dav; + return 301 $scheme://$host:$server_port/remote.php/dav; } location = /.well-known/caldav { - return 301 $scheme://$host/remote.php/dav; + return 301 $scheme://$host:$server_port/remote.php/dav; } # set max upload size @@ -199,7 +199,7 @@ your nginx installation. listen [::]:80; server_name cloud.example.com; # enforce https - return 301 https://$server_name$request_uri; + return 301 https://$server_name:443$request_uri; } server { @@ -248,10 +248,10 @@ your nginx installation. # rewrite ^/.well-known/webfinger /nextcloud/public.php?service=webfinger last; location = /.well-known/carddav { - return 301 $scheme://$host/nextcloud/remote.php/dav; + return 301 $scheme://$host:$server_port/nextcloud/remote.php/dav; } location = /.well-known/caldav { - return 301 $scheme://$host/nextcloud/remote.php/dav; + return 301 $scheme://$host:$server_port/nextcloud/remote.php/dav; } location /.well-known/acme-challenge { }