The URLs are used for the service discovery, which means that an application can use it to access calendar and contact data without knowing the final access path. This problem has been reported several times and it looks as if it has also been solved.
Same here. Nextcloud 19. I also was looking through those posts and the “redirects” mentioned in them as a solution did not work for me.
Though, it seems logical to me because after following the instructions in the documentation shown in the warning message about .htaccess setup redirecting well-known’s works fine for me just as it does for @74cmonty. In my browser I get
This is the WebDAV interface. It can only be accessed by WebDAV clients such as the Nextcloud desktop sync client.
So it seems like the problem is somewhere else maybe it’s a bug in the nextcloud.
same for me: NC 19.0.1 running as Docker container with traefik reverse proxy and letsencrypt SSL cert.
caldav/carddav work from internal network and internet but the error repaets all the time in the server log… any idea?
I was able to fix the issue. Here the solution for Traefik2.
Initially I had this rewrite rules assigned to my NC container
- “traefik.http.middlewares.nextcloud-dav.replacepathregex.regex=https://(.*)/.well-known/(card|cal)dav”
- “traefik.http.middlewares.nextcloud-dav.replacepathregex.replacement=https://$${1}/remote.php/dav/”
and fixed the issue by changing to this:
- “traefik.http.middlewares.nextcloud-dav.replacepathregex.regex=^/.well-known/ca(l|rd)dav”
- “traefik.http.middlewares.nextcloud-dav.replacepathregex.replacement=/remote.php/dav/”
for me it looks same but for NC health checks it makes some difference.
