I can access port 8083 in the container, but nothing works on port 80…
Running sudo tcpdump port 80 and '(tcp-syn|tcp-ack)!=0' on the host shows the traffic hitting the host, but the same command in the container doesn’t work and no results are shown…
sudo tcpdump port 80 and '(tcp-syn|tcp-ack)!=0'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp6 0 0 :::80 :::* LISTEN -
tcp6 0 0 :::8083 :::* LISTEN -
Here’s the container…
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 10.112.106.223:8080 0.0.0.0:* LISTEN -
tcp 0 0 10.112.106.223:80 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:8081 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:8084 0.0.0.0:* LISTEN -
I was testing out HestiaCP, which is a VestaCP fork but I had a similar problem with VirtualMin… these panels use Apache and/or NGINX as selected but during this batch of testing, the control panel/web servers seem to pickup the IP of their container, hence this problem, rather than anything else, which I think is where the problem came from this time…
I’ve got another system running HA Proxy in a container which works out fine as I think it listens on all ports/addresses, as do email servers when forwarding ports 25 or 993 etc.