Suddenly I can not access forwarded public IP:port (web site) using Orbi.
Hi friends here
I've been using my Orbi RBR750 since last year, and I've set up a port forwarding to expose a hobby website from my PC (192.168.1.123), so for external users, they visit http://public_ip -> http://192.168.1.123.
It works well. However, since the last firmware upgrade, I found myself unable to visit https://public_ip under Orbi's wifi.
If I turn off wifi on my phone, I can still access http://public_ip using the mobile network.
If I turn on WIFI on my phone, I can only use http://192.168.1.123 to access my site.
It is pretty annoying as I WFH most of the time. Does anyone know how to fix this? Thanks in advance.
PS, I do have ddns setup but I track it down and found it does not work on the IP address level.
I've been using my Orbi RBR750 since last year, and I've set up a port forwarding to expose a hobby website from my PC (192.168.1.123), so for external users, they visit http://public_ip -> http://192.168.1.123.
It works well. However, since the last firmware upgrade, I found myself unable to visit https://public_ip under Orbi's wifi.
If I turn off wifi on my phone, I can still access http://public_ip using the mobile network.
If I turn on WIFI on my phone, I can only use http://192.168.1.123 to access my site.
It would be a useful experiment to manually load the previous firmware on the router and then quickly test NAT loopback (before the router has a chance to 'auto update' itself. If NAT loopback works as it used to with the previous firmware, then it would seem that Netgear has broken NAT Loopback with the firmware update.
Have you tested NAT Loopback using a device connected to the Orbi with Ethernet?
This issue would not seem to be connected to a possible DDNS problem. It would take more detail to understand that issue.
