Hi, I have built a dedicated Home Assistant Raspberry Pi server. Everything went reasonably smoothly, bar the normal headaches associated with a new computer build. I now have the system up and running and hard wired to my network. I can ping my new Home Assistant machine at 192.168.3.143, but trying to open the web interface using that address has no effect. I have tried opening it via http://hassio.local:8123/, again to no effect. I have tried numerous web browsers, Chrome, Firefox, Chromium, Safari and numerous platforms, Windows, Mac and Android tablet. All that happens is the page times out (like there’s nothing there) and I can make no further progress.
So I’m officially stumped right at the start it seems. Why can’t I reach the web interface?
My Raspberry PI build is configured in such a way that I have it hooked up to a monitor via HDMI. When I look at the boot-up process, everything seems normal - and at the end of this I am presented with a login prompt. Do I need to login locally on the Pi somehow, before I can log in via the network?
I’m not sure this is valid any longer, I may be wrong, but I think it is now http://homeassistant.local:8123 or http://homeassistant:8123 if you have mDNS network issues.
Easier to access from the IP like Dave has mentioned.
You will be able to reach your installation at http://homeassistant.local:8123 (if your router supports mDNS, otherwise see below).
From here, you have two options - either configure your Home Assistant from scratch, or restore a saved snapshot with all its settings and add-ons that you saved in the past.
We used hassio.local in the past, if you have a system that is installed before this naming change, you might need to use hassio.local instead of homeassistant.local .
If your router doesn’t support mDNS, then you’ll have to use the IP address of your Pi instead of homeassistant.local . For example, http://192.168.0.9:8123 . You should be able to find the IP address of your Pi from the admin interface of your router. Installation - Home Assistant
As new user i have similar problem: yesterday i flashed 32bit Raspberry Pi 4 image several times for following reason. The installation went well. Network GUI is accessable with PC and Home Assistant for Android app, which automatically found its IP (MAC based reservation in router - every time the same 192.168.1.183. I was also able to get working my tuya based sockets through tha home assistent. Everything worked flawlessy until very first power off / reboot, every time. After that reboot I see through Fing app, that my device is online, it has the same IP. But no webgui at all: no http, no https. Home Assistant for Android also doesn’t recocnize it anyhow. Fing says that there are no ports open on 192.168.1.183.
It occured several times, both with wifi and ethernet. Always started after first reboot after initial setup.
Have you done something with Lets Encrypt?
Did you add port 8123 when trying to access HA.
Try with different browsers and be aware that the default protocol might be https and you have not configured SSL, so you have to make sure to add http.
Best to do this is with a browser and maybe with another one.
No i did not do anything related to Let’s Encrypt. I tried both https://192.168.1.183:8123 and http://192.168.1.183:8123 and the result was the same. I tried the browser at least through my Android phone and on my PC, but i’ll make extra check with all different browsers later again. But is there a command line way to make sure that the web interface is up and running?
If the Web interface is up and running, how to explain that FING app did not recocnized port 8123 as open on my HA?
Have you also not configured access from outside your network with DuckDNS?
Are you 100% sure that you are using the IP address of you HA and not from one of the tuya devices - or something else…
So yes, i’m almost sure, the IP is right. But when I run ha > supervisor info, the there it displays that IP is 172.30.32.2. I don’t know where it gets that IP from…
Also not that. I cave up yesterday and did new image flashing with balenaEtcher, made only the required onboardind during initial installation. Then without making anything else, rebooted (flashdrive with network configuration removed) and voila: again no access. So i don’t even get a chance to think about getting dyndns or encryption of remote access, it gets broken basically when doing nothing additional. For me it seems like it holds til the reboot all the settings in the memory and works, but it like does not save them anywhere and after reboot it does not find those settings and something just crashes and and will not run at all.
Docker. HA OS, HA Supervised and HA Container are using Docker container technologie, which also creates an internal network. The actual Home Assistant container should also bind to the host’s network, so port 8123 is reachable on the “public” ip of that host.
ERROR (MainThread) [supervisor.homeassistant.core] Home assistant has crashed!
error on log with timestamp outside my timezone.
In other part there is
ERROR (MainThread) [supervisor.homeassistan.core] Invalid Home Assistant config found!
message.
ha > core restart returns
Processing … Done.
Error: Unknown error, see supervisor.
I just can’t understand the reason, because before that critical first reboot, which messes everything up, i do not edit configuration.yaml manually in any way. It basically gets into such state after required onboarding + reboot. I really don’t see where myself could mess up on so early stage after installation.
But i need to specify: on those tries when i did set up my tuya devices and which started working also, i did not notice any changes or additional code appearing in configuration.yaml. It seems to stay just like it is from the beginning…
Among the HA command line, there is ha core check, maybe it reports the errors, possibly resulting from a truncated or otherwise f*cked up configuration.yaml.
Hi Maiko,
I am experiencing the same issue right now. The HA is starting, I can ping it, but web gui is not accessible anymore. This happened after a power blackout. Did you manage to resolve this issue?
Your best bet is to log in via SSH / Samba and read the log file. Likely HA is loading properly / the GUI due to some error which you should be able to find in the log.
