To get a valid certificate but not allow external access to the service see https://github.com/jwilder/nginx-proxy#internet-vs-local-network-access
- nginx-proxy must be publicly reachable on both port 80 and 443.
- Check your firewall rules/port forwards and do not attempt to block port 80 as that will prevent http-01 challenges from completing.
- For the same reason, you can't use nginx-proxy's HTTPS_METHOD=nohttp.
- The (sub)domains you want to issue certificates for must correctly resolve to the host.
- Your DNS provider must answer correctly to CAA record requests.
- If your (sub)domains have AAAA records set, the host must be publicly reachable over IPv6 on port 80 and 443.
- gibby/dummy - 738 KB image that just runs for ever by tailing /dev/null
- gibby/nginx-proxy:alpine - container is a fork of https://github.com/jwilder/nginx-proxy that supports VIRTUAL_IP for non docker services. PR here - nginx-proxy/nginx-proxy#1219
- jrcs/letsencrypt-nginx-proxy-companion:v1.11 - https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion
VIRTUAL_PORT: # Needed if more than 1 port is exposed VIRTUAL_HOST: # URL you want to use, must be publicly accessbile LETSENCRYPT_HOST: # URL you want to use, must be publicly accessbile