OCM-provider problem

Zorglube · March 15, 2026, 8:54pm

Support intro

Sorry to hear you’re facing problems.

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

Official documentation (searchable and regularly updated)
How to topics and FAQs
Forum search

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can.

The Basics

Nextcloud Server version (e.g., 29.x.x):
- Nextcloud Hub 26 Winter (33.0.0)
Operating system and version (e.g., Ubuntu 24.04):
- Debian 12.13
Web server and version (e.g, Apache 2.4.25):
- Apache 2.4.65
Reverse proxy and version _(e.g. nginx 1.27.2)
- no reverse proxy
PHP version (e.g, 8.3):
- 8.4
Is this the first time you’ve seen this error? (Yes / No):
- no
When did this problem seem to first start?
- se below
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- manual
Are you using CloudfIare, mod_security, or similar? (Yes / No)
- no

Summary of the issue you are facing:

In the administration Overview it’s said that there’s an ocm-provider problem.

Here (https://forum.ubuntu-fr.org/viewtopic.php?id=2081998) the solution is to put the “AllowOverride” statement to “All”.

But when I do this my server is not reachable and there are errors message like “ExceptionThe requested uri(/apps/dashboard/) cannot be processed by the script ‘/xxxx/index.php’)

The alternative is : ocm-provider error or server unavailable

Steps to replicate it (hint: details matter!):

Modify the AllowOverride from None to All

Log entries

Erreur
index
Exception
The requested uri(/apps/dashboard/) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:14

Erreur
index
Exception
The requested uri(/avatar/unuage/64) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:13

Erreur
index
Exception
The requested uri(/avatar/unuage/64) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/contactsmenu/teams) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/settings/ajax/checksetup) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/dark-highcontrast.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/light.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/light-highcontrast.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/js/core/merged-template-prepend.js) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/opendyslexic.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/light-highcontrast.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/dark.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/dark-highcontrast.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/light.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/dark.css) cannot be processed by the script '/xxx/index.php')

15 mars 2026, 21:28:12

Erreur
index
Exception
The requested uri(/apps/theming/theme/default.css) cannot be processed by the script '/xxx/index.php')
Web Browser

The working file xxx.conf

<VirtualHost *:80>
    ServerName sss.com
    Redirect permanent / https://sss.com/
    ServerSignature Off
    RewriteEngine On
    RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
</VirtualHost>

<VirtualHost *:443>
    ServerAdmin foo@bar.com
    ServerName sss.com

    DocumentRoot /path/www/xxx/

    <Directory /path/www/xxx/>
       Options -Indexes +FollowSymLinks +MultiViews
       AllowOverride None
       Require all granted
       SetEnv HOME /path/www/xxx
       SetEnv HTTP_HOME /path/www/xxx
    </Directory>

    SSLEngine on
    SSLProtocol All -SSLv2 -TLSv1
    SSLHonorCipherOrder On
    SSLCompression off
    Header set Strict-Transport-Security "max-age=15768000"
    SSLCertificateFile /etc/letsencrypt/live/sss.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/sss.com/privkey.pem

    <IfModule mod_http2.c>
      Protocols h2 http/1.1
    </IfModule>

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

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


    ErrorLog /var/log/apache2/xxx-error.log
    CustomLog /var/log/apache2/xxx-access.log combined

</VirtualHost>

If someone can help me…

jtr · March 16, 2026, 3:24pm

What’s the precise warning message? There are several variations.

But when I do this my server is not reachable and there are errors message like “Exception The requested uri(/apps/dashboard/) cannot be processed by the script ‘/xxxx/index.php’)

Have you see this section of the Installation section of the Admin Manual: Installation on Linux — Nextcloud latest Administration Manual latest documentation

I suspect you’re using a subdirectory installation, but you didn’t post your config so unclear.

Zorglube · March 27, 2026, 5:28pm

Hello,

The message is

OCS provider resolving

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

After reading the documentation, I can confirm that I’m using a sub directory, not on NGINX.

But in the .htaccess :

there are two sections concerning the mod_rewrite
a comment request not to modify one of those sections

After all I try to modify the file, but the error remain.

Should I replace all the lines concerning the mod_rewrite by the commands of the installation guide :

<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]
</IfModule>

Zorglube · March 28, 2026, 5:41pm

Hello, I found two .htaccess files :

at the root of the web site
at the root of the data directory

wich one should I change ?

Zorglube · March 29, 2026, 7:39pm

Hello,

After installing another instance of Nextcloud from scratch, I finally found the solution.

At the end the .htaccess file stored in the root directory of the site, let’s say /var/www/nextcloud, the lines ErrorDocument and RewriteBase refer to /nextcloud instead of /.

I think it’s because I assigned the value /var/www/nextcloud/ to the DocumentRoot and SetEnv directives in my configuration file.

Whatever the reason, the directive AllowOverride in now assigned to All without problem.

system · April 6, 2026, 7:39pm

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.