Didn’t find a solution looking through similar posts that’s why I as with my specifics:
I’m using HA using either the http://homeassistant.local:8123 or for remote a https duckdns setup which works perfectly fine.
I now wanted to setup an Android tablet using fully kiosk which obviously can’t access HA by using http://homeassistant.local:8123
So I wanted to give it a go using HA’s fixed IP (set on the router) 192.168.178.79:8123 which ends up in an ERR_EMPTY_RESPONSE.
I can ping that IP and it’s also visible in the HA networks settings → IP-Information.
I tried to reach HA via it’s IP in Chrome, Edge and on my phone’s chrome browser too. same problem.
I can access HA observer using 192.168.178.79:4357 so the issue must be the IP plus 8123 port (my assumption).
I appreciate any idea.
HA running on Pi, router AVM Fritzbox 7590 (all up to date).
It was an assumption of mine as it can’t access it with the http://homeassistant.local:8123 and I read in a different thread that can happen and then to use the IP instead.
I had a lot of problems like this with DuckDNS, and finally gave up and subscribed to NabuCasa. Now, I have rock-solid access to my Home Assistant from anywhere. Plus a subscription supports Home Assistant development.
all done. Cache, Cookies. Even on devices that never had a connection on HAS yet I can’t access using the IP. Maybe someone else has an idea. thanks though @nickrout