Help Needed: Cannot access Home Assistant via IP or http://homeassistant.local:8123 [Solved]

[chungalunga]

What does your router say? Are you all really on the same network / subnet? I once left hotspot on my phone on and things connected in a way that produced very similar symptoms.

[einydor (Dor Einy)]

Having the same issue on X86 install
after updating HA, I don’t have access.

[swifty1101 (Jan)]

Same here. Working for years, now out of the sudden the local acces is gone:

What is working:

• home.mydomain.com:8123 from outside web
• Healtstate via local lan@ http://192.168.42.42:4357/
• ESPhome nodes internally, all automations running
• ssh command line
• SMB to file share

What is not working:

• Local IP connection @ https://192.168.42.42:8123/ (unable to connect screen)
• local domainname connection: https://homeassistant.local:8123/lovelace (unable to connect)
• iOS App from LAN: hostname could not be found

The only thing which I see to be changed is a new SSL certificate.
HA ist running on Proxmox in a Unifi network with Pihole DNS. So far it was no problem.

EDIT: Working again.

Solution: update HA to latest version 2024.05 to 2024.06. (via command shell)

[melton2]

has it been consistent since the upgrade?
i havent had an issue for years, and then the past few days i havent been able to login via my PC at all, and from my phone, randomly. but my tablet which is wall mounted doesnt seem to have an issue at all.

iv updated everything but to no success

[me.remedi]

Same here, I can’t log in to Ha anymore since the last update

[lordwizzard]

@me.remedi Could your issue be related to Alexa Media Player memory leak? either disable, roll it back or remove (Alexa Media Player) it may get you back on line.
For the HA 2024.10.1 update

[zgadson (Zach)]

Same here! I just updated the Alexa Media Player integration and now I can’t log in either. I can see that my Rpi4 is connected to my network, but nothing works to connect. How can I disable this without access to my HA instance?

[lordwizzard]

@zgadson @me.remedi
Boot in to safe mode
Read and follow these instructions:

PSA: Alexa Media Player v4.13.3 breaks all versions of Home Assistant

Alexa Media Player v4.13.3 puts home assistant into a boot loop due to a memory leak. Home Assistant v2024.10.1 will block this version of Alexa Media player. Also keep in mind, 2024.10.1 will block all versions of Alexa media player below version 4.13.3. Any version released by Alexa Media Player that is greater than 4.13.3 will not be blocked assuming they fix the issue. For all other users on older versions of HA, do not update to version 4.13.3 of Alexa Media Player. For more details see…

[goodniceweb (Oleksii Cherkashyn)]

Mac user here. I had a similar issue. Turned out to be browser related. Even through I granted Chrome the access to find devices on the local network, it just didn’t succeed. I had to switch to Safari, which worked fine for the homeassistant.local:8123 address. Just sharing my experience as might be useful for someone else.

[EduardoLev]

I was dealing with a similar issue immediately after switching to a static IP through the settings UI on a fresh HAOS install on a Proxmox VM.

Using ‘network info’ in the CLI, I noticed that the IP address had been set with a /32 CIDR suffix rather than /24. Changing it to /24 fixed the problem.

I hope this is helpful to anyone else who runs into this problem.