I’m running a fresh install (VirtualBox on Windows 10 laptop) and seeing this issue after I login using root.
I have searched online extensively and all i’ve seen are such problem posts but no solutions in any of them. can someone please help?
Usually it just means that you tried to log in before the rest of the containers are up and running.
1 Like
i see. how do i get past it? once the VM is booted up, should i wait a while before logging in using “root” so containers are given ample time to start up?
What are you trying to do in the console? Most people have no need to log in there, and simply proceed to the web interface.
1 Like
i thought i had to login to be able to use the web interface. TIL. thanks! can’t believe i spent so much time on this.
It takes 20minutes Preparing Home Assistant WebUI. Console login will display error CLI not running. Go directly to your web url and continue the setup.
same error message. But I can’t get past the waiting 20 minutes message on the Web UI. Is there some way to get to the setup page when it is locked into the waiting 20 minutes message. (I waited an hour)
I also bumped into error “Home Assistant CLI not starting jump into emergency console”, tried over dozen times with fe wSD cards and 4.x, 5.x and 6.x HA versions. Browsed all over the net and this forum, then finally noted some post with unclear instructions to “log in with any user info…” So I tried in CLI screen prompt after the original error message and just wrote “login” and pressed enter. It proceeded right to HA welcome prompt showing the urls like HA url http://homeassistant.local:8123
Observer, mikä lie http://homeassistant.local:4357. So I entered HA url into my browser and it took then 30+ min to do rest of installations and asked to register. So some silly stuck which you can bypass, propably with many login kind of attempts
59 Likes
Thank you this worked! Lucky this came up near the top of google. appreciate you posting back here what you found.
Had to come here to say that ‘login’ worked for me too. Thank you
2 Likes
“login” also worked for me after waiting for installation. Just be patient and type login
Worked also for me. Big thanks!!
Have to use it also every time after manual shutdown to get to Home Assistant command line (screen attached). Doesn’t seem to impact the use of Home Assistant app/web UI.
WORKING AGAIN! - I got this issue recently after updating to the latest OS platform. Unplugged the network cable let it boot up showed the home assistant cli onscreen, connected the network cable and was able to access again.
Perfectly worked
How can I access the command line after the error message?
Thanks in advance
What IP address would you use? If the CLI starts properly you see the IP address HA is accessible on which is not the case with the above error message
I just had the same situation as you, my solution was to enter “login” after the warning line showed “[WARN] Home Assistant CLI is not running! Jump into emergency console…”. Everything is working fine
After some issue with my NAS attached to VMware ESXi, my HA OS (VM via vmdk of the site) doesn’t want to boot anymore.
Message is “CLI not runing! Jump to emergency console”
Also 2 messages about a service that cannot start (fsck and grow data), but I think these are related to the other issue.
Eventually it was possible to run the fsck manually, but this one cannot complete as it cannot modify some inode (#1707758) folder.
Upon checking docker, only the observer container is visible and no other docker containers. Although there seem to be more present in the docker folder, but as these are only GUIDS, I cannot be certain.
Unfortunately the backups in the backup folder are not a (full) HASSIO backup / snapshot and thus I cannot restore via new instance of HA OS.
Anyone any idea on how to fix HA OS so I can keep my history database? 
1 Like
I would hev spent hours on logs, this post is awesome!!
I have found the most important part o this solution is patience. Dome time I ave to repare several time and wait…up o 20 minutes