No error message before upgrade.
Now showing: Your web server is not properly set up to resolve “/ocm-provider/”.
Everything seems to be working normally, but it is annoying.
New .htaccess contains RewriteRule ^ocm-provider/?$ /index.php [QSA,L]
Tested various solutions found here and in other places, but nothing seems to work.
Nginx does not make use of .htaccess files, so you have to edit it by hand anyway. If you have chosen for nginx as webserver, you should read the manual if anything had changed after each update and change it yourself…
Hi @ernolf , thank you for the info.
I removed RewriteRule ^ocm-provider/?$ /index.php [QSA,L] from .htaccess.
You did mentioned a second step, but I don’t have a line with /(ocm-provider|ocs-provider|updater)/ in my .htaccess,
I’'m therefore still getting the warning.
oh I’m sorry about that. Then unfortunately I can’t help any further for the time being. The message didn’t even appear for me because I had already set everything up before the update and I do not use .htaccess for the sake of performance, so all my directory based config is in apache2 configfile.
Following the upgrade the ocm-provider folder was deleted.
I presume that folder is no longer needed, but somehow there is a link to it somewhere.
I downloaded 27.1.1 and copied the ocm-provider folder inside my 27.1.2 installation and the warning disappears, as also described in the bug report…
I’'ll leave the warning on [see I’ve deleted the ocm-provider folder I had manually copied], so that I can monitor what happens with the next upgrade. @ernolf thank you again.
If I copy the folder from the old version, I get this with curl:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<title>301 Moved Permanently</title>
<p>The document has moved <a href="https://mynextcloud/ocm-provider/">here</a>.</p>
<address>Apache/2.4.57 (Debian) Server at mynextcloud</address>
Bei mir hat auch nichts von oben funktiniert.
Jetzt habe ich die Meldung weg bekommen
habe aber keine Ahnung ob die Lösung richtig ist.
Aber vielleicht hilft meine Lösung bei anderen wo die Meldung auch nicht weg geht.
hier meine Lösung
Für alle die die json datei überdie URL angezeigt bekommen
My installation is in domain.tld/nextcloud. The .htaccess changes in #40745 redirect ocm-provider to /index.php, which doesn’t exist.
Changing that line in .htaccess from: RewriteRule ^ocm-provider/?$ /index.php [QSA,L]
to: RewriteRule ^ocm-provider/?$ index.php [QSA,L]
resolved the issue for me, and all checks now pass on the admin page.