Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. 
The Basics
- Nextcloud Server version (e.g., 29.x.x):
32.0.0
- Operating system and version (e.g., Ubuntu 24.04):
Ubuntu Server 22, NC Docker Compose installation, now AiO
- Reverse proxy and version _(e.g. nginx 1.27.2)
Traefik 3.5.3
- Is this the first time you’ve seen this error? (Yes / No):
No
- When did this problem seem to first start?
Years go ;-)
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Docker Compose, Nextcloud Community
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
The good old .well-known URL handling is not configured properly in the NC Admin panel.
I am not asking for help here, but want to document the solution that helped me:
This is a long standing issue for me and I was never able to fix it until I stumbled upon this thread .well-known seems to work but still a warning (using Traefik) and the answer of @Tim-Erwin .
Since I do not use labels for everything, but a good chunk of my Traefik configuration is in the dynamic-conf.yml, my solution differs in 2 ways:
- I configure the Redirect rules in the dynamic-conf-yml of traefik instead of labels in the docker-compos.yml
- I had to change the $$ to $ only in the replacement rules.
So in the end, the Middlewares in my dynamic-conf.yml of Traefik look like this:
nextcloud-secure-headers:
headers:
hostsProxyHeaders:
- "X-Forwarded-Host"
referrerPolicy: "same-origin"
nextcloud-redirect1:
redirectregex:
regex: "https?://([^/]*)/.well-known/(card|cal)dav"
replacement: "https://${1}/remote.php/dav/"
permanent: true
nextcloud-redirect2:
redirectregex:
regex: "https?://([^/]*)(/.well-known[^#]*)"
replacement: "https://${1}/index.php${2}"
permanent: true
nextcloud-chain:
chain:
middlewares:
- default
- nextcloud-secure-headers
- nextcloud-redirect1
- nextcloud-redirect2
And I point my docker-compose.yml Traefik labels just to the nextcloud-chain Middleware.
