Hi Jan-Luca,
thanks for your quick reply.
I have checked that. It seems that the reverse proxy is/was correct. But i still get an error 404 on all nextcloud requests. it seems that this has something to do with the docker-container.
in Nextcloud container shell no request a logged in /var/log/apache2/access.log
But than I have detected that if I use the ip the access works:
10.100.10.105 - - [14/Jan/2022:14:31:26 +0100] "GET /nextcloud/status.php HTTP/1.1" 200 1695 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36"
but with the domain not?!
10.100.10.105 - - [14/Jan/2022:14:31:41 +0100] "GET /nextcloud/status.php HTTP/1.1" 404 1055 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36"
We have an alias dns entry for the server that is different to the ucs-hostname
with ucs hostname it works:
https://ucs.opc.local/nextcloud/status.php
but with public hostname it is not working any more:
https://ucs.<external-domain>.org/nextcloud/status.php
certificate (letsencrypt) is generated on external hostname.
I have done a test and config the alias hostname also in /etc/hosts - without success.
Where to look? Thanks for bringing me in the right direction.
Tobias