401: Unauthorized in Terminal Web, Node-RED, ESPHome, Frigate and others since last update

Not sure in which category this should be posted. I’ve updated to the latest version of HASS this morning (2024.10.2) and since, I’m unable to access ESPHome, Node-RED, Frigate or the Terminal web. All are giving me a 401: Unauthorized. I’ve tried to reboot Home Assistant without more success. Am I the only one with that issue? Not to sure what can be done as outside of the update, nothing changed in weeks. And as all add-on are affected with the same problem, I kind of think it is really related to the update.

I don’t see anything in the logs of the add-on that would explain the issue and the system logs is complaining about multiple things but it’s hard to tell if it can be related. So, before putting more effort into this, anybody else has those problems?

Thank you.

ehfortin

That is odd. I also updated this morning.

I don’t use Frigate or Node-RED. But I can access Terminal Web and ESPHome just fine.

Sorry, not an answer. Just an observation.

But it might narrow it down to the two I don’t use causing the issue.

Did try to disable all add-on except Terminal Web and still have the same result. Right now I only have ZWave, ESPHome and Terminal Web started. I put everything else in do not start mode and I rebooted the computer physically just to make sure. Still have the same problem.

The only log that seems related at the moment after trying to reach ESPHome is the following:

2024-10-12 11:21:16.607 ERROR (MainThread) [homeassistant.components.esphome.dashboard] Dashboard unavailable; skipping reauth: Cannot connect to host 127.0.0.1:63770 ssl:default [Connect call failed ('127.0.0.1', 63770)]

Even if I don’t see a similar message from other add-on, it may be a similar problem. But not being able to reach 127.0.0.1 should not be the issue. Maybe the port itself but… I get 401: Unauthorized which seems to indicate the system is reaching the port but is not authorized to log in.

Will try to log on the local console and see if I can find anything. It curious that it affect all add-on.

ehfortin

I’ve tried from the Home Assistant app and everything is working there. I returned to the laptop and deleted all cookies and it started working after that. Not sure why it was working on Home Assistant itself and not on the add-ons but it seems it was a cookie related issue.

Thank you @jeffcrum for confirming that it was working for you.

ehfortin

1 Like

I had the same problem today and deleting cookies was the correct fix for me too.