NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Port Forward
1 TopicOrbi Port forwarding (443) Not Working
Hi all, I'm at my witts end in trying to implement a simple port forward on the Orbi. Effectively, I have Home Assistant (HA) running in my network, and have installed a SSL Certificate and implemented a DynDNS Hostname to access the Home Assistant device externally. This generally allows access via https://xxxx.duckdns.org:8123. 8123 being the default Port for HA. I have a portforward for 8123 port calls to be redirected to the server (a RPi) on 8123, and it works fine. According to http://www.canyouseeme.org, port 8123 is open. However, my workplace blocks port calls outside of standard port numbers. So 8123 is blocked, and so I thought I would use Port 443 (the standard SSL port), as the HA connection is using HTTPS (/SSL), and have the Orbi redirect external calls to 443 to port 8123 on the HA/RPi. This should allow me to head to https://xxxx.duckdns.org/ without a problem. The issue is, however, when I set the port forward rule -- it doesn't work. According to http://www.canyouseeme.org, port 443 is closed. Yet, when I do a Port Scan, using a program, on the server from inside the network -- Port 443 and 8123 are both open and fine -- Further, if I access the HA Server internally on https://xxxx.duckdns.org/ it works fine. Now what could be causing it? The only thing I can work out is that it is Orbi which is unable to receive and redirect the port calls from 443, which is why it's closed. Any suggestions on how I could overcome this? Thanks all! (p.s. upnp is off)Solved