Letsencrypt/swag ports not accessible

LSIO Discussion Container Support
1

I have set up a Debian-based virtual machine in proxmox to host my docker containers. The containers are up an running, but i am not able to forward some ports from this VM to the internet.

the VM is also running a simple web server. that i am unable to access, although the port mapping in the docker container is correct.
when i do an nmap on the host the ports 80 and 443 (and bunch of others that are used by some containers) are not visible. consequently i am not able to forward them to WAN and generate a certificate via the http method.

$ nmap 192.168.50.10 -Pn 
PORT     STATE SERVICE 
22/tcp   open  ssh 
25/tcp   open  smtp 
111/tcp  open  rpcbind 
143/tcp  open  imap 
587/tcp  open  submission 
993/tcp  open  imaps 
1334/tcp open  writesrv 
3000/tcp open  ppp 
5000/tcp open  upnp 
6789/tcp open  ibm-db2-admin 
8000/tcp open  http-alt 
8080/tcp open  http-proxy 
8086/tcp open  d-s-n 
8100/tcp open  xprint-server 
8180/tcp open  unknown 
8181/tcp open  intermapper 
8443/tcp open  https-alt 
9000/tcp open  cslistener 
9091/tcp open  xmltec-xmlmail

nmap started from within the vm shows the ports 80 and 443 listening

$ nmap localhost -Pn
PORT     STATE SERVICE
22/tcp   open  ssh
25/tcp   open  smtp
80/tcp   open  http
111/tcp  open  rpcbind
143/tcp  open  imap
443/tcp  open  https
587/tcp  open  submission
993/tcp  open  imaps
1334/tcp open  writesrv
3000/tcp open  ppp
5000/tcp open  upnp
6789/tcp open  ibm-db2-admin
8000/tcp open  http-alt
8080/tcp open  http-proxy
8081/tcp open  blackice-icecap
8083/tcp open  us-srv
8086/tcp open  d-s-n
8100/tcp open  xprint-server
8180/tcp open  unknown
8181/tcp open  intermapper
8443/tcp open  https-alt
9000/tcp open  cslistener
9091/tcp open  xmltec-xmlmail

i have no firewall running on proxmox. any idea what can be wrong with my setup?

2

you just need to allow 80 through your router/firewall and DNAT it to you docker host. You will not see port 80 running on our SWAG (formerly known as letsencrypt) container except when it’s actively trying to get certs.

If you’re unable to get certs, show us those errors.
make sure you also take a look at

3

thanks for the reply. of course the ports on my router are NATe, i’ve been using the letsencrypt container for serveral months on a different host. it just refuses to work after the migration.

but again, this was my stupidity. i was trying to generate certificates for subdomains that are not in the dns records of my domain…