-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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]: After upgrade to 28.0.1 errors "Your web server is not properly set up to resolve "/.well-known/caldav". occur #42472
Comments
The check runs from your browser - can you check your browser console including the network tab while running a test? This is nearly always a configuration matter. e.g. #34737 (comment) One thing that stands out to me in your config:
Should that not be Likely unrelated but also of note:
|
@joshtrichards Thank you for your response! The fixes I did by your suggestions:
The Still unresolved: the log is still plagued ("30 errors in log") with:
and
I would appreciate if you pointed me in the right direction with those (I assume it's not in the scope of this report). The latter might be here? |
I just want to add that I actually got the very same curios situation on a fresh docker installation (Nextcloud Hub 7 (28.0.1)). 10 minutes ago there was the message "Your web server is not properly set up to resolve "/.well-known/caldav"" now it's gone. Also behind a reverse proxy (nginx). and I also have those message in the error logs. And - that's the reason I am searching about this error message - I can't share folders anymore. but only with Browsers on desktop. the Android app is still working. When I try to share I got the Message the message browser console "OC.MimeType is undefined" and the sharing dialog never appear. |
@Struppi FWIW I had this same issue, that was solved with a bug in a firewall rule that was not allowing the network to access nextcloud.com or apps.nextcloud.com. Fixed that issue, and everything magically started working. I had the same webdav errors. I also had errors of "internet connectivity check - unable to access nextcloud.com". |
I think I'm encountering a similar issue here. I upgraded from 27.1.4 to 28.0.1. today. Ran into an issue with the online updater that left the site on maintenance mode and hade to complete the upgrade via Looking at the console I'm getting a 404 on those links:
Nextcloud seems to be running well and logs are empty. I've run Edit: I've solved the error message after investigating a bit more. It seems that my /var/log/nextcloud.log file had its permission changed and was owned by root. With that said I still have 3 of the 4 errors above in the console (webfinger, nodinfo and .ocdata) |
@TheWojtek can we close your report? |
@kesselb Yes, this error is gone now. Thank you. |
Bug description
After upgrading the Nextcloud instance from 27.1.4 to 28.0.1, the server started throwing errors of:
Your web server is not properly set up to resolve "/.well-known/caldav"
Your web server is not properly set up to resolve "/.well-known/carddav"
While the server runs behind a reverse proxy, it has been configured properly for the past 3 years and has always passed the check with flying colors. It also actually does properly redirect from https://servername.com/.well-known/caldav and /carddav to https://servername.com/remote.php/dav from a browser or a https client (I am using Cocoa Rest Client on MacOS). There were never any redirection errors in this server anyway.
The upgrade was done to the exact steps of the "manual Nextcloud upgrade", which is how I always do the upgrades. The config file was transferred directly without any changes from 27.1.4 to 28.0.1.
Steps to reproduce
Expected behavior
Clean (error-free) Admin Overview as it was with the version Nextcloud was upgraded from, without falsely claiming the upgraded Nextcloud instance has configuration problems.
Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
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
Additional info
No response
The text was updated successfully, but these errors were encountered: