Home Assistance VM Stuck at Login

Hi Everyone,

I am not sure what exactly happened here or how to fix this. I restarted Home Assistance OS from going to the supervisor section in the UI and then VNC is stuck in the following screen. I am running the VM in unraid server. Can someone please help what I should do?

ok…nvm…looks like it came back up. but these are the commands I ran.

root
ha start

why did this happen?

Same here except “ha start” isn’t recognized.

@war1000
This is expected. When HA OS boots, it will boot to the login screen like you were seeing. There is no need to login via the console for the web frontend to work. If you need to debug or make backend changes, then you can login using root like you did to manage HA via the console.
After updates, it can quite some time before the frontend becomes available again, so be patient and it should come back up. If not, the ha start command could work like it did for you :slight_smile:

@imola.zhp
The ha start command is deprecated but should still work. The new command is now core start. In order to run these commands you must be logged into the HomeAssistant OS console.

My understanding is the login is only displayed when you press enter.

This is displaying itself as the machine is trying to load. HA’s front end doesn’t load.

I tried “ha core start” as well, no luck. Home Assistant won’t load. It’s time for bed and half of the house won’t shut off. My better half isn’t amused.

Yes, the Login is only displayed after you do anything on the console.
You may want to check to see if you can ping the HA ip address. If not, you may need to fix networking on your VM or whatever you’re running HA on.

If you can ping it, have you tried accessing it directly using 192.168.0.x:8123 instead of a hostname like homeassistant.mydomain.org?

Now I’m getting this when I type in root.

Hangs up on loading Supervisor and then prompts login. I was able to login earlier. Looks like my system may be hosed, again.

For me it came back up after 2 reboots and waiting at the screen after entering root. then I typed “core start” and it said it was processed. after a few mins the web ui was live again.

I gave up and went to bed, after bringing in the ladder to reach an outlet way up in the bedroom on a ledge.

Woke up the next morning and hassio was running.

So this comes up but hassio still starts eventually in the background.

My Konnected stopped working months ago, this is happening and now I’m having to restart every day due to an issue with the USB ZWave/Zigbee stick.

I think my setup is about to go, might be better to start fresh then to keep chasing these issues. Thanks for the help!