Open rodinux opened 3 days ago
Be careful, it seems not been a good idea to try this patch !
The issue will be fixed in version 29.0.4 While browsing the discussion, MichaIng reports that carddav and caldav work perfectly but it is the verification mechanism that bug, that is why the fix is not considered urgent and that it must be checked that it will not break something else. In short, modify by hand php files of such a complex application, I will avoid until the developer has not asked.
Describe the bug
After upgrade I have a message
.well-known URLs, failed on: /.well-known/caldav
Context
29.0.2~ynh
1 (stable branch) and have try the testing branch nextcloud29.0.3~ynh1
29.0.3~ynh1
(was also with29.0.2~ynh1
)Steps to reproduce
If you performed a command from the CLI, the command itself is enough. For example:
If the error occurs in your browser, explain what you did:
Your web server is not properly set up to resolve .well-known URLs, failed on: /.well-known/caldav For more details see the [documentation ↗](https://docs.nextcloud.com/server/29/go.php?to=admin-setup-well-known-URL).
Expected behavior
Keep the
/.well-known/caldav
working after an updateThis issue is related there :
https://github.com/nextcloud/server/issues/45033
After trying a lot of things to debug, like editing the nginx nextcloud.conf, I have understood my problem is because for subfolder installations because this will be checking for /subfolder/.well-known/carddav instead of /.well-known/carddav whereas applications using WebDAV will be querying for /.well-known/carddav without the subfolder.
So this issue comes with a nextcloud installed on a subpath URL like
https://mydomain.tld/nextcloud/
This post help me resolve the issue: https://github.com/nextcloud/server/issues/45033#issuecomment-2095742325
So editing the file
/var/www/nextcloud/apps/settings/lib/SetupChecks/CheckServerResponseTrait.php
and change the line 64with :