Accessing systems within my LAN via 443?

We can point you in the right direction to fix this error message, Johns2k.

Due to the nature of your concern, we recommend reaching out to the team at our paid service, HomeTech. They provide 24/7 support for a range of networking subjects and can help you find a resolution.

If you need help with anything else, we'll be here. Thank you for visiting the AT&T Community Forums.

Aminah, AT&T Community Specialist

I already pay for this service, why should I pay more to fix AT&T's issue.......

Port 443 is reserved for management use by the AT&T Gateway. If you need LAN access, you will need to use a different port number by your LAN device(s), or potentially use port 443 but setup port forwarding to translate an external port (e.g., 8143) to port 443, although I have not played with this.

By default, you cannot access any computer on your LAN from the WAN. What you appear to be doing is accessing the AT&T router admin page from the WAN, which by default is disable and for good reason. That prevents people from hacking into your router and likely disabling the firewall functionality it provides.

If you are wanting to access the router admin functions from the WAN, I would consider setting up a remote desktop app like teamviewer or anydesk to allow you to remote into a computer on your LAN and access the router's admin function from there.

If you are trying access a http/https server running on a device on your LAN, which appears is the case, you need to do as thechef1 suggests and setup port forwarding on the router. If you are not familiar with setting up port forwarding on a broadband router, call AT&T support and they should be able to help you (for free). Be cautious though and understand everyone on the internet will be able to get through so you should consider proper firewall settings and rules on the http/https server. A plain, unhardened http server installation is rarely secure.

I came here looking for confirmation that AT&T was blocking inbound port 80/443 traffic.  I have an application that needs you to point your domain name DNS to your WAN IP HTTPS.  That works fine but the traffic never hits my router so I suspected it was with the ONT.  It would be nice if AT&T would block external access to the management UI but still allow us to send HTTP/S traffic to an internal IP.

@Johns2k Have you added 443 to the firewall NAT/Gaming tab, pointing to the server that needs it?  The log seems to indicate that the port isnt being forwarded. If you are using IP Passthrough, you need to forward through your own router (which should have your public address).

@rafael_diaz Ports 80 and 443 are not blocked.  I run a web server on mine without issue, listening on 80 and 443.  My configuration is IP passthrough to my router, then port forwarded to my server.  There is a list of blocked ports somewhere, but from experience, 80 and 443 are not on that list.

The only two times I know the gateway blocks 443 is when:

• you have enabled remote access (even if the remote access port isn't 443) [and remote access still doesn't work the way you'd expect] OR,
• you have AT&T U-verse TV with a WAP for your wireless receivers.

Turning off remote access fixed my problem with 443 not being accessible from outside. Thank you @JefferMC