-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Your web server is not properly set up to resolve "/ocm-provider/" warning after update to 27.1.4 #41762
Comments
Seems this is the cause:
Replacing that commmented rewriterule works for resolving the issue, if someone else can doublecheck I'd appreciate it. |
If you set your For any further context, see #40803 (and others). But the above should be all you need. |
After updating to Nextcloud Hub 7 (28.0.1), I'm still getting this error message (Your web server is not properly set up to resolve "/nextcloud/ocm-provider/" ) and the various suggested fixes do not appear to work, at least for me. |
for me, also on 28.0.1 I'm getting this error message |
This changed nothing and the error is still there. I am not sure why this was closed when there are multiple reports of this still being an issue. |
I just upgraded my NextCloud to 28.0.1 and i get the same error witch ocm-provider |
I fixed ocm-provider and a bunch of other faults being reported by editing one entry in /etc/apache2/apache2.conf
Replace |
@thisiszeev Changing AllowOverride from None to All fixed a bunch of warnings but not the ocm-provider or ocs-provider. Could you provide your apache2.conf and your nextcloud.conf to see if I can why my warnings won't go away. |
replacing AllowOverride None with All does not fix anything for me. |
@cliffordsnow If further help is needed with troubleshooting, pop over to the help forum and post the details about your installation and update method: https://help.nextcloud.com. That way your specific situation can be looked at closer. |
there are hundreds of posts in help.nextcloud.com reporting the same issue. Many of them suggest some changes in htaccess and others to the apache.conf file but still the problem is not resolved. That is the reason this still remains a bug and should be addressed as that. |
@Superyorch Please share the following:
Regardless of whether it resolves the current matter for you, it not being on indicates your environment may not be fully setup. That option being set is a fundamental element of installation and documented in the Admin Manual (https://docs.nextcloud.com). As it happens though, it must also be on for |
@joshtrichards Here is the info:
|
What happens when you visit the URL:
(With your domain of course) If it fails, please check your Apache error log and access log for clues. |
it fails with 404 not found. Apache error log shows nothing, access log only displays the GET instruction with the 404 result |
Bug description
The following warning is displayed post update to 27.1.4 in my Admin Overview page:
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 at it's documentation page ↗. On Nginx those are typically the lines starting with "location ~" that need an update.
As far as I can tell everything still seems to work, so it seems unrelated to #39549
Steps to reproduce
Expected behavior
No errors or warnings in overview
Installation method
Community Manual installation with Archive
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MySQL
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?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: