search

jpstaub / reverse-proxy-ripcord

Reverse proxy with SSL capatiblity and test server for network configuration verification.
GNU General Public License v3.0
1 stars 2 forks source link

HTTPS gets Connection refused, but HTTP is fine #1

Open oneskysandy opened 5 years ago

oneskysandy commented 5 years ago

I deployed using docker-compose.web.yml, but I am getting "Connection refused" for HTTPS. I checked that the port is being listen to:

netstat -tnlp | grep :443 tcp6 0 0 :::443 :::* LISTEN 12702/docker-proxy

I also checked that the firewall is open:

lsof -i -P -n COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME ... docker-pr 12702 root 4u IPv6 53848 0t0 TCP :443 (LISTEN) docker-pr 12715 root 4u IPv6 53863 0t0 TCP :80 (LISTEN) ...

Firewall is disabled:

ufw status verbose Status: inactive

Any ideas why HTTPS gets connection refused? I am using AWS and the Security groups are all set properly with 80 and 443 open to all traffic.

Any ideas?

jpstaub commented 5 years ago

Hello,

The best thing to do would be to check the logs for containers:

It is likely you will see squawks related to IPv6 traffic. The containers were set up to handle IPv4. IPv6 appears to be the traffic of interest based on the details included in your post.

To handle IPv6 traffic see details related to that matter in the instructions published by the authors for the respective containers. You will need to modify reverse-proxy-ripcord to comply with the published instructions.

Regards, Jake