Access through either duckdns or local IP

Configuration
1

Hi,

Once upon a time I could access my home assistant either through https://MY.duckdns.org or through https://192.168.0.160:8123 when I was on my home network (as pointed out to me in this thread).

I haven’t used the local IP much since then, but lately I have not been able to. I have since made a fresh install on Raspbian Stretch Lite, but all the duckdns and remote access configurations have stayed the same.

Did I just miss something obvious? Did anything change, that I didn’t catch?

in my configuration.yaml, I have

http:
  api_password: !secret api_password
  ssl_certificate: !secret my_ssl_certificate
  ssl_key: !secret my_ssl_key
  base_url: !secret secret_base_url
  ip_ban_enabled: True
  login_attempts_threshold: 3
  trusted_networks:
    - 127.0.0.1
    - ::1
    - 192.168.0.0/24

I do suffer from occasional internet outages (more than is acceptable, but I won’t be able to change ISP for a while), so I would really like to have the option to still access through the local IP. Any suggestions would be welcome.

2

I have the exact same issue! Did you already manage to solve it?

3

What’s the exact error you get?

4

Sorry, no luck yet.

In chrome, when trying to connect to https://192.168.0.160:8123/ (my static IP for the Raspberry Pi running home assistant) I get:

This site can’t be reached
192.168.0.160 took too long to respond.
Try:

Checking the connection
Checking the proxy and the firewall
Running Network Diagnostics
ERR_TIMED_OUT

My best guess is that it has something to do with port forwarding. If I forward port external 160 to internal 160 (so I can access via ssh from outside home network), then I can no longer use ssh to the local IP even when connected to the home network.

Deleting the port forwarding for external/internal port 160, I can connect via ssh to 192.168.0.160 again. And if I delete my forwarding of port external 443 to internal port 8123, I can also connect to home assistant through https://192.168.0.160:8123/. But then I can’t access securely from outside, of course :confused:

5

In Chrome on Android it works, but in Firefox for Android I get:

Corrupted Content Error

The site at https://192.168.1.5:8123/ has experienced a network protocol violation that cannot be repaired.

The page you are trying to view cannot be shown because an error in the data transmission was detected.

6

Never heard of that. Did you try clearing the cache etc.? Or try to open it in a private browser instance (if that’s supported on android). Whenever I have trouble connecting to my HA if feels like the browser has cached something that’s out of sync. Maybe an expired cookie. Not sure though. So to verify it would make sense to try access with a “clean” browser.

7

Funny: opening the local IP in a private tab did the trick! So I just need to clear out the cache of the browser and it will probably work. Thanks for the tip!

1 Like