New Member
•
5 Messages
Port forwarding 443 gets Bad Gateway
I just switched to AT&T Fiber from Spectrum and it broke my home servers (most importantly, Nextcloud) because the fiber gateway behaves as a router. I've removed my old router from the system and I am trying to use the native features of the Gateway. I have set up Port Forwarding according to the instructions, and this works fine for SSH but I get Bad Gateway and Gateway Timeouts for port 443 when forwarding https.
I can tell that it is set up properly because:
- Port forwarding with SSH works properly
- the Nextcloud server works properly when accessed from the LAN, which bypasses forwarding.
- For a split second I was able to see the site load before the error, but it took > 30s to load (the site which is on the LAN.
For troubleshooting, I've already tried rebooting the gateway and doing a factory reset on the gateway. This is a critical problem for me and if I can't get it resolved I will be switching back to Spectrum.
Accepted Solution
benmordecai
New Member
•
5 Messages
1 year ago
I don't have wireless receivers and the port forwarding instructions do not work for port 443. The only solution I have found is putting the gateway in pass through mode and using a real router.
0
0
ATTHelp
Community Support
•
221.6K Messages
1 year ago
We're here to help with your port 443 forwarding concerns @benmordecai.
Do you have any wireless receivers? If yes, port 443 may be used by the wireless receivers. You can get past this by unplugging the wireless receivers, clearing out the port forwarding rules, and then putting the forward rule to your device.
You can learn more about port forwarding and how to set it up for your gateway.
If you still can't get it to work, please check to see if the port is open.
Let us know if this helps and feel free to reach out again if you have further questions or concerns.
Olajide, AT&T Community Specialist
0
0
JefferMC
ACE - Expert
•
33.2K Messages
1 year ago
@benmordecai , can you clarify exactly what you're trying to do when you get these errors? Are you:
1) Inside your local network, and
2) Using your public IP address or a DNS name that points to your public IP address?
0
0
benmordecai
New Member
•
5 Messages
1 year ago
Basically it does not matter what I am trying to do, as it is the Gateway's job to honor my port forwarding configuration, which it does not.
0
0
tonydi
ACE - Guru
•
9.9K Messages
1 year ago
🤦♂️
You post here looking for help and when someone asks you questions so they can give you help, you don't answer the questions and instead essentially tell them it's none of their business?
0
0
benmordecai
New Member
•
5 Messages
1 year ago
I've already solved my problem, no thanks to AT&T support (1.5 hours on the phone) and I have already read the forums where a bunch of people basically beg for answers on getting 443 to forward and only get robot responses about the generic port forwarding guidelines or other irrelevant info. No one understands the problems and they just try to come up with work arounds to cope with the fact that apparently forwarding port 443 does not work.
0
0
JefferMC
ACE - Expert
•
33.2K Messages
1 year ago
What an attitude. See ya.
0
0
benmordecai
New Member
•
5 Messages
1 year ago
It's really simple. Web server on the lan gets outside access by the router forwarding WAN traffic on port 443 to it. There is a setting for that in the gateway. That setting does not work. Whether I have a static IP, a domain, or an IP that gets periodically reassigned on the WAN side, it is still the job of the gateway to simply forward the port 443 traffic that I told it to. If it does not do so, it is a problem with the gateway.
I called the only people who have anything to do with the gateway and they can't do anything about it. Basically the only solution is to bypass the gateway and use a real router.
(edited)
0
0