Visitor
•
3 Messages
Access internal web server from inside network
I have a web server inside my network. I've set up port forwards to access it from outside. I have no problem accessing the server on ports 80 or 443 (http or https) from outside my LAN by my domain name. I can no longer access the web server from inside my LAN (this changed in the last few days) by domain name. I have other port forward mappings and those work fine. This is only affects ports 80 and 443. If I set up forwards on my internal router to 80 or 443 on my web server from 81 or 444, I can access the webserver from inside the LAN via those ports (forwarded on the xFinity gateway to my router). So this is only affecting trying to forward 80 and 443 on the xFinity gateway and only in the last week.
XfinityRay
Official Employee
•
2.1K Messages
3 years ago
Hello, @user_sk16. Thanks for reaching out about the ports. I know this is an obvious step but we always ensure it has been done. Did you try deleting the ports and then resetting them up using the Xfinity app? I checked but am not seeing any issues with those ports at our Engineering level and they are not on the blocked list. Do you have them set for a Static IP?
4
0
Yeloshak
Visitor
•
4 Messages
3 years ago
Having the same problem here, started about the same time as OP.
All was working fine before (mid February)
It has been really hard to troubleshoot.
In addition to ports 80 and 443, I am also having trouble with IMAP port 587 on internal mail server.
Again, everything works fine from outside my LAN but trying to access the server from inside connections get no reply / timeouts.
2
glbarnes67
Visitor
•
2 Messages
2 years ago
I am having the same problem here. I'm not sure when it started but fairly recently. Spent hours trying to troubleshoot, everything points to the xfinity gateway.
From outside my local network or thru a VPN, ports 80 and 443 work perfectly.
When connected to my local network, I can access by private (local) IP but not via the http or https url.
I have found other ports to work from my local network, only 80 and 443 seem to be blocked. ping works with the correct i.p. address and no error is given, just no response.
I am not using Advanced Security as that blocks everything and does not allow port forwarding at all. I toggled it on and off anyway. Let me know if there is something I can try to resolve this issue.
5
user_f94f0c
Visitor
•
1 Message
2 years ago
Hello, I am having this problem as well. Port 80 is showing as open and I can access it from outside but not from behind the fire wall. I also when I forward port 8080 it still says closed when I check it. Thanks
0
0
CCMorgan
Gold Problem Solver
•
3.3K Messages
2 years ago
Hi all. For anyone continuing to experience this issue, please create your own public post with a summary of what's going on. Try to be as detailed as possible. Thanks!
0
0
Yeloshak
Visitor
•
4 Messages
2 years ago
So we need to start over again?
Someone pushed an update to the Xfinity router and broke packets that are going out and coming back to internal servers.
I have a dynamic DNS service that maps my domain name to my home. I make a request to https://www.myhouse.com. The DNS lookup goes fine and finds the external IP address to my house. My brower sends the request to the EXTERNAL_IP_address:443 and the packet never gets to my server.
It USED to work so we know we had port forwarding in the Xfinity router working correctly before.
It also works if I bypass the name lookup and just point my browser to INTERNAL_IP_address:443 so I know my web server is still working.
Which means it an Xfinity issue with something that changed recently...
2
0
smc99
Visitor
•
1 Message
2 years ago
Well, it's nice to know it isn't just me.
ALERT: I feel confident in saying that this is being done on purpose with ports 80 and 443. See the last paragraph for explanation.
After going through all that, I decided to see if the port was the issue. I simply changed the SSL port on my webserver to a port I had forwarded for my Minecraft server since it was already port forwarded. I shutdown my Minecraft server, and changed my website's SSL port to the same port. Low and behold, the website came up via DNS name from internal devices when specifying the alternative port. This is being done specifically to port 80 and 443 only. All other services work internally via DNS just fine.
1