Hi,
thanks for the quick reply!
That is the weird thing. The server name uses the wildcard.
This is my /appdata/swag/nginx/proxy-confs/nextcloud.subdomain.conf:
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name nextcloud.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_app nextcloud;
set $upstream_port 443;
set $upstream_proto https;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
proxy_max_temp_file_size 1024m;
}
}
Wich is exactly the same as my /appdata/letsencrypt/nginx/proxy-confs/nextcloud.subdomain.conf:
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name nextcloud.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_app nextcloud;
set $upstream_port 443;
set $upstream_proto https;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
proxy_max_temp_file_size 1024m;
}
}
If I deploy the stack with letsencrypt it works perfectly. If I deploy the stack with swag, I end up at the swag placeholder page…
Am I adressing the correct proxy conf?
The only difference I found is in the swag\nginx\site-confs\default:
In there is an additional line right on the top compared to the letsencrypt’s default:
error_page 502 /502.html
;
Thanks,
Flo