After update to Home Assistant Core Update 2023.12.3, can not access with homeassistant.local

Installation
1

I have Home Assistant running on an Intel NUC with HAos installed on SSD bare metal. It has worked flawlessly for a year that way and I always update to each new version as it is released. But after updating to the latest HomeAssistant Update 2023.12.3, I am unable to access my HomeAssistant on the homeassistant.local:8123 URL. I am able to use the lan IP assisgned though with no issues (ex: 10.1.1.22:8123). Although I am not saying the update was the culprit.

Can someone tell me how to determine or diagnosis what has happened and to get it back to working with the local HA URL?

Any assistance would be much appreciated…

Orgbrat

2

Same thing happened to me. I just did a hard boot of my system and it connected as it should. This happens occasionally, never understood why.

3

I have tried multiple hard boots with no success. HA is up and running it seems with no issues other than I can not access it thru the homeassistant.local:8123 URL.

I can access the HA instance on the NUC with the Lan IP:8123 from my Windows computer and everything in HA seems to work as expected. I have a monitor connected to the NUC and can see the HA CLI screen and it looks normal. I can run the command “ha core check” in the CLI screen and it returns “Command completely suxxessfully”

4

Probably mdns problem. Don’t use haos but mdns should resolve ha ip to homeassistant.local

5

One thing to try: ping homeassistant.local. That will at least tell you if its a mDNS issue.

6

Maybe due to this? Disabling new login page functionality - Home Assistant

Related: Disable user profiles on login screen by frenck · Pull Request #105749 · home-assistant/core · GitHub

7

By the way, avoid using .local domains for unicast resolution. They are reserved for mDNS and as of last year Android has been enforcing it.

8

Ok ping with homeassistant.local returns “Ping request could not find host homeassistant.local” but ping with the HA IP gets a valid reply

9

That would indicate it is an mDNS problem. Not sure what to tell you, other than it works on my system (so I guess there is hope). Maybe restart your NUC to see if things clean up.

10

You could try add something like this in your /etc/hosts file

your_ha_ip    homeassistant.local    homeassistant

and reboot it.

11

I have got a similar issue and I’m in panic as I have rental houses and they all have the same issues. I also update regularly and never had this issue. It’s about an update I have installed today, I think it was HomeAssistant Update 2023.12.3 indeed. After restart I cannot connect anymore. Nothing else changed.

Ping IP and ping homeassistant.local all fine. I can see it in the local network list. It has nothing to do with the bare metal. As I have the same issues at other locations as well.

If anybody could help how to connect again I’ll be very thankful. :pray:

12

Seems your issue is a little different in that you can ping homeassistant.local which means mDNS is working for you.

Do you mean http://homeassistant.local:8123 times out?

13

Exact same problem.

ping is working… I am completely sure that this 2023.12.3 update broken down something.

Is there a way to restore my last backup from console ?

Thanks

14

In my case I made a mistake in configuration.yaml… it had nothing to do with 2023.12.3 or any update…

I had to hook a monitor and keyboard to my NUC to recover the configuration.yaml.

15

I’ve been working for 4 days now to get my Home Assistant up and running again. Each time after the update 2023.12, the installation is no longer accessible. I’ve wasted months of my life on this misery over the past years. The downside is that I’ve become dependent on it because everything in the house is adapted to this frustrating system. Tablets on the wall that were supposed to control everything, and dozens of automations that are not easy to get rid of. It’s great for Frenck, who probably has good intentions but spends his entire day making constant changes. However, it’s terrible for people who actually use the system in their family/home.

I’m transferring various things to a server with Z2MQTT and Node-RED, hoping to get rid of this misery as soon as possible. I’m done with it!

16

I’ve been on vacation and lost access to Home Assistant once I updated to the newest version of home assistant and now I’m struggling to gain access again. I can see the device on my network, but I cannot access it in any way. It’s very frustrating, now that most of my apartment is automated through home assistant :-/

I can access home assistant on the observer channel either using homeassistant.local or the local ip on port :4357. It also seems 8123 should be running, but I get an error. Do anyone have an idea of how I can get into Home Assistant again?