NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
How do I figure out why port-forwarding is not working?
I have an Orbi setup and a RaspberryPi running Node-red in my network.
The Node-red server is listening on port 1880 using HTTPS.
Accessing the Node-red app works fine in the LAN, e.g. https://192.168.20.50:1880/
I've added a port forward for TCP/UDP from external 443 to internal 1880.
My Remote Admin for Orbi is set to port 4443 and UPnP is disabled.
I can still not access the Node-Red server from outside using my Public IP, nor through my no-ip DNS.
https://my.public.ip/ gives a network error.
Portscanning says port 443 is closed in my system.
Running latest firmware and have restarted Orbi multiple times...
Tried the Orbi logs but they don't really tell me much... :o
How can I track down why this is not working...?
8 Replies
Try a different port than 443/TCP .... well (un-)known feature of Netgear's newer (?) router implementation: 443/TCP won't be freed up even if no other services like remote access and the like are changed to other ports. Don't wonder a second if this feature has made it to Orbi, too.
Any progress on this?
awasen wrote:I have an Orbi setup and a RaspberryPi running Node-red in my network.
The Node-red server is listening on port 1880 using HTTPS.
Accessing the Node-red app works fine in the LAN, e.g. https://192.168.20.50:1880/
I've added a port forward for TCP/UDP from external 443 to internal 1880.
My Remote Admin for Orbi is set to port 4443 and UPnP is disabled.
I can still not access the Node-Red server from outside using my Public IP, nor through my no-ip DNS.
https://my.public.ip/ gives a network error.
Portscanning says port 443 is closed in my system.
Running latest firmware and have restarted Orbi multiple times...
Tried the Orbi logs but they don't really tell me much... :o
How can I track down why this is not working...?
awasen wrote:I have an Orbi setup and a RaspberryPi running Node-red in my network.
The Node-red server is listening on port 1880 using HTTPS.
Accessing the Node-red app works fine in the LAN, e.g. https://192.168.20.50:1880/
I agree with schumaku . Forward 1880 instead of 443 and put the ":1880" on the end of your browser string.
I'm sure you already checked that your Orbi is not behind another router. i.e. that the Orbi WAN IP is the same thing that you get when you do a web test for your public IP, such as https://www.whatismyip.com/
Thanks for confirming this "feature" that port 443 can't be forwarded. I just purchased the Orbi WiFi 6 System (RBK753) AX4200 and spent a few hours scratching my head, trying all the options in settings (disablinb uPnP, "DoS protection", etc.). That the Orbi refuses to forward port 443 makes sense now given what I've observed.
Luckily I've just reached 1 day of ownership so plenty of time to return it!
Austin_G wrote:Thanks for confirming this "feature" that port 443 can't be forwarded. I just purchased the Orbi WiFi 6 System (RBK753) AX4200 and spent a few hours scratching my head, trying all the options in settings (disablinb uPnP, "DoS protection", etc.). That the Orbi refuses to forward port 443 makes sense now given what I've observed.
Luckily I've just reached 1 day of ownership so plenty of time to return it!
Typically port 443 is reserved for HTTPS connections. Many browsers use that port for HTTPS. When your browser makes an HTTPS connection, a TCP request is sent via port 443. So switching to another mesh system may result in the same problem.
Usually the server and/or main router handles port 443. So it's possible whatever is in front of the Orbi is doing the blocking. Couyld even be your ISP. Are you not allowed to uise another port?
