I'm just starting out and installed the HA software on a RP5 32 Gb. Fresh install. I have the RP connected to a monitor and KB. The ha loads fine and the CLI loads. I can log into the Observer using http://homeassistant.local:4357 but I get an error trying http://www.homeassistant.local:8123. The page load just stops. I'm on a MAC OS 26.35.1 and I tried Safari, Chrome and Firefox. No address on wlan0 and the IPv4 address is 192.168.1.239/24 and it says that Safari cannot connect to the server.
You probably have network issues.
A full power down and restart of both your HomeAssistant server and the router is suggested.
First time onboarding also takes a while for eveything to unpack install and load. Are you sure you have left enough time for this to complete?
Is your device connected by Ethernet (recommended, or WiFi (not recommended)?
Are you on a VLAN? If so, is your Mac on the same LAN as the HomeAssistant server?
Thanks for the reply, I ended up re-creating the SD cards clearing the History in Safari and using the IP address instead of home assistant. I'm in business!
Hello,
I have the same problem. Observer is running and tells all is healthy, but neither supervisor nor the app can connect.
After the installation in December 2025 it worked perfectly fine. But after the latest updates I can't work with it anymore.
Ping and also name resolution is working fine.
I noticed, that HA is working after a fresh start, but only for approx. 30 minutes.
It reloads the whole services every few minutes and at some point completely stops working and behaves like described.
There is no routing between my PC and the HA.
Unfortunately I'm a newbie to this, so any help would be welcome.
Thank you in advance and have a nice day.
Hello,
Just updated to Core 2026.6.4, but unfortunately it didn't help with my issue.
The supervisor stops working after about 10-15 minutes. Only the observer is still working.
Still no ideas from anybody?
I would be thankful for any help.
Thank you ind advance and have a nice day.
So not relying on mDNS to find your server over the network.
When you are specific where it is located, you either find it or you don't. No hoping and praying!
No network, no access. You may find this statement obvious in hindsight.
Try accessing the HomeAssitant server via the current IP Address, and making your network more stable using a static IP address for your HomeAssistant server, instead of relying on mDNS discovery which can prove bothersome.
You can configure a Static IP address on your router in the DHCP configuration page, where probably your current setup has it dynamically allocated, (so subject to change), hence unable to be found if looking for it the last place you tried to access it, the most likely cause of these problems, usually encountered by newly configured systems.
The other issue is often the system updates needing to access files over the internet for downloading, or having downloaded them, unpacking and installing them, which can take a while on a slower system with limited resources, and the network being unavailable, so it is patiently waiting, and you are stuck, the HomeAssistant server network driver responding to pings, but the server in a partially updated state, waiting for network access. The solution here is not the sledge hammer approach of complete wipe and re-install, but have a look on your welcome screen and see if it is showing any errors, maybe doing a reboot of both the HomeAssistant server and your router if stuck for a few hours, and waiting for it to complete the update process. The rebuild sledge hammer approach will work for the first time you reconnect, but of course if your IP address changes due to dynamic reallocation, you are back to the very same issue of relying on mDNS to find the server across the network, and that is often unreliable, and your network problem will rear its' ugly head yet again.