I’ve had this exact same error and I am BRAND NEW to HA this is literally my first ever install on a VirtualBox machine on an i5 laptop that I installed a clean windows build on with nothing else running.
I’ve read through so much of this post to figure out what is wrong and none of this relates to me as I can’t even start HA for the first time after getting this error let alone change the number of things people are suggesting might be the culprit.
I really need advice as this Noob has no idea what to do and its quickly scaring me off my migration to HA.
And even though you may get the error, HA may still have started successfully.
What makes you say that Home Assistant is not starting?
Do you know the IP address of HA and tried to surf to http://a.b.c.d:8123 where a.b.c.d is the IP address?
Hi mchangsp
Thankyou for the helpful link. I had tried to navigate to the home assistant login using the 3 different methods outlined in the install guide eg. homeassitant.local:8123, homeassistant:8213 and finally my IP address http://192.168.x.x:8212 and none of these will bring me to the login screen.
However I have just watched the beginning of the video in the link you sent me and now understand that I can make some changes in the system before getting into the login screen (like set a static IP) which I will now try out tomorrow to see if this allows me to login.
Ok so I set up static IP addresses and tried the whole thing again using the new static ipv4 address that I created and still can’t reach the login screen. I’m not sure what I’m doing wrong. I think at this point I should probably just start a clean install, and if I’m still having the issue post a new thread to the ‘installation’ area of the forums.
I personally had this issue today, on a brand new install of Home Assistant OS in a fresh vm on Proxmox VE 6.3-3. I solved the issue by changing my “machine” from Q35 to i440fx.
I’m having the same error, except it’s showing devd[205] - this is the first time that I’ve installed HA on my computer, using VMware Workstation 16 Pro on a Windows machine. I’ve deleted the image, adjusted compatibility settings, changed network connections - all nada. If anyone finds a solution to this, please @ me. I can’t be too upset as it’s free and open source but I just spent 3 hours trouble shooting and can’t find a solution…
5.11 seems to be junk, updating to it broke my HA setup. I used the 5.9 image and all is good again even though this error was present in that version too.
I was actually able to fix mine - I needed to go into the VMware Virtual Network Editor and manually add the Network Bridge. Hope this helps anyone else struggling with this issue on initial setup in VMware Workstation 16 Pro.
As @frenck predicted the error message “bind failed” disappeared when I upgraded to supervisor-2021.02.11.
Average reboot times for me (from the event “Home Assistant stopped” to “Home Assistant started”) is 4 minutes. Before Home Assistant version 2012.02 it was 2 minutes.
Hi - I am still having an issue - but my setup is this way - I have noticed if you have the console open when you are booting up you can see the VM booting.