Everything below is from and executed on the reverse proxy. This is the command I execute on the reverse proxy webserver:
Port 80 of the router is port forwarded to 81 on the reverse proxy.
And my http reverse proxy config:
server {
listen 81;
server_name domain.domain.com;
location / {
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_buffering off;
client_max_body_size 1024M;
proxy_pass http://192.168.2.151:81/;
proxy_redirect off;
}
location /.well-known/carddav {
return 301 $scheme://$host/remote.php/dav;
}
location /.well-known/caldav {
return $scheme://$host/remote.php/dav;
}
}
Do I miss something for the ./well-known?
The ./well-known stated already is needed as per installation instructions of nextcloud.
The webserver itself on the backend through the reverse proxy is working as expected. It went wrong from this part when creating the certificate from the reverse proxy server. When I do the webroot certificate creation on the backend server where the reverse proxy is sent too. It succeeds.