Looking at the config options for this addon it seems subdomains should be supported via the customize variable, but I don’t see any examples of what to put in those files.
I’ve tried many variations so far in the /share/nginx_proxy_default*.conf and /share/nginx_proxy/*.conf files.
I get various error messages from 502 bad gateway, unauthorized, 404, and the most common, chrome’s generic domain server could not be found
@2carlos & @bestlibre, I’m able to get the NGINX addon working and can confirm that it routes my subdomains on port 80 correctly to the below duckdns subdomains, but I can’t get the Certbot addon working to get SSL going. What am I doing wrong???
starting version 3.2.2
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for vm-XXX.duckdns.org
http-01 challenge for XXX.duckdns.org
http-01 challenge for bi-XXX.duckdns.org
Using the webroot path /ssl/wk for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. bi-XXX.duckdns.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://bi-XXX.duckdns.org/.well-known/acme-challenge/Hh_4iB8Bwc2fvco2P8jNRSitUUCDDo1t6ZfZ1vnN4UU: Error getting validation data, XXX.duckdns.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://XXX.duckdns.org/.well-known/acme-challenge/l93aleOZrpn5_AxnnDf4KZy0XviYjrcr7KeCAOazFo8: Error getting validation data
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: bi-XXX.duckdns.org
Type: connection
Detail: Fetching
http://bi-XXX.duckdns.org/.well-known/acme-challenge/Hh_4iB8Bwc2fvco2P8jNRSitUUCDDo1t6ZfZ1vnN4UU:
Error getting validation data
Domain: XXX.duckdns.org
Type: connection
Detail: Fetching
http://XXX.duckdns.org/.well-known/acme-challenge/l93aleOZrpn5_AxnnDf4KZy0XviYjrcr7KeCAOazFo8:
Error getting validation data
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
hmm, Did you make sure to disable NGINX addon while you’re running the certbot addon? On my machine they’re both grabbing port 80, so I have to make sure NGINX is stopped before running certbot
Mind sharing how did you configure nginx? I wanna give it a try, I tried caddy and no luck for me. NGINX seems to be working fine however I can get it to work with subdomains.
The official NGINX addon uses the /share/ nginx_proxy folder, there I should just drop the .config files for each subdomain, is that correct?
Notice below how there’s only one path from the internet into the network of servers. That’s one way a reverse proxy helps. NGINX has additional options to increase security behind the scenes. it’s also nice for convenience as you can map subdomains such as: