Cannot connect to HA using app or browser

Configuration
1

Hi everyone!
I woke up this morning with my lights not automatically switched on. They get their daily command to go on via Zigbee.
I’m running HAOS for two months now on a dedicated machine using a SONOFF ZigBee 3.0 USB Dongle. I have a Zigbee switch as well so I tried that but no response to using that either. So I opened the HA app only to find out it can’t connect. Next I tried connecting via homeassistant.local:8123 from both my phone and my laptop. Even using two different browsers but still no connection. I restarted my HAOS and later also my router thinking it had to do with the IP-address but still no connection.
So I checked the forum and read about common causes. Did “ping homeassistant.local -4” forcing it to use ipv4 and to my surprise all looked well. The IP address is the same as it used to be so a common cause was ruled out. I am running PuTTY (an SSH client) to access HA and it also tells me all is up and running with the proper IP address. So I am clueless as to why I have no longer access via the app? If anyone is familiar with the issue it would be kindly appreciated. If I need to clarify the case please let me know!

2

What I failed to mention is that using the observer page (http://homeassistant.local:4357/) all seems well:

Home Assistant observer

|Supervisor:|Connected|
|Support:|Supported|
|Health:|Healthy|

3

Same problem here with my Rpi4. I then re-installed HomeAssistant on a Rpi5 (with an NVMe SSD) and used the latest back-up from yesterday, but the problem still exists.

HomeAssistant is visible on my router and I can access http://homeassistant.local:4357 but I get a blank page with http://homeassistant.local:8123/

4

have you guys tried to access using the ip-number ?

5

Have you cleared the browser cache?

6

Are you using entso-e? Another job is running for job group home_assistant_core / fails to start

3 Likes
7

Yes, am using that! Is that the cause?

8

Seems a lot of users have issues with it crashing HA, yes.

9

I just found out, it has indeed something to do with the ENTSOe integration (again).

I started my Rpi5 with a keyboard and a screen an disabled the ENTSOe integration.

10

Thanks, system is up and running again! Looked up the fix on Github and will see if I can edit the code so this won’t happen in the future! Did not expect this to be the problem!

1 Like
11

I got to the same conclusion. Entso-e! I think an addon should never block HA from starting.

12

Minutes after this comment an update was launched for ENTSO-e. I can access via browser again but my app is still unable to connect. A new installation off the app fixed that issue.