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:
Nothing seems to be working and I have no idea why. Guidance would be appreciated!
test hub in modem mode no need for forwarding ports which if port 443 work its a hub router mode problem
UPDATE: Got a new router and flashed OpenWRT onto it. Still the same issue with every other port working fine.
Absolutely stumped, may have to call Virgin Media to see if they haven't intentionally blocked the port for some reason.
I would do but I use Linux primarily, not sure if it'd work under WINE. Every website I've checked has stated port 80 (and in fact any port I tested that hasn't been blacklisted explicitly by Virgin Media) has been forwarded properly. But 443 is not getting forwarded for some reason.
Thanks but what I don't understand is that this setup worked perfectly fine under BT.
But when I moved my server to Virgin Media, everything broke. It has just left me confused and wasting hours trying to troubleshoot what the issue is.
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).
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
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.
Ok so I think I know what's going on now.
Port 443 is open internally, a test on bridgemode confirms this.
But any external port it gets forwarded to remains closed (as seen here).
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.
Hi kaeini,
Wondering did you get a workable solution in the end? have the same issue currently.
Thanks
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.
The Port 443 error is faced while migrating to a reverse proxy setup from BT to Virgin Media. To solve the error and understand it in detail, check out:- https://certera.com/blog/what-is-port-443-detailed-guide-on-https-port-443/
When migrating your reverse proxy setup, it's common to encounter problems with port 443 — especially on Virgin Media’s residential broadband plans. The key issue here is that Virgin Media typically blocks incoming traffic on port 443 to prevent home servers, which can break setups that rely on standard HTTPS access. Check out this Blog - https://www.ssl2buy.com/wiki/port-443
