.well-known URLs, failed on: /.well-known/caldav

[rodinux]

Describe the bug

After upgrade I have a message .well-known URLs, failed on: /.well-known/caldav

Context

• Hardware: Old laptop or computer
• YunoHost version: 11.2.17.1
• I have access to my server: Through SSH | through the webadmin | direct access via keyboard / screen | ...
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: yes
  • If yes, please explain: I have the found the issue upgrading to nextcloud 29.0.2~ynh1 (stable branch) and have try the testing branch nextcloud 29.0.3~ynh1
• If upgrading, current package version: 29.0.3~ynh1 (was also with 29.0.2~ynh1)

Steps to reproduce

• If you performed a command from the CLI, the command itself is enough. For example:

  sudo yunohost app upgrade nextcloud
  sudo yunohost app upgrade nextcloud -u https://github.com/YunoHost-Apps/nextcloud_ynh/tree/testing --debug

• If the error occurs in your browser, explain what you did:

  1. Go to ' the admin settings parameters on nextcloud
  2. **See error 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 update *

This issue is related there :

nextcloud/server#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: nextcloud/server#45033 (comment)

So editing the file /var/www/nextcloud/apps/settings/lib/SetupChecks/CheckServerResponseTrait.php and change the line 64

 60         protected function getTestUrls(string $url): array {
 61                 $hosts = $this->config->getSystemValue('trusted_domains', []);
 62                 $cliUrl = $this->config->getSystemValue('overwrite.cli.url', '');
 63                 if ($cliUrl !== '') {
 64                         $hosts[] =  $cliUrl;
 65                 }

with :

 60         protected function getTestUrls(string $url): array {
 61                 $hosts = $this->config->getSystemValue('trusted_domains', []);
 62                 $cliUrl = $this->config->getSystemValue('overwrite.cli.url', '');
 63                 if ($cliUrl !== '') {
 64                         $hosts[] = rtrim(str_replace($this->urlGenerator->getWebroot(), '', $cliUrl), '/');
 65                 }

[rodinux]

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.

[SQLSlacker]

29.0.4 does not fix the issue for my server using NGINX with Nextcloud in a subdirectory

[rodinux]

The trailing slash is now not needed anymore, but sub directories are still not supported. But a PR is open, and awaits review/suggested adjustments: nextcloud/server#46255

[MCMic]

It seems the check expects a redirection to /<subfolder>/remote.php/dav, but what happens is a redirection to /<subfolder>/index.php/.well-known/caldav
Ref https://docs.nextcloud.com/server/30/admin_manual/issues/general_troubleshooting.html#service-discovery (see also the page about nginx configuration).

So

nextcloud_ynh/conf/nginx.conf

Lines 25 to 27 in 49c28ca

	# Let Nextcloud's API for `/.well-known` URIs handle all other
	# requests by passing them to the front-end controller.
	return 301 __PATH__/index.php$request_uri;

would need to be changed to match https://docs.nextcloud.com/server/30/admin_manual/installation/nginx.html#nextcloud-in-a-subdir-of-the-nginx-webroot

[ericgaspar]

@MCMic can you be more specific about what need to be changed?

our settings seem to be the same as suggested in the doc...

        # Let Nextcloud's API for `/.well-known` URIs handle all other
        # requests by passing them to the front-end controller.
        return 301 /nextcloud/index.php$request_uri;

[MCMic]

        location = /.well-known/carddav { return 301 /nextcloud/remote.php/dav/; }
        location = /.well-known/caldav  { return 301 /nextcloud/remote.php/dav/; }

I thought this part was missing, it’s missing in my local version, it seems to be there in the git version.

The file does not appear in the output of yunohost tools regen-conf --list-pending. Can I still regen it somehow?