cancel
Showing results for 
Search instead for 
Did you mean: 

Can't forward port 443

kaeini
Tuning in

Hi, so I'm trying to migrate my reverse proxy setup from BT to Virgin Media. But no matter what I do, port 443 seems to always be closed.

I've managed to forward port 80 successfully but 443 seems to always remain closed.

I've tried:

  • Disabling the firewall
  • Disabling uPnP
  • Forwarding the port I used for port 80 to port 443.
  • Resetting the router
  • Using different external ports for 443.

Nothing seems to be working and I have no idea why. Guidance would be appreciated!

18 REPLIES 18

kaeini
Tuning in

image.pngimage1.pngimage2.png

Here's some photos of the problem. Again, stumped as to what it can be as it isn't seemingly a configuration issue at all (basically the same with the Hub 5 under modem mode and a OpenWRT firmware router handling the ports).

legacy1
Alessandro Volta

Connect PC to the hub in modem mode and run Wireshark when you scan for the port 443

Its possible VM ACL the port 443 by mistake when they did 445 

---------------------------------------------------------------

Screenshot_20240722_092222.pngScreenshot_20240722_092728.png

Filtering out port 443 in particular during the lets encrypt challenges appears to show that it's communicating with the port going by the information of the packet (SYN, SYN ACK, SYN). However, the port still appears to be closed online and the lets encrypt challenges still fail.

legacy1
Alessandro Volta

set the start filter with   

host 4.79.142.206

scan here

GRC | Port Authority, for Internet Port 443  

---------------------------------------------------------------

Ok so I think I know what's going on now.

Port 443 is open internally, a test on bridgemode confirms this.Screenshot_20240722_122430.png

But any external port it gets forwarded to remains closed (as seen here).

Screenshot_20240722_122544.png

So I do highly suspect that there is some interference going on in-between. Pretty convinced now that Virgin Media may have accidentally blocked internal port 443 from being routed to any external port.

legacy1
Alessandro Volta

My test it for outgoing GRC is incoming

why have to tested port 18443? you want 443 yes test with Port Listener with a PC to the modem no router

---------------------------------------------------------------

I tested it with 18443 because that's the port that my reverse proxy docker container has. 

I also forwarded 80 to 1880 for the same reason

Apologies for not clarifying. 

 

EDIT: Accidentally marked an answer as helpful while trying to scroll through the thread on my phone! Not sure how to undo it.

Hi kaeini,

Wondering did you get a workable solution in the end? have the same issue currently.

Thanks

Use hub in modem mode

---------------------------------------------------------------