[Bug]: Your web server is not properly set up to resolve "/nextcloud/ocm-provider/" #40803

wuda2525 · 2023-10-06T13:55:36Z

⚠️ This issue respects the following points: ⚠️

This is a bug, not a question or a configuration/webserver/proxy issue.
This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
I agree to follow Nextcloud's Code of Conduct.

Bug description

Ever since I updated the latest version of NextCloud from v27.1.1 to v27.1.2 using the Updater, I get the following warning message in the Administration Overview page

Your web server is not properly set up to resolve "/nextcloud/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 ↗. On Nginx those are typically the lines starting with "location ~" that need an update.

Steps to reproduce

Click on Administration Settings
On the left pane, click Overview
Click on the Update button

Expected behavior

Should be receiving no warning messages after an update

Installation method

Community Web installer on a VPS or web space

Nextcloud Server version

27

Operating system

Other

PHP engine version

PHP 8.1

Web server

Apache (supported)

Database engine version

PostgreSQL

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?

Default user-backend (database)
LDAP/ Active Directory
SSO - SAML
Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

Looking at the Nextcloud Server Repo (https://github.com/nextcloud/server), it looks like ocm-provider folder. My solution was the following:

Download the previous version (v27.1.1) of Nextcloud server, https://download.nextcloud.com/server/releases/nextcloud-27.1.1.zip
Unzip the file and copy the ocm-provider folder and it's content (index.php) into Apache

alars · 2023-10-06T16:45:48Z

The error seems to be caused by this recent commit:

commit a250250985e6517c1c3a1cc7cd28008948353cb3
Author: Maxence Lange <maxence@artificial-owl.com>
Date:   2023-10-03 14:19:44 -0100

    Update .htaccess
    
    Co-authored-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
    Signed-off-by: Maxence Lange <maxence@artificial-owl.com>

diff --git a/.htaccess b/.htaccess
index 2be3c1b9e15..52caeaf70d4 100644
--- a/.htaccess
+++ b/.htaccess
@@ -90,7 +90,7 @@
   RewriteRule ^remote/(.*) remote.php [QSA,L]
   RewriteRule ^(?:build|tests|config|lib|3rdparty|templates)/.* - [R=404,L]
   RewriteRule ^\.well-known/(?!acme-challenge|pki-validation) /index.php [QSA,L]
-  RewriteRule ^ocm-provider /index.php [QSA,L]
+  RewriteRule ^ocm-provider/?$ /index.php [QSA,L]
   RewriteRule ^(?:\.(?!well-known)|autotest|occ|issue|indie|db_|console).* - [R=404,L]
 </IfModule>

The new RewriteRule looks weird (?$ isn't correct perl re syntax) - when I change it to
RewriteRule ^ocm-provider/(.*) /index.php [QSA,L]
the error disappears.

solracsf · 2023-10-06T17:03:44Z

Cc @blizzz

joshtrichards · 2023-10-06T17:47:18Z

Someone else with subdir install noted the recent PR may have an oversight but I haven't looked deeper into it:

#40794 (comment)

wuda2525 · 2023-10-06T18:03:39Z

Hey Everyone,

Dumb question. Was the ocm-provider folder needed? I'm looking at the master branch (https://github.com/nextcloud/server) and the ocm-provider directory is not present or removed

Dave

PVasileff · 2023-10-06T18:27:53Z

Same warning here after updating v27.1.1 to v27.1.2.
Using nginx webserver (nextcloud is not in subfolder)

solracsf · 2023-10-07T13:32:32Z

@PVasileff For Nginx, see nextcloud/documentation#11179 and nextcloud/documentation#11184

ernolf · 2023-10-07T13:49:35Z

@PVasileff
Using nginx webserver (nextcloud is not in subfolder)

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..

Old config: https://docs.nextcloud.com/server/25/admin_manual/installation/nginx.html?highlight=oc[ms]-provider
New config: https://docs.nextcloud.com/server/27/admin_manual/installation/nginx.html?highlight=ocs-provider

In detail:
Search for this re-string: oc[ms]-provider in your nginx configfile and replace it by this string: ocs-provider

reload or restart nginx

That should do it for you (and nginx users in general)

much luck!

M3taKn1ght · 2023-10-07T18:44:50Z

I also did an update from 27.1.1 to 27.1.2 and get this error.
I use an Nginx Proxy Manager to redirect to my cloudserver. For this I use a subdomain wolke.mydomain.net.
The Cloudserver itself use Apache and root-folder is set to /var/www/nextcloud
Interessting to see is, that wolke.mydomain.net/index.php/ocm-provider will give me an result, but wolke.mydomain.net/ocm-provider will not work.
I updated .htaccess with occ commands, so I see the correct content of the file. For me it seems that an redirect from wolke.mydomain.net/ocm-provider to wolke.mydomain.net/index.php/ocm-provider is not working.
`
RewriteEngine on
RewriteCond %{HTTP_USER_AGENT} DavClnt
RewriteRule ^$ /remote.php/webdav/ [L,R=302]
RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteRule ^.well-known/carddav /remote.php/dav/ [R=301,L]
RewriteRule ^.well-known/caldav /remote.php/dav/ [R=301,L]
RewriteRule ^remote/(.) remote.php [QSA,L]
RewriteRule ^(?:build|tests|config|lib|3rdparty|templates)/. - [R=404,L]
RewriteRule ^.well-known/(?!acme-challenge|pki-validation) /index.php [QSA,L]
RewriteRule ^ocm-provider/?$ /index.php [QSA,L]
RewriteRule ^(?:.(?!well-known)|autotest|occ|issue|indie|db_|console).* - [R=404,L]

AddDefaultCharset utf-8
Options -Indexes

DO NOT CHANGE ANYTHING ABOVE THIS LINE

ErrorDocument 403 /index.php/error/403
ErrorDocument 404 /index.php/error/404

Options -MultiViews
RewriteRule ^core/js/oc.js$ index.php [PT,E=PATH_INFO:$1]
RewriteRule ^core/preview.png$ index.php [PT,E=PATH_INFO:$1]
RewriteCond %{REQUEST_FILENAME} !.(css|js|mjs|svg|gif|png|html|ttf|woff2?|ico|jpg|jpeg|map|webm|mp4|mp3|ogg|wav|wasm|tflite)$
RewriteCond %{REQUEST_FILENAME} !/core/ajax/update.php
RewriteCond %{REQUEST_FILENAME} !/core/img/(favicon.ico|manifest.json)$
RewriteCond %{REQUEST_FILENAME} !/(cron|public|remote|status).php
RewriteCond %{REQUEST_FILENAME} !/ocs/v(1|2).php
RewriteCond %{REQUEST_FILENAME} !/robots.txt
RewriteCond %{REQUEST_FILENAME} !/(ocs-provider|updater)/
RewriteCond %{REQUEST_URI} !^/.well-known/(acme-challenge|pki-validation)/.*
RewriteCond %{REQUEST_FILENAME} !/richdocumentscode(_arm64)?/proxy.php$
RewriteRule . index.php [PT,E=PATH_INFO:$1]
RewriteBase /
`
Thats my complete .htaccess-file

wuda2525 · 2023-10-08T05:42:42Z

Hey Everyone,

I tried implementing the changes mentioned here from @Lawkss (#40794 (comment)) with a brand new install of Nextcloud v27.1.2 using Apache 2.4

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

However, I'm still getting the warning message. Also, I'm using a path(domain.tld/nextcloud) for Nextcloud, as mentioned by @Lawkss

This worksi
domain.tld/nextcloud/index.php/ocm-provider

But, this does not work
domain.tld/nextcloud/ocm-provider

PVasileff · 2023-10-08T07:45:49Z

oc[ms]-provider

@PVasileff
Using nginx webserver (nextcloud is not in subfolder)

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..

Old config: https://docs.nextcloud.com/server/25/admin_manual/installation/nginx.html?highlight=oc[ms]-provider New config: https://docs.nextcloud.com/server/27/admin_manual/installation/nginx.html?highlight=ocs-provider

In detail: Search for this re-string: oc[ms]-provider in your nginx configfile and replace it by this string: ocs-provider

reload or restart nginx

That should do it for you (and nginx users in general)

much luck!

Thanks. That works!

ivnmad · 2023-10-08T10:06:17Z

Hey Everyone,

I tried implementing the changes mentioned here from @Lawkss (#40794 (comment)) with a brand new install of Nextcloud v27.1.2 using Apache 2.4

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

However, I'm still getting the warning message. Also, I'm using a path(domain.tld/nextcloud) for Nextcloud, as mentioned by @Lawkss

This worksi domain.tld/nextcloud/index.php/ocm-provider

But, this does not work domain.tld/nextcloud/ocm-provider

I managed to remove the warning by adding the following to my Nextcloud .conf file:


<Directory /var/www/html/nextcloud/>
     Require all granted
     AllowOverride All
     Options FollowSymLinks MultiViews

     <IfModule mod_dav.c>
       Dav off
     </IfModule>
   </Directory>

SKJoy · 2023-10-08T14:38:43Z

Try this: #40818 (comment)

M3taKn1ght · 2023-10-08T14:58:12Z

Try this: #40818 (comment)

This is not a solution at all, cause i use everytime after an Update Firefox in private Mode and get the Same Errors all over again!

M3taKn1ght · 2023-10-08T17:17:30Z

Hey Everyone,
I tried implementing the changes mentioned here from @Lawkss (#40794 (comment)) with a brand new install of Nextcloud v27.1.2 using Apache 2.4
Changes below: RewriteRule ^ocm-provider/?$ index.php [QSA,L]
However, I'm still getting the warning message. Also, I'm using a path(domain.tld/nextcloud) for Nextcloud, as mentioned by @Lawkss
This worksi domain.tld/nextcloud/index.php/ocm-provider
But, this does not work domain.tld/nextcloud/ocm-provider

I managed to remove the warning by adding the following to my Nextcloud .conf file:
<Directory /var/www/html/nextcloud/>
     Require all granted
     AllowOverride All
     Options FollowSymLinks MultiViews

     <IfModule mod_dav.c>
       Dav off
     </IfModule>
   </Directory>

Oh boy, there was my problem! In german we would say "You don't see the forest, cause of all the trees" and this is quiet what happend. It seems to me, I used an very old apache-config. What was missing was the complete Directory-Node :(
Just this adding to my server, everything is working correct now AND I dont need to copy the old ocm-folder anymore.
Maybe there should be a hint in the documentation, in the update or in the description of the error, taht this message comes up, if apache needs the missing node ^^

JazMTaz · 2023-10-08T21:38:23Z

@PVasileff
Using nginx webserver (nextcloud is not in subfolder)

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..

Old config: https://docs.nextcloud.com/server/25/admin_manual/installation/nginx.html?highlight=oc[ms]-provider New config: https://docs.nextcloud.com/server/27/admin_manual/installation/nginx.html?highlight=ocs-provider

In detail: Search for this re-string: oc[ms]-provider in your nginx configfile and replace it by this string: ocs-provider

reload or restart nginx

That should do it for you (and nginx users in general)

much luck!

Manually updated config as described be ernolf for nginx, warning resolved

wuda2525 · 2023-10-09T03:15:31Z

That solution that @ivnmad suggested did the trick.
Thanks everyone for chiming in with suggestions and solutions.

Closing the ticket

shahn · 2023-10-09T05:35:21Z

I needed to change the RewriteRule in addition to adding the Directory stanza to the Apache config. Is this really closed or does the .htaccess-file need a patch?

M3taKn1ght · 2023-10-09T07:17:26Z

I needed to change the RewriteRule in addition to adding the Directory stanza to the Apache config. Is this really closed or does the .htaccess-file need a patch?

I think, if you read carfully the manual again (e.g. apache and nginx config) and also all Rewrite-Rules, there is no need for a patch.
Seems to me, that only a hint to the webserver-configuration is missing in the warning-msg. Maybe this can be done?

shahn · 2023-10-09T09:08:42Z

Do you also have your nextcloud installation in a subdirectory? If yes, I would appreciate if you could point out which part of the documentation I may have missed.

M3taKn1ght · 2023-10-09T09:23:53Z

Do you also have your nextcloud installation in a subdirectory? If yes, I would appreciate if you could point out which part of the documentation I may have missed.

No, but it's a combination of the update of your webserver-config and .htaccess.
First things first, check the docu
https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html
or for apache
https://docs.nextcloud.com/server/latest/admin_manual/installation/source_installation.html#apache-web-server-configuration
if this looks like your configuration, you need to edit .htaccess like @alars wrote.
You need to include your subfolder to the rewrite rule and bingo ;)

ckorn · 2023-10-09T09:40:02Z

For me this does not fix the issue:
#40803 (comment)
But this does:
#40794 (comment)

This is my nextcloud.conf:

Alias /nextcloud "/var/www/nextcloud/"

<Directory /var/www/nextcloud/>
        Require all granted
        Options FollowSymLinks MultiViews
        #Options +FollowSymlinks
        AllowOverride All

        <IfModule mod_dav.c>
                Dav off
        </IfModule>

        #SetEnv HOME /var/www/nextcloud
        #SetEnv HTTP_HOME /var/www/nextcloud

        #<IfModule mod_rewrite.c>
        #        RewriteEngine on
        #        RewriteRule ^/ocm-provider     /nextcloud/ocm-provider/     [R=301,L]
        #        RewriteRule ^/ocs-provider     /nextcloud/ocs-provider/     [R=301,L]
        #        RewriteRule ^\.well-known/carddav /nextcloud/remote.php/dav [R=301,L]
        #        RewriteRule ^\.well-known/caldav /nextcloud/remote.php/dav [R=301,L]
        #</IfModule>

</Directory>

shahn · 2023-10-09T13:36:11Z

Do you also have your nextcloud installation in a subdirectory? If yes, I would appreciate if you could point out which part of the documentation I may have missed.

No, but it's a combination of the update of your webserver-config and .htaccess. First things first, check the docu https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html or for apache https://docs.nextcloud.com/server/latest/admin_manual/installation/source_installation.html#apache-web-server-configuration if this looks like your configuration, you need to edit .htaccess like @alars wrote. You need to include your subfolder to the rewrite rule and bingo ;)

My argument is that the RewriteRule should be written such that it works for both installations that are in / as well as in /nextcloud/, because you are not supposed to edit the rewrite rules as per a comment included in that very file, and that is why this issue is not resolved IMO. That in addition you need to edit the apache configuration is a separate point.

wrecklass · 2023-10-11T11:47:56Z

Problem still exists in latest update.

wuda2525 · 2023-10-11T14:43:52Z

Hey Everyone,
I'm going to reopen this ticket. It seems that some of the solutions proposed is not working for everyone.

This question is for the Nextcloud developers and architects. I'm just wondering if the removing ocm-provider folder/directory and redirecting it to use index.php is short term solution or a permanent fix?

Just want to say Thank You to the Nextcloud team for giving all of us a great product.

OlafTitz · 2023-10-11T18:38:51Z

The real issue is that all RewriteRule entries must produce relative instead of absolute URL paths, i.e. the leading slash is wrong in all of them. ("Relative" here really means "relative to the directory where the .htaccess file is".) You can verify this by trying curl -i https://your.host/path/to/nextcloud/.well-known/caldav, this will produce a wrong redirect URL.

This patch fixes all of them, I've checked manually.
htaccess.diff.txt
What appears to be missing is a matching RewriteBase, but that is installation-specific.

See also first answer in https://stackoverflow.com/questions/21347768/what-does-rewritebase-do-and-how-to-use-it which explains better than the Apache docs what happens with absolute and relative redirect results.

blizzz · 2023-10-11T19:24:56Z

fix is in #40843 + backported, i.e. arrives with next maintenance releases.

enricotagliavini · 2023-10-12T13:02:42Z

It looks like the .htaccess RewriteRule is not generic enough. It works for setups without a subfolder, but not when using a subfolder (i.e. nextcloud in accessed via https://domain.tld/nextcloud/). The original line is

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

which is an absolute rewrite rule. Any subfolder component would be lost, i.e. https://domail.tld/nextcloud/ocm-provider/, becomes https://domail.tld/index.php/ocm-provider/, rather than https://domail.tld/nextcloud/index.php/ocm-provider/

Changing the line above to

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

making it a relative substitution, will solve the issue provided you set the correct 'htaccess.RewriteBase' option in config/config.php and ran

sudo -u <apache user> php /var/www/nextcloud/occ maintenance:update:htaccess

recrunchi · 2023-10-13T16:19:25Z

Hi. Even if i try modifying .htaccess in nextcloud folder, it fails the overall check because there is no ocm-provider folder anymore, after today i updated to 27.1.2

I've noticed that in my previous backup folder of older nextcloud versions the ocm-provider folder exists.
f.e.:
locate ocm-provider
backups/nextcloud-27.0.2.1-1694975084/ocm-provider
backups/nextcloud-27.0.2.1-1694975084/ocm-provider/index.php
backups/nextcloud-27.1.0.7-1697195388/ocm-provider
backups/nextcloud-27.1.0.7-1697195388/ocm-provider/index.php

So i copied on of these "old" folders and now i have the "All checks passed" in Administration Settings.

Hope it helps.
Bye.

MegaV0lt · 2023-10-13T16:28:34Z

Changing .htaccess works for me. Thanks!

darkBuddha · 2023-10-14T09:15:37Z

How to fix in Nginx?

Hetti · 2023-10-14T12:46:18Z

How to fix in Nginx?

As mentioned by @ernolf #40803 (comment)

Then reload config with nginx -s reload

MattRGX · 2023-10-19T17:17:48Z

Hello,
Do we have to wait for an update to fix this issue on apache web server ?

joshtrichards · 2023-10-20T13:00:37Z

@MattRGX - No see #40920 (comment)

catfish-k · 2023-10-23T18:40:49Z

I don't have an ocm-provider folder after upgrade to 27.1.2. I do have an ocs-provider folder. I edited my .htaccess to remove the slash:

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

changed to:

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

But I still get the error.

EDIT: Same ocm-provider error in 27.1.3.

EDIT2: Linking the ocs-provider directory to what I assume is the old location of ocm-provider fixes the error, ie. "ln - s ocs-provider ocm-provider" in the nextcloud installation directory

ScrambleTheRamble · 2023-10-31T10:18:08Z

The solution mentioned by @alars here solved the issue for me

catfish-k · 2023-10-31T16:54:48Z

In my case I think I had a malformed apache virtual host config. I no longer have the warning after changing .htaccess to:

RewriteRule ^ocm-provider/(.*) /index.php [QSA,L]

And adding these starred lines to my apache virtual host config:

 <VirtualHost *:80>
            ServerAdmin webmaster@domain.com
            ServerName nextcloud.domain.com
            DocumentRoot /var/www/nextcloud

            **<Directory /var/www/nextcloud>
             Require all granted
             AllowOverride All
             Options FollowSymLinks MultiViews
             SetEnv HOME /var/www/nextcloud
             SetEnv HTTP_HOME /var/www/nextcloud
            </Directory>**

            <IfModule mod_headers.c>
                    Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"
            </IfModule>

            ErrorLog ${APACHE_LOG_DIR}/error.log
            CustomLog ${APACHE_LOG_DIR}/access.log combined

    </VirtualHost>

(I have a Caddy SSL reverse proxy, so no SSL)

Thanks all!

BenS89 · 2023-11-01T11:02:42Z

Hey Everyone,
I tried implementing the changes mentioned here from @Lawkss (#40794 (comment)) with a brand new install of Nextcloud v27.1.2 using Apache 2.4
Changes below: RewriteRule ^ocm-provider/?$ index.php [QSA,L]
However, I'm still getting the warning message. Also, I'm using a path(domain.tld/nextcloud) for Nextcloud, as mentioned by @Lawkss
This worksi domain.tld/nextcloud/index.php/ocm-provider
But, this does not work domain.tld/nextcloud/ocm-provider

I managed to remove the warning by adding the following to my Nextcloud .conf file:
<Directory /var/www/html/nextcloud/>
     Require all granted
     AllowOverride All
     Options FollowSymLinks MultiViews

     <IfModule mod_dav.c>
       Dav off
     </IfModule>
   </Directory>

That did the trick for me! Thanks a lot

david-kalbermatten · 2023-11-03T12:30:55Z

For anyone using Nginx Proxy Manager with Nextcloud being hosted on a sub-domain instead of a sub-folder

I added the following lines to the 'Advanced' Tab:

location = /ocs-provider {
    try_files $uri $uri/ /index.php$request_uri;
}

location ~ ^/ocm-provider {
    try_files $uri $uri/ /index.php$request_uri;
}

Dizspy · 2023-11-25T11:36:20Z

Folder ocm-provider has been removed from Nextcloud since 27.1.2, which has been confirmed in another thread.
But the stupid check for this folder still persists even in 27.1.4, which has been released recently.
Could you please be so kind to finally remove the obsolete check for 'ocm-provider' which is bugging so many users with a non existent error?

joshtrichards · 2023-11-25T14:39:03Z

@Dizspy The old folder is gone, not the new handler for it is not. The check isn't for the folder, but for the URL which is an endpoint handled in-code. It's still very much a legitimate endpoint:

server/core/routes.php

Line 108 in 28e0ccf

['name' => 'OCM#discovery', 'url' => '/ocm-provider/'],

dd5fz · 2023-11-30T13:53:20Z

I just updated to 27.1.4 and am also, yet again, getting the error message: Your web server is not properly set up to resolve "/nextcloud/ocm-provider/"...

Operating System: Linux 6.1.21-v8+ aarch64
CPU: Raspberry Pi 3 Model B Plus Rev 1.3 (4 cores)
Memory: 959.00 MB
Webserver: Apache/2.4.56 (Debian)
URL: https://xxx.yyyyy.zzz/nextcloud/index.php
NextCloud Directory: /var/www/html/nextcloud

PHP:
Version: 8.1.13
Memory limit: 512 MB
Max execution time: 3600
Upload max size: 4 GB
Extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, Reflection, SPL, session, standard, sodium, apache2handler, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, gmp, iconv, igbinary, imagick, imap, intl, exif, msgpack, mysqli, pdo_mysql, Phar, posix, readline, redis, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, memcached, Zend OPcache

Database:
Type: mysql
Version: 10.5.21

ulno · 2023-12-30T19:48:17Z

I don't get the above error message, though I think my problem is related. I am on nextcloud aoi (running in docker). On "Checking for system and security issues." In the admin overview it says "All checks passed."

My rewrite rule in the aoi-nextcloud container .htaccess is: RewriteRule ^ocm-provider/?$ index.php [QSA,L]

However since the last update to Nextcloud AIO v7.9.0 / Nextcloud Hub 6 (27.1.5) I get the following and the system is slow as molasses (4 core i7, 32 gb ram, SSD storage):

[no app in context] Warning: GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 10003 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://192.168.1.10/nextcloud/ocm-provider/ at <<closure>>

 0. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 158
    GuzzleHttp\Handler\CurlFactory::createRejection("*** sensitive parameters replaced ***")
 1. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 110
    GuzzleHttp\Handler\CurlFactory::finishError(["GuzzleHttp\\Handler\\CurlHandler"], "*** sensitive parameters replaced ***", ["GuzzleHttp\\Handler\\CurlFactory"])
 2. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Handler/CurlHandler.php line 47
    GuzzleHttp\Handler\CurlFactory::finish(["GuzzleHttp\\Handler\\CurlHandler"], "*** sensitive parameters replaced ***", ["GuzzleHttp\\Handler\\CurlFactory"])
 3. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 137
    GuzzleHttp\Handler\CurlHandler->__invoke("*** sensitive parameters replaced ***", "*** sensitive parameters replaced ***")
 4. /var/www/html/lib/private/Http/Client/DnsPinMiddleware.php line 114
    GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***")
 5. /var/www/html/3rdparty/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php line 35
    OC\Http\Client\DnsPinMiddleware->OC\Http\Client\{closure}("*** sensitive parameters replaced ***")
 6. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 31
    GuzzleHttp\PrepareBodyMiddleware->__invoke("*** sensitive parameters replaced ***", "*** sensitive parameters replaced ***")
 7. /var/www/html/3rdparty/guzzlehttp/guzzle/src/RedirectMiddleware.php line 71
    GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***")
 8. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 63
    GuzzleHttp\RedirectMiddleware->__invoke("*** sensitive parameters replaced ***", "*** sensitive parameters replaced ***")
 9. /var/www/html/3rdparty/guzzlehttp/guzzle/src/HandlerStack.php line 75
    GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***")
10. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Client.php line 331
    GuzzleHttp\HandlerStack->__invoke("*** sensitive parameters replaced ***", "*** sensitive parameters replaced ***")
11. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Client.php line 168
    GuzzleHttp\Client->transfer("*** sensitive parameters replaced ***", "*** sensitive parameters replaced ***")
12. /var/www/html/3rdparty/guzzlehttp/guzzle/src/Client.php line 187
    GuzzleHttp\Client->requestAsync("*** sensitive parameters replaced ***")
13. /var/www/html/lib/private/Http/Client/Client.php line 230
    GuzzleHttp\Client->request("*** sensitive parameters replaced ***", "https://192.168 ... /", [true,10,10,[tru ... "])
14. /var/www/html/lib/private/OCM/OCMDiscoveryService.php line 92
    OC\Http\Client\Client->get("https://192.168 ... /", [10,true,10])
15. /var/www/html/apps/files_sharing/lib/External/Storage.php line 84
    OC\OCM\OCMDiscoveryService->discover("https://192.168.1.10/nextcloud")
16. /var/www/html/lib/private/Files/Mount/MountPoint.php line 168
    OCA\Files_Sharing\External\Storage->__construct(["https://192.16 ... "])
17. /var/www/html/lib/private/Files/Mount/MountPoint.php line 193
    OC\Files\Mount\MountPoint->createStorage("*** sensitive parameters replaced ***")
18. /var/www/html/lib/private/Files/Mount/MountPoint.php line 294
    OC\Files\Mount\MountPoint->getStorage()
19. /var/www/html/lib/private/Files/Config/UserMountCache.php line 83
    OC\Files\Mount\MountPoint->getStorageRootId()
20. /var/www/html/lib/private/Files/SetupManager.php line 297
    OC\Files\Config\UserMountCache->registerMounts("*** sensitive parameters replaced ***", [["OC\\Files\\Mo ... ]], ["OC\\Files\\Mou ... "])
21. /var/www/html/lib/private/Files/SetupManager.php line 221
    OC\Files\SetupManager->afterUserFullySetup("*** sensitive parameters replaced ***", [])
22. /var/www/html/lib/private/legacy/OC_Util.php line 111
    OC\Files\SetupManager->setupForUser("*** sensitive parameters replaced ***")
23. /var/www/html/custom_apps/memories/lib/Service/Index.php line 75
    OC_Util::setupFS("ulno")
24. /var/www/html/custom_apps/memories/lib/Cron/IndexJob.php line 92
    OCA\Memories\Service\Index->indexUser("ulno")
25. /var/www/html/lib/private/User/Manager.php line 632
    OCA\Memories\Cron\IndexJob->OCA\Memories\Cron\{closure}("*** sensitive parameters replaced ***")
26. /var/www/html/custom_apps/memories/lib/Cron/IndexJob.php line 100
    OC\User\Manager->callForSeenUsers(["Closure"])
27. /var/www/html/custom_apps/memories/lib/Cron/IndexJob.php line 63
    OCA\Memories\Cron\IndexJob->indexAllUsers()
28. /var/www/html/lib/public/BackgroundJob/Job.php line 81
    OCA\Memories\Cron\IndexJob->run(null)
29. /var/www/html/lib/public/BackgroundJob/TimedJob.php line 103
    OCP\BackgroundJob\Job->start(["OC\\BackgroundJob\\JobList"])
30. /var/www/html/lib/public/BackgroundJob/TimedJob.php line 93
    OCP\BackgroundJob\TimedJob->start(["OC\\BackgroundJob\\JobList"])
31. /var/www/html/cron.php line 152
    OCP\BackgroundJob\TimedJob->execute(["OC\\BackgroundJob\\JobList"], ["OC\\Log"])

at 2023-12-30T19:38:55+00:00

Why is it trying to connect to 192.168.1.10? I have not configured that anywhere.
I can successfully open on my server /index.php/ocm-provider/ as well as only /ocm-provider/ (both giving a json file).

Also the /nextcloud/ prefix seems weird.

Any idea what could have gone wrong here?

Can also start a new issue if this one is significantly different.

joshtrichards · 2024-01-01T21:49:54Z

@ulno Your matter appears unrelated. I suggest posting over at the Nextcloud Help Forum - https://help.nextcloud.com - since it also appears to likely be a configuration matter.

ulno · 2024-01-03T08:35:06Z

For reference, if someone lands here, I re-posted my problem here: https://help.nextcloud.com/t/nextcloud-aoi-update-to-nextcloud-hub-6-27-1-5-introduces-ocm-provider-issues-and-uses-undefined-ip-192-168-1-10/178100

Uncert · 2024-08-20T01:05:17Z

How to fix in Nginx?

As mentioned by @ernolf #40803 (comment)

Then reload config with nginx -s reload

its doesn't work for me. : (


    location ~ ^\/(?:updater|ocs-provider)(?:$|\/) {
        try_files $uri/ =404;
        index index.php;
    }

joshtrichards · 2024-08-21T14:38:53Z

@Uncert Compare your config to the actual documented one. Yours does not match:

https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html

Please follow-up at the help forum - https://help.nextcloud.com - for further troubleshooting since this is not a bug.

apotek · 2024-10-22T16:21:23Z

The new RewriteRule looks weird (?$ isn't correct perl re syntax) - when I change it to
RewriteRule ^ocm-provider/(.*) /index.php [QSA,L]

I don't think the problem is that the pattern is incorrect. It's a correct pattern, the $ indicating end of the line, meaning that the intent is that the rule should only apply if the url IS literally either ocm-provider or ocm-provider/.

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

So it looks like the developer meant for this to only work if there are no query parameters, etc, which might be correct, depending on what an ocm-provider route is supposed to do.

I think the "root" issue here is that this pattern assumes nextcloud is installed at root and not in a subfolder.

wuda2525 added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Oct 6, 2023

szaimen added the 27-feedback label Oct 6, 2023

solracsf changed the title ~~[Bug]:~~ [Bug]: Your web server is not properly set up to resolve "/nextcloud/ocm-provider/" Oct 6, 2023

solracsf added bug and removed bug labels Oct 6, 2023

bachp mentioned this issue Oct 7, 2023

nextcloud27: 27.1.1 -> 27.1.2 NixOS/nixpkgs#259348

Closed

12 tasks

wuda2525 closed this as completed Oct 9, 2023

wuda2525 reopened this Oct 11, 2023

blizzz closed this as completed Oct 11, 2023

holta mentioned this issue Nov 6, 2023

Nextcloud 27.1+ NGINX configuration might need improvement? iiab/iiab#3669

Closed

joshtrichards mentioned this issue Nov 30, 2023

[Bug]: Your web server is not properly set up to resolve "/ocm-provider/" warning after update to 27.1.4 #41762

Closed

8 tasks

dd5fz mentioned this issue Dec 5, 2023

[Bug]: ocm-provider is missing from nextcloud-27.1.2.zip #40920

Closed

8 tasks

[Bug]: Your web server is not properly set up to resolve "/nextcloud/ocm-provider/" #40803

[Bug]: Your web server is not properly set up to resolve "/nextcloud/ocm-provider/" #40803

Comments

wuda2525 commented Oct 6, 2023

⚠️ This issue respects the following points: ⚠️

Bug description

Steps to reproduce

Expected behavior

Installation method

Nextcloud Server version

Operating system

PHP engine version

Web server

Database engine version

Is this bug present after an update or on a fresh install?

Are you using the Nextcloud Server Encryption module?

What user-backends are you using?

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

alars commented Oct 6, 2023

solracsf commented Oct 6, 2023

joshtrichards commented Oct 6, 2023 • edited Loading

wuda2525 commented Oct 6, 2023 • edited Loading

PVasileff commented Oct 6, 2023

solracsf commented Oct 7, 2023 • edited Loading

ernolf commented Oct 7, 2023 • edited Loading

M3taKn1ght commented Oct 7, 2023 • edited Loading

DO NOT CHANGE ANYTHING ABOVE THIS LINE

wuda2525 commented Oct 8, 2023

PVasileff commented Oct 8, 2023

ivnmad commented Oct 8, 2023 • edited Loading

SKJoy commented Oct 8, 2023

M3taKn1ght commented Oct 8, 2023

M3taKn1ght commented Oct 8, 2023

JazMTaz commented Oct 8, 2023 • edited Loading

wuda2525 commented Oct 9, 2023

shahn commented Oct 9, 2023

M3taKn1ght commented Oct 9, 2023

shahn commented Oct 9, 2023

M3taKn1ght commented Oct 9, 2023

ckorn commented Oct 9, 2023

shahn commented Oct 9, 2023

wrecklass commented Oct 11, 2023

wuda2525 commented Oct 11, 2023 • edited Loading

OlafTitz commented Oct 11, 2023

blizzz commented Oct 11, 2023

enricotagliavini commented Oct 12, 2023

recrunchi commented Oct 13, 2023

MegaV0lt commented Oct 13, 2023

darkBuddha commented Oct 14, 2023

Hetti commented Oct 14, 2023 • edited Loading

MattRGX commented Oct 19, 2023

joshtrichards commented Oct 20, 2023

catfish-k commented Oct 23, 2023 • edited Loading

ScrambleTheRamble commented Oct 31, 2023

catfish-k commented Oct 31, 2023 • edited Loading

BenS89 commented Nov 1, 2023

david-kalbermatten commented Nov 3, 2023

Dizspy commented Nov 25, 2023

joshtrichards commented Nov 25, 2023

dd5fz commented Nov 30, 2023 • edited Loading

ulno commented Dec 30, 2023

joshtrichards commented Jan 1, 2024

ulno commented Jan 3, 2024

Uncert commented Aug 20, 2024

joshtrichards commented Aug 21, 2024 • edited Loading

apotek commented Oct 22, 2024 • edited Loading

joshtrichards commented Oct 6, 2023 •

edited

Loading

wuda2525 commented Oct 6, 2023 •

edited

Loading

solracsf commented Oct 7, 2023 •

edited

Loading

ernolf commented Oct 7, 2023 •

edited

Loading

M3taKn1ght commented Oct 7, 2023 •

edited

Loading

ivnmad commented Oct 8, 2023 •

edited

Loading

JazMTaz commented Oct 8, 2023 •

edited

Loading

wuda2525 commented Oct 11, 2023 •

edited

Loading

Hetti commented Oct 14, 2023 •

edited

Loading

catfish-k commented Oct 23, 2023 •

edited

Loading

catfish-k commented Oct 31, 2023 •

edited

Loading

dd5fz commented Nov 30, 2023 •

edited

Loading

joshtrichards commented Aug 21, 2024 •

edited

Loading

apotek commented Oct 22, 2024 •

edited

Loading