Sorry I know (AKA learned) it’s an FAQ and already crawled the forums some hours (or days in total) in the meantime. Everytime I ended frustated and hoped it would be self fixing in the next release. But the problem persists for some updates now and the frustation at the moment lasts to issue this post ;).
I have two more or less straight forward installations, my private bookworm/nginx and one at at friend of mine who I support a little (bookworm/apache2). No proxy or docker setup underneath.
I am quite sure that I have set up the redirection for cal- and carddav correctly. My nginx:
location ^~ /.well-known {
location = /.well-known/carddav { return 301 /mycloud//remote.php/dav/; }
location = /.well-known/caldav { return 301 /mycloud/remote.php/dav/; }
However in both installations the Nextcloud Admin intereface claims a bad .well-known/…dav setup.
OTOH it seems to work on both setups as expected:
https://mittelerde.voll-tbl.de/.well-know/carddav
https://mittelerde.voll-tbl.de/.well-know/caldav
or is there something wrong here?
Crawling the forms I found following curl test:
root@www /var/www/medizintechnik # curl -Sv --fail -o /dev/null --GET https://mittelerde.voll-tbl.de/.well-known/caldav 2>&1 | grep -iE '^(> get|< (HTTP/|location))'
> GET /.well-known/caldav HTTP/2
< HTTP/2 301
< location: https://mittelerde.voll-tbl.de/mycloud/remote.php/dav/
and that is IMHO what should be expected isn’t it?
Why is the &$%§ Admininterface nevertheless still claiming that my setup is wrong where it is obviously ok?
TIA.