Issue Connecting Remotely

Configuration
1

Hi all,

I’m hoping that you can help me work out an issue that I’m having trying to access HA remotely. Effectively, I have both Duckdns and SSL (using Let’s Encrypt) installed successfully. However, it’s using the traditional 8123 port (i.e. https://xxxx.duckdns.org:8123/).

As my workplace blocks ports such as 8123, I wanted to get it to work just using https://xxxx.duckdns.org/ which I tried by setting up a portforward on my router for external IP with port 443 mapping to the HA (on RPi) on port 8123. As opposed to the previous port forward which was just 8123 straight.

However, since I’ve applied that setting, any attempt to go to https://xxxx.duckdns.org or even https://xxx.duckdns.org:443 times out.

Any suggestion as to what could be causing this?

Thanks!

2

Try setting your server port and base url.

server_port: 443
base_url: xxx.duckdns.org

Then access it at https://xxx.duckdns.org without a port number.

Have you set up port forwarding on your router to allow traffic from 443 to your RPi’s IP address? If not, you don’t really need to change your port in the hass config, you can just set up a port forward rule for source port 443 to destination (RPi’s IP address) port 8123.

3

I hadn’t tried that – I’ve just amended the configuration file to reflect the server_port as 443. Previously, I just had base_url: xxxx.duckdns.org:8123. I’ve deleted 8123 from that line and saved.

I already had Portforwarding from 443 (External) to 8123 (Internal). However, since I’ve changed the server_port in the configuration.yaml, I should also change the Port Forwarding rule to 443 (External) to 443 (Internal), right?

4

in configuration.yaml is 8123. The duty to forward port is the router.

5

To clarify and update:

  • I’m attempting to have external calls to 443 routed to RPi’s Port 8123 (which is HA).
  • I’ve setup a Port Forwarding rule for 443 -> 8123.
  • In configuration.yaml I’ve set the server_port: as 8123
  • According to http://www.canyouseeme.org/ Port 443 is still blocked, and accessing the server by https://xxx.duckdns.org external results in a page timeout. Yet, internally it works fine.

I am assuming this is a router issue, as a port scanner is showing both 443 and 8123 on the RPi as open. So will see if I can get support for the router (Netgear Orbi), and then will advise if this fixes it.

6

Do you need to reboot your router for port-forward changes to go into effect?

As long as server_port is set back to 8123, the port forward rule of external 443 going to RPi 8123 should be correct.

7

Turns out the culprit preventing incoming 443 connections was the ISP. I’ve since fixed that (through the ISP’s control panel), and it is working all smoothly now.

Thanks Cwhits!