Open MCMic opened 2 years ago
I have a 404 on my .well-known
, so I guess I have the same problem
Can you both confirm no other app has a ./well-known path or permission?
I confirm, I've only Nextcloud installed on this domain name
(Also this bug breaks the automatic CardDav/CalDav configuration for clients)
always there in v28.0.1
Just upgraded to 28.0.3 and this popped up in my Nextcloud:
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation ↗. Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation ↗.
It seemed to work fine in 28.0.2 though.
Same here
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the [documentation ↗](https://docs.nextcloud.com/server/28/go.php?to=admin-setup-well-known-URL).
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the [documentation ↗](https://docs.nextcloud.com/server/28/go.php?to=admin-setup-well-known-URL).
It has been like this for a few versions for me.
Describe the bug
.well-known path are detected as handled by another app while there are not. So the app removes the well-known part from config.
Context
Steps to reproduce
When updating from 22 to the current one, I saw the warning saying another app is handling ./.well-known paths. Because of this, the .well-known paths were removed from nginx config. I think they were handled by nextcloud, looking at the log:
Expected behavior
.well-known redirections in the nginx configuration and no warning in Nextcloud admin page.