files? how many are there?Also do I have to change the network mode from however_i_named_the _network to bridge in both containers? airsonic and letsencrypt
Do I need the arguments? --cap-add=NET_ADMIN --network however_i_named_the _network ??
ok let's try to get it sorted out.
After successfully setting up the letsecrypt docker (including the extra arguments --cap-add=NET_ADMIN --network networkname) and getting the certificate for your duckdns subdomain and the extra sub-subdomains, you don't have to change anything in the letsencrypt container or on your ports.
Also you set up the airsonic docker called airsonic and added the extra argument --network networkname. At this point can you access the gui of airsonic locally (http://ip_of_your_omv-machine:4040 (standard port)?
Now you need to have a file in the Appdata/letsencrypt/nginx/proxy-confs folder which is named airsonic.subdomains.conf (the docker user specified by the entered puid and pgid needs read permissions to that file)
server {
listen 443 ssl;
listen [::]:443 ssl;
# in the next line change the name before .*; to whatever sub-subdomain you want to use and you have a valid letsencrypt cert for
server_name airsonic.*;
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_airsonic airsonic;
proxy_pass http://$upstream_airsonic:4040;
}
}after that restart the letsencrypt container, clear your browser cache and try your domain again.
