.well-known seems to work but still a warning (using Traefik)

I have nextcloud up and running using Traefik as proxy. When I navigate to my-cloud.de/.well-known/caldav I get redirected to my-cloud.de/remote.php/dav - which I think is correct. However, in the settings I still get a warning

Your web server is not properly set up to resolve “/.well-known/caldav”.

Also, while I’m able to connect the calendar on my phone, it fails on OSX. I’m assuming, has to do with this “.well-known” issue.

There have been quite some questions around this topic in this forum, however, most are about configuring Apache, I’m using Traefik. The configuration is:

      - "traefik.http.middlewares.nextcloud-redirectregex.redirectregex.regex=/.well-known/(card|cal)dav"
      - "traefik.http.middlewares.nextcloud-redirectregex.redirectregex.replacement=/remote.php/dav/"
      - "traefik.http.middlewares.nextcloud-redirectregex.redirectregex.permanent=true"
      - traefik.http.services.nextcloud.loadbalancer.server.port=80

Do I have to set any headers, maybe?

i use “replacepathregex” instead of “redirectregex”:

nevertheless up to now i couldn’t get rid of the webfinger warning. but remote.php/dav seems to work well.

1 Like

Hm, this does not seem to change anything. The redirect still works, but the Warning is still displayed and I cannot connect my OSX clients.

Hey, since I read your name very often here and I guess you know what you are doing I wanted to ask if you were able to resolve the well known webfinger warning?
I can’t get rid of it sadly with traefik and nextcloud:apache image.
image
Currently my traefik lables in nc look like this:
I tried different suggestions from github but couldn’t make them work.

      - "traefik.enable=true"
      - "traefik.http.routers.nextcloud-app.entrypoints=http"
      - "traefik.http.routers.nextcloud-app.rule=Host(`example.secureserver.de`)"  #set url (cloud.example.com)
      - "traefik.http.middlewares.nextcloud-app-https-redirect.redirectscheme.scheme=https"
      - "traefik.http.routers.nextcloud-app.middlewares=nextcloud-app-https-redirect"
      - "traefik.http.routers.nextcloud-app-secure.entrypoints=https"
      - "traefik.http.routers.nextcloud-app-secure.rule=Host(`example.secureserver.de`)"  #set url (cloud.example.com)
      - "traefik.http.routers.nextcloud-app-secure.tls=true"
      - "traefik.http.routers.nextcloud-app-secure.tls.certresolver=http"
      - "traefik.http.routers.nextcloud-app-secure.service=nextcloud-app"
      - "traefik.http.services.nextcloud-app.loadbalancer.server.port=80"
      - "traefik.docker.network=proxy"
      - "traefik.http.routers.nextcloud-app-secure.middlewares=nextcloud-dav,secHeaders@file"
      - "traefik.http.middlewares.nextcloud-dav.replacepathregex.regex=^/.well-known/ca(l|rd)dav"
      - "traefik.http.middlewares.nextcloud-dav.replacepathregex.replacement=/remote.php/dav/"

@SimonWolf I’m afraid no. I could find the correct traefik settings for this yet. sorry.

I think the issue disappeared now.
I didn’t change anything but checked again if it’s working now and it seems to be working just fine on arm aswell now…
Do you still have any Traefik warnings about well-known?
(This is the configuration I am using)