After migrating from Nextcloud 27.1.1 to 27.1.2, in the security and configuration warnings, I received the following message: "Your web server is not properly configured to resolve “/OCT/ocm-provider/,” with OCT being my Nextcloud directory. I noticed that the ocm-provider folder was no longer present. I copied it from version 27.1.1 to version 27.1.2, but the problem was not resolved. I also attempted to add the following line:
to the .htaccess file, but it did not fix the issue. In the past, I successfully made modifications to the .htaccess file, particularly for CardDAV, CalDAV, Webfinger, and Nodeinfo, which resolved similar error messages. Is there a bypass or a solution for this issue?
Thank-you !
Same problem form me. After upgrading from Nextcloud 27.1.1 to 27.1.2 through web based updater I get the same configuration warning. I’m using Apache too.
I am running 27.1.3 updated from 27.1.2. The problem is still there.
The problem seems to be that the rule in .htaccess is pointing to a directory which was included in 27.1.1 but not in 27.1.3. No amount of toying with .htaccess or nginx config will make the error message go away. ISTM the question resolves to one of two alternatives:
The directory is not needed, has been removed, the error message is, therefore incorrect and the test which generates it should also be removed as should the rewrite rule…
The error message is correct and the directory should be reinstated.
Neither. ocm-provider is still handled by Nextcloud. It’s no longer a folder, but it’s a live route.
If you’re still encounter this warning today…
The error means that https://domain.tld/$WEBROOT/ocm-provider isn’t functioning.
E.g.
https://domain.tld/ocm-provider
Or, if using a subdirectory installation:
https://domain.tld/nextcloud/ocm-provider
(These can also be visited in a browser to test - which is the setup check is doing anyway).
To fix:
If web server is Nginx: Make sure you’re running the up-to-date Nginx config from https://docs.nextcloud.com for your installed version of Nextcloud. Check it carefully - it is periodically updated and was for ocm-provider when the handling changed.
If using Apache, make sure you have the .htaccess in your Nextcloud installation directory that gets updated automatically with each release. If still failing, post the line in it that mentions ocm-provider and also confirm you aren’t also getting also setup check failures (because another cause would be if your .htaccess is either being ignored by your Apache config or if it’s being used but some of the required modules are causing some of the rules in it to be ignored). Apache setup instructions are also located in the Admin Manual in the Installation chapter - https://docs.nextcloud.com