With Nextcloud update: "Not properly set up to resolve “/ocm-provider/” and “/ocs-provider/” on NGINX server

MCF · October 8, 2023, 3:42am

There is much chit-chat about this stuff in various nextcloud github issues related to upgrading to the latest 27.1.2 version. There seems to be a problem.

I’m running an apache server with nextcloud in a sub-directory. The fix in this comment solved the problem for me:

github.com/nextcloud/server

[Bug]: ocm-provider validation not working anymore + htaccess entry wrong

opened 03:51AM - 06 Oct 23 UTC

closed 04:22AM - 06 Oct 23 UTC

MrLoverLoverMMMM

bug 0. Needs triage

### ⚠️ This issue respects the following points: ⚠️ - [X] This is a **bug**, no…t a question or a configuration/webserver/proxy issue. - [X] This issue is **not** already reported on [Github](https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3Abug) OR [Nextcloud Community Forum](https://help.nextcloud.com/) _(I've searched it)_. - [X] Nextcloud Server **is** up to date. See [Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions. - [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/). ### Bug description When updating to 27.1.2 the server says that the ocm-provider paths are incorrect. I checked the .htaccess shipped with 27.1.2, but the config in there is incorrect. Deleting the config path from there is leading to a working ocm-provider path (checked in the browser). I do have 2 redirects in the apache-conf: Redirect 301 /ocm-provider /nextcloud/ocm-provider Redirect 301 /ocs-provider /nextcloud/ocs-provider Nevertheless, the nextcloud admin page is still telling me that the ocm-provider path is setup incorrect, why? The ocs-provider is fully fine. There was no error in the .htaccess and my redirect worked out of the box. ### Steps to reproduce 1. Upgrade from 27.1.1 to 27.1.2 2. Open Admin Page 3. ### Expected behavior That it is working like on 27.1.1 without any errors ### Installation method Community Manual installation with Archive ### Nextcloud Server version 27 ### Operating system Debian/Ubuntu ### PHP engine version PHP 8.2 ### Web server Apache (supported) ### Database engine version MariaDB ### Is this bug present after an update or on a fresh install? Updated from a MINOR version (ex. 22.1 to 22.2) ### Are you using the Nextcloud Server Encryption module? None ### What user-backends are you using? - [X] Default user-backend _(database)_ - [ ] LDAP/ Active Directory - [ ] SSO - SAML - [ ] Other ### Configuration report ```shell not needed for this issue ``` ### List of activated Apps ```shell not needed for this issue ``` ### Nextcloud Signing status ```shell all works fine ``` ### Nextcloud Logs ```shell No relevant erros in the log ``` ### Additional info _No response_

TL;DR - in the .htacces file found in your nextcloud root, drop the front slash of the index.php part of this line:

RewriteRule ^ocm-provider/?$ index.php [QSA,L]

I suspect you could also ignore the warning and it will be fixed in the next release of nextcloud.