Port forwarding not working correctly with new Archer GE800
I run a reverse proxy on my network that points to home assistant.
I got a new Archer GE800 and installed/configured it but the port forwarding is not working.
I am forwarding port 80 and port 443 but I cannot connect to my site. If I add the server IP as the DMZ the connection works fine, so I know it isn't an issue with my reverse proxy or DNS. The services are accessible through their ip:port on my local network so I know theyre working as well.
I looked through all of the settings and I dont see anything obvious as to why this isnt working. This setup was working fine with my previous router.
Can anyone help? To me it seems like ports aren't forwarding.
canyouseeme.org reports that ports 80 and 443 are indeed open, but I still cant reach my services. What is going on here? This really doesn't make sense.
I would say this is a problem with my setup but since putting the server in the DMZ makes it all work it has to be an issue with the router.
Thanks for the reply.
The port forwarding is for the proxy server. The DMZ is for the Nintendo Switch.
Here are my exact setup steps:
1. Configure and turn on port forwarding for three ports on my server at 192.168.0.28.
At this point port forwarding is working correctly
- canyouseeme.org says the ports are open
- The services using those three ports are accessible from inside and outside my network
- Doing tracert shows that the domain is resolved in a single hop, which is expected and correct.
2. Turn on the DMZ and point it to my Nintendo Switch at 192.168.0.14
At this point port forwarding is not working correctly
- canyouseeme.org says the ports are open
- The services using those three ports are NOT accessible from inside or outside my network
- Doing tracert shows that the domain is not resolved. The first hop is exactly the same and is correct, but then it attempts a second hop which times out.
- This behavior happens with any DMZ Host IP.
I'd rather not reset the GE800 if I don't have to but if that's the only thing to try here I could give it a shot.
I'm almost totally sure this is a bug in the firmware. It seems pretty cut and dry here; when the DMZ is off port forwarding works. When DMZ is on port forwarding doesn't work.