Properly resolving "/.well-known/caldav" or "/.well-known/carddav"

[coatmaker618]

I’m going over issues in my Nextcloud (18.0.4 – just updated) & this is one of the few issues left!

* 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/18/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/18/go.php?to=admin-setup-well-known-URL).

I’m using manual install on Ubuntu Server 18.04 (headless) with Apache2 & the NC home path is “/var/www/nextcloud”

the mod_rewrite section of my .htaccess file in

<IfModule mod_rewrite.c>
  RewriteEngine on
  RewriteCond %{HTTP_USER_AGENT} DavClnt
  RewriteRule ^$ /remote.php/webdav/ [L,R=302]
  RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
  RewriteRule ^\.well-known/host-meta /public.php?service=host-meta [QSA,L]
  RewriteRule ^\.well-known/host-meta\.json /public.php?service=host-meta-json [QSA,L]
  RewriteRule ^\.well-known/webfinger /public.php?service=webfinger [QSA,L]
  RewriteRule ^\.well-known/nodeinfo /public.php?service=nodeinfo [QSA,L]
  RewriteRule ^\.well-known/carddav /remote.php/dav/ [R=301,L]
  RewriteRule ^\.well-known/caldav /remote.php/dav/ [R=301,L]
  RewriteRule ^remote/(.*) remote.php [QSA,L]
  RewriteRule ^(?:build|tests|config|lib|3rdparty|templates)/.* - [R=404,L]
  RewriteCond %{REQUEST_URI} !^/\.well-known/(acme-challenge|pki-validation)/.*
  RewriteRule ^(?:\.|autotest|occ|issue|indie|db_|console).* - [R=404,L]
</IfModule>

I don’t know if this is related or not but I am currently accessing my path via https://nextcloud.mydomain.com/nextcloud rather than just https://nextcloud.mydomain.com as https://nextcloud.mydomain.com goes to the default Apache success page.

Thanks in advance!!

PS: There are a number of similar topics, but no relevant answers in those posts that I found

[Kent]

Hi.
I’ve got the same issue, did you ever resolve this problem?
When I look in the documents, if you have your nextcloud in a subfolder, you should add this behind the well-known lines.

e.g ^.well-known/carddav /nextcloud/remote.php/dav/ [R=301,L]

I did that, still didn’t work. So if you did get a solution, I would be very happy if you shared it.

[coatmaker618]

Kent,

I never did get it working. Honestly it’s been a while since I’ve looked at this…but if you ever find a solution, feel free to post it! I’d much appreciate it

[Adriaan_van_Vliet]

This is my Solution that worked for my.
If your working with Apache this should help place it in your vhost config.

        RewriteEngine On
            RewriteRule ^/\.well-known/carddav https://%{SERVER_NAME}/remote.php/dav/ [R=301,L]
            RewriteRule ^/\.well-known/caldav https://%{SERVER_NAME}/remote.php/dav/ [R=301,L]

if you doesnt use https use this

        RewriteEngine On
            RewriteRule ^/\.well-known/carddav http://%{SERVER_NAME}/remote.php/dav/ [R=301,L]
            RewriteRule ^/\.well-known/caldav http://%{SERVER_NAME}/remote.php/dav/ [R=301,L]

[coatmaker618]

@Adriaan_van_Vliet It looks like the difference between your entry and my entry is the “/” in the characters: ^/\. I’ll give that a try! Glad to have something concrete to try! With any luck, it’ll even work

[Adriaan_van_Vliet]

an did it work ?

[coatmaker618]

@Adriaan_van_Vliet sorry to leave you hanging. But I am trying to upgrade to NC 21 right now, and haven’t had a chance to try this. Currently stuck on a php error where I should see NC…

PHP error on upgrade via fresh install

I have Nextcloud 19.0.4.2 running in Ubuntu LTS 18.04. Since the new NC requires a new php, I thought it’d be easier to just create a new VM to install the new version on. So I created an Ubuntu 20.04 environment to install NC 21.0.0. Went through the manual install (since that’s recommended), stopped NC 19, moved the config et al over, and tried to connect. Below is the error I get on “sudo -u www-data php occ upgrade”. Any advice would be appreciated! {"reqId":"bE7KgaWhcexPBMBM3wE8","le…

[coatmaker618]

Just wanted to report back for the sake of closure. Upgrading ended up being a total nightmare (new php → new host OS → not a simple upgrade). So I ended up creating a new host for Nextcloud & just pointing to the same config files & database & data & all that. Apparently this issue fixed itself.

By that I actually mean two related but distinct things. When I first installed Nextcloud 21, I had a list of issues in the management tab, including 4 (not just the 2 I was used to) related to well-known. I ran a few of the fixes, but did nothing to address these specifically before going to bed. When I checked on it the next morning, all the “well-known” issues were fixed.

So I guess it’s solved? Not sure how (unless they made a change to the config file)–but I’m not looking a gift horse in the mouth!

Regardless, I appreciate the help & didn’t want to leave you hanging!

[finhjj]

Update for NC 21 (relevant for previous versions as well):

I had the same issue, but in my experience it’s always an issue of having the proper rewrite rules set in your server configuration. Adrian’s solution should work for any version; for SSL:

         RewriteRule ^/\.well-known/carddav https://%{SERVER_NAME}/remote.php/dav/ [R=301,L]
        RewriteRule ^/\.well-known/caldav https://%{SERVER_NAME}/remote.php/dav/ [R=301,L]

I have not been able to get webfinger or nodeinfo to work, however.

[schmudde]

There is some nice documentation on this in the official Nextcloud troubleshooting: https://docs.nextcloud.com/server/21/admin_manual/issues/general_troubleshooting.html#service-discovery

Unfortunately, I was not able to get this to work. I tried updating the .htaccess in all three places, but no luck.

• ./var/www/nextcloud/.htaccess
• ./var/www/nextcloud/config/.htaccess
• ./var/www/nextcloud/data/.htaccess

Any guidance on this?