Your web server is not properly set up to resolve "/ocm-provider/"

ℹ️ Support
10

Same here?

11

Same here! Fedora server 29, Apache (httpd-2.4.38), PHP(7.2.15) upgrade to 15.0.5 from 15.0.4

12

On Fedora server 29, Apache (httpd-2.4.38), PHP(7.2.15) upgrade to 15.0.5 from 15.0.4. I solved the error by adding the following line in the file < file-nextcloud >.conf in the folder /etc/httpd/conf.d

Redirect 301 /ocm-provider https://< name server > / < folder nextcloud install > / ocm-provider
Redirect 301 /ocs-provider https://< name server > / < folder nextcloud install > / ocs-provider

do not put the spaces, they are only for this edition…

1 Like
13

Good work for me.

Tested on Also

Redirect 301 /ocm-provider/ /nx/ocm-provider/
Redirect 301 /ocs-provider/ /nx/ocs-provider/

I writers on .htaccess root
And work for me,

/nx/ is folder on My nextcloud

1 Like
14

Same here SharedHosting Apache PHP 7.2.3 upgrade to 15.0.4 from 15.0.5.

Thanks to gus and Tiger for a solution :clap:
Because of no access to /etc/httpd/conf.d (SharedHosting) it works for me to put into my .htaccess in the webroot:
Redirect 301 /ocm-provider /< FolderNextclouInstall >/ocm-provider
Redirect 301 /ocs-provider /< FolderNextclouInstall >/ocs-provider

Works for me too …

15

why don`t the nextcloud developers pay more attention to shared enviroments? I guess most of the people have have nextcloud installed on a shared webspace…

3 Likes
16

I dropped the following into the end of my /etc/apache2.conf file and all good now.

Redirect 301 /ocm-provider/ /nextcloud/ocm-provider/
Redirect 301 /ocs-provider/ /nextcloud/ocs-provider/

Thanks guys!

3 Likes
17

As the OP I am increasingly confused. My instance of Nextcloud is running on a Synology DS218+ NAS and none of these locations seem to make sense in my install. I’ve put the redirect commands all over the place to no avail. In the past I’ve had a couple of issues and it’s like I am the only person ever to be running Nextcloud on a Diskstation. The Synology communities claims not to have a clue, neither do the Nextcloud communities and each refers me back to the other - so I am between the devil and the deep blue sea. I’ve even been looking for some alternative to Nextcloud which might be better supported on a Synology NAS - but I am yet to find anything. I need Calendar and Contacts (with user pics) - not too bothered about files. There must be someone out there who can help?

18

Hi Bernie_O,

I am also using nginx and nextcloud running in a subdirectory.

I have added the following lines in my nextcloud.conf:

    location ~ ^\/nextcloud\/(?:updater|ocs-provider|ocm-provider)(?:$|\/) {
        return 301 $scheme://$host/nextcloud/$1/;
        #return 301 https://$server_name$request_uri;
        try_files $uri/ =404;
        index index.php;
    }

but I have always the same warning.

Where I am wrong?
Thank you in advance.
Omar

19

Worked!

PHP Version 7.1.26-1+ubuntu18.04.1+deb.sury.org+1
NC in /var/www/nextcloud

20

Can you see the difference?
You need to point from the root to the subfolder. My location block does this - your location doesn’t.
Undo your changes (they break ocs/m-provider completely!) and add my location block right after the location blocks with the .well-known/[...] redirects.

21

Adding this to /etc/apache2/sites-available/nextcloud.conf

Redirect 301 /ocm-provider/ /nextcloud/ocm-provider/
Redirect 301 /ocs-provider/ /nextcloud/ocs-provider/

and restarting apache also worked for me.
Thank you all!

2 Likes
22

Your tip saved my day. Hope, that the Nextcloud boys and girls are reading this, too.

23

I put your lines here

    location = /nextcloud/.well-known/caldav {
                return 301 $scheme://$host/nextcloud/remote.php/dav;
        }

    location /.well-known/acme-challenge { }

    location ~ /(ocm-provider|ocs-provider)/ {
        return 301 $scheme://$host/nextcloud/$1/;
    }

    location ^~ /nextcloud {
    ...

But the warnings persist. Is this the right spot?
Or are your lines meant to be inserted in addition so something else?

24

That looks good.
Did you tell nginx to reload the configuration?

nginx -s reload
26

That looks good.
Did you tell nginx to reload the configuration?

nginx -s reload

yes, I did.

I should probably mention that I use nginx as a reverse proxy, so everything Nextcloud gets redirected to 127.0.0.1:82 and this is where this configuration takes over. (I don’t know it this matters, just to prevent a “you should have said that earlier”)

27

Instead of sending the client a redirect, I just created aliases for these two paths.
I already had in my apache conf:
Alias /nextcloud "/var/www/nextcloud/"

So now I also have:
Alias /ocm-provider “/var/www/nextcloud/ocm-provider/”
Alias /ocs-provider “/var/www/nextcloud/ocs-provider/”

And that too seems to have cleared this error.

2 Likes
28

Hello Bernie_O,

I have added exactly your lines into my nextcloud.conf file (located in /etc/nginx/conf.d/), so now I have this:

# The following rule is only needed for the Social app.
# Uncomment it if you're planning to use this app.
# rewrite ^/.well-known/webfinger /nextcloud/public.php?service=webfinger last;

location = /.well-known/carddav {
    return 301 $scheme://$host/nextcloud/remote.php/dav;
}

location = /.well-known/caldav {
    return 301 $scheme://$host/nextcloud/remote.php/dav;
}

location /.well-known/acme-challenge { }

location ~ /(ocm-provider|ocs-provider)/ {
    return 301 $scheme://$host/nextcloud/$1/;
}

location ^~ /nextcloud {

    # set max upload size
    client_max_body_size 10240M;
    # turns out the optimization conf already set the fast buffer size so I just nixed that from my conf
    #fastcgi_buffers 64 4K;

but the warning message on the WebUI is still there.

Any other idea? Where I am wrong?

Thank you very much.
Omar

29

NOT solved! I have no /etc/httpd/conf.d - nobody in this thread has addressed my issue. I am running NextCloud on a Synology DS218+ NAS. Who marks these threads as ‘solved’?

30

Merci, pour la solution, plus de message :slight_smile: