From d41fb74bb0c9e9be04fe4e476ff97e02ecd13f11 Mon Sep 17 00:00:00 2001 From: BernieO Date: Thu, 28 Feb 2019 17:33:22 +0100 Subject: [PATCH] change nginx-config for subdir to resolve /ocm-provider properly MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After upgrading to 15.0.5 this is shown in the Admin-panel: ``` Your web server is not properly set up to resolve “/ocm-provider/”. This is most likely related to a web server configuration that was not updated to deliver this folder directly. Please compare your configuration against the shipped rewrite rules in “.htaccess” for Apache or the provided one in the documentation for Nginx at it’s documentation page 1. On Nginx those are typically the lines starting with “location ~” that need an update. ``` I think for runnning nextcloud in a subdirectory of webroot, this redirect has to be added to the configuration signed-off by bernieo.github@gmx.de --- admin_manual/installation/nginx.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/admin_manual/installation/nginx.rst b/admin_manual/installation/nginx.rst index 4c53a8cfd..63d870f22 100644 --- a/admin_manual/installation/nginx.rst +++ b/admin_manual/installation/nginx.rst @@ -255,6 +255,9 @@ your nginx installation. location = /.well-known/caldav { return 301 $scheme://$host/nextcloud/remote.php/dav; } + location ~/(ocm-provider|ocs-provider)/ { + return 301 $scheme://$host/nextcloud/$1/; + } location /.well-known/acme-challenge { }