Problem with ocm-provider

ℹ️ Support
1

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:

RewriteRule ^\OCT/ocm-provider /OCT/ocm-provider [R=301,L]

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 !

1 Like
2

Same problem - following

3

+1
I am using Apache as my web server, and previously it has been rock solid

4

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.

5

Same problem with Nginx

6

Hi Guys try to have a look on this treat First RC of Nextcloud 27.1.2 - #47 by Joern_Kenntnisreich there is your Solution.

7

I have the same problem. After upgrade to 27.1.2 the ocm-provider folder is missing. I downloaded https://download.nextcloud.com/server/releases/nextcloud-27.1.2.zip and looked inside. Could not found ocm-provider there. I think that is the problem. I have submitted a bug. [Bug]: ocm-provider is missing from nextcloud-27.1.2.zip · Issue #40920 · nextcloud/server · GitHub

8

Removing a slash in .htaccess as indicated in the link below worked for me:

9

Solved with version 27.1.3

10

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:

  1. 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…
  2. The error message is correct and the directory should be reinstated.

Which of these is correct?

11

The former is because NGINX does not support .htaccess files, matter of fact it ignores them. For the latter this and this might be of any help.

Yep.