Had the same issue this week:
grid suddenly offline, after about an hour, the power went back on, HA did not reconnect.
Pulled the NUC, did a fresh install, nothing worked. Finally it seemed that the NUC got another IP adress from the router, and the port forwarding wasn’t set for that IP adress!!!
Check your router first if you get a situation like this!
I have had running on a pi 3. Aftersome time, I can’t connect to ha (it’s connected via WiFi). That’s using an Ipad via the IP/port 8123.
I get can’t connect every time.
But if I tryfrom my windows 11 pc using the same IP/port it connects fine. All devices connect to same WiFi.
Mac user here. I had a similar issue. With the new Sequoia release, there are more granular permissions should be granted to apps. 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.
Hello,
I’m new here, I was beginning my home assistant in my previous house, I run home assistant through home assistant green, I have nabu casa and always connect through home assistant via link that nabu casa displays.
Never had issues with it, but since I changed house, and have a new router, I can’t connect to my home assistant.
I need help, any suggestions?
Thanks in advance
I had the same issue today. Yesterday I was able to connect to my HA using ‘homeassistant.local:8123’, but today it is not working. I am able to access it by the IP Address, but not by local:8123 URL.
Reason for this is that last night I had changed the Host (Instance) name in ‘Settings > System > Network > Host name’ to something other than default ‘homeassistant’. The ‘homeassistant’ in ‘homeassistant.local:8123’ is the Host name defined in ‘Network’ settings. Change it to what you named your local Instance and it will start working again.
This solved my problem. I ran “ha core update”, rebooted and was able to connect on all my devices. Thank you!
same for me…
I have the problem maybe 3 times a week…with no solution…
Connecting via IP is working
Pinging is working
Safari is working
Chrome → DNS_PROBE_FINISHED_NXDOMAIN
Hi guys. A workaround si you can connect to HA with the IP but not with homeassistant.local:8123. Thanks to @shelend.
In terminal, type hostname
In HA, go to Settings → System → Network.
In “hostname” or “Home Assistant URL” field you have to put “http://[hostname]:8123”. ([hostname] need to be replaced by the hostname returned previously in terminal).
Now you cant connect through http://[hostname]:8123 in your favorite browser. This is not the standard homeassistant.local url but it may be better than nothing.
No relate but who run on VM just try to change network setup to Host-only - Adapter
I have a MLLSE mini pc with virtual disk but it doesn’t connect. I also fixed the port in the router. With lan cable http://192.168.1.236:8123
This is an interesting solution to a problem that’s vexed me for years now; I’m rather hopeful it’ll work, and be consistent.
Unfortunately I’m not terribly familiar with using the Terminal.
Also, when you say “in ‘hostname’ or ‘Home Assistant URL’ Field”…is that an either/or scenario? Or do I have to replace both.
I’m hesitant to experiment, lest I screw something up and my instance becomes FUBAR’d.
For me, this was specific to my Chromium browser and happened after the IP changed, meaning I could access via IP but not homeassistant.local. The fix was to clear host cache in chrome://net-internals/#dns.
I added a DHCP reservation in router settings to prevent this from happening again in the future.
I am also new with homeassistant. I tried what I saw here (checking https vs http, IP,etc).
I just want to share that what worked for me was connecting a keyboard to my rpi5 and:
Supervisor repair
Core rebuild
Core restart
After reading down the thread, your solution worked for me. Thank you.
I had just cleaned up my Mac, incl main browsers, so I figured that might be the culprit.
Opened a browser that didn’t get deep cleaned, logged in fine to HA (both URL & DNS worked)
Hope it can help someone.