I upgraded to the final 27.1.2 version yesterday and this problem is showing up.
I also have an apache web server, but the difference is that nextcloud is in a subdir: www.domainname/nextcloud.
I can confirm that the Rewrite rule in .htaccess file of nextcloud folder is existing:
RewriteRule ^ocm-provider/?$ /index.php [QSA,L]
Did you run occ maintenance:update:htaccess after the upgrade?
Yes, I did.
I also have my nextcloud in a subfolder.
The ocm-provider folder does not exist for me.
I edited the .htaccess and the line:
RewriteRule ^ocm-provider/?$ /index.php [QSA,L] changed to
RewriteRule ^\.ocm-provider/?$ /index.php [QSA,L].
The error disappeared immediately.
Is this the right approach?
1 Like
The problem is still present on my side even with this change.
www.domainname/nextcloud/ocm-provider/
File not found.
www.domainname/nextcloud/index.php/ocm-provider/
Shows some json file
Apache Webserver with Nextcloud in subfolder.
Is your .htaccess at the top root of your domain ?
If so, try this one:
RewriteRule ^ocm-provider/?$ /nextcloud/index.php [QSA,L]
replace /nextcloud/index.php with the sub folder path of your setup
3 Likes
Yes, that was the solution. The warning message no longer exists. Thank you very much.
It’s strange, it’s still not working for me with .htaccess at the root of the domain…
I don’t know how it should behave exactly?
here the same problem without solution
do you have rewrite enable ? do you allow Rewrite Rules in .htaccess ? is the .htaccess loaded/accepted by apache ? can you past the line you have in .htaccess related to ocm-provider ?
is there still a folder ‘ocm-provider’ in your nextcloud setup ?
Here is the .htaccess on the root:
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteRule ^\.well-known/carddav /nextcloud/remote.php/dav [R=301,L]
RewriteRule ^\.well-known/caldav /nextcloud/remote.php/dav [R=301,L]
RewriteRule ^\.well-known/webfinger /nextcloud/index.php/.well-known/webfinger [R=301,L]
RewriteRule ^\.well-known/nodeinfo /nextcloud/index.php/.well-known/nodeinfo [R=301,L]
RewriteRule ^ocm-provider/?$ /nextcloud/index.php [QSA,L]
</IfModule>
The other rules are working, because if I remove them I get some warnings from nextcloud.
The ocm-provider folder is no longer existing.
can you send me (maxence@nextcloud.com) the address of your nextcloud so I can run a curl request myself ?
My .htaccess is not at the top root of my domain.
Yes, your solution works too.
Both types:
RewriteRule ^\.ocm-provider/?$ /index.php [QSA,L] as well
RewriteRule ^ocm-provider/?$ /nextcloudfolder/index.php [QSA,L].
But the question is which variant makes more sense or what effect
the first variant with “\.” at the beginning?
Thank you
Same problem here. nextCloud is installed in a subfolder, ocm-provider rewrite rule is in site config. If I comment ocm-provider line in subfolder .htaccess, the warning disappears, but then of course core integrity check fails for .htaccess. Any suggestions?
I have the same problem. Nextcloud is installed in a subdirectory. The rewrite rules mentioned in this thread did not solve the problem.
Same problem, same fix. The problem disappeared immediately. But I am a noob and I don’t know what this does. Is it a “stable solution”, doesn’t it break something in the future?
Thanks everybody! 
1 Like
Same here - for me it doesnt solve the problem too
So I got rid of the warning by modifying .htaccess and changing the line to
RewriteRule ^.ocm-provider/?$ /index.php [QSA,L]
Initially I tried putting this in my Apache config for my Nextcloud setup but for some reason any rewrite rules I put in there seem to have no affect.
This may work for you when you have nextcloud in a subdirectory. I use nextcloud in a subdomain like cloud.mydomain.de and when I put your change into my .htaccess the warning pops up again. It was gone with the former solution.