Have the same problem with VMbox on a Win10 machine. I have changed nothing and updated nothing. But today I wasn’t able to connect to HA and this error message came up when I tried to reboot it.
I am already using a wired connection, so I have no clue what to do. Most comments above seem to address wireless connections.
Any suggestions?
I just had the same. In my case (Win10 + Virtualbox) it was not Hassio related. I had to find issue with my local network (which was strage as I had internet connection on other devices). I did couple steps including rebooting all routers/aps, disabling dhcp on one of the routers (I had it enabled on two for some reason), flushing dnses.
At the end of that reboot of server and reboot for hassio and now it worked.
I have just started using Home Assistant with a Dell Latitude laptop with Windows 10 and VirtualBox 7.
I can confirm that VirtualBox bridged mode with the Wi-Fi adaptor is unreliable, it works sometimes and not others and can be slow. I spent several hours trying different settings etc. but nothing worked.
After reading this post, I turned off the Wi-Fi and connected the laptop directly to my router via Ethernet and the responsiveness is significantly improved and now it just works.
I have added the Home Assistant VM as a shortcut to the desktop and then using the Windows “run” command then “shell:startup” I have added it to automatically start on boot up which so far works. I then have Team Viewer for remote access to the PC.
The solution consist:
instead of Network > Adapter 1 > Bridged Adapter, choose:
Adapter 1 > NAT &
Adapter 2 > Host-only Network
I’m not convinced that that is the fix.
After upgrading virtualbox from 7.0.14 to 7.0.18 and installing a Windows 10 upgrade I found I couldn’t get in to homeassistant, trying to access http://homeassistant.local:8123 just got a DNS error that homeassistant.local couldn’t be found.
Tried a couple of things from this article as I saw the ‘failed to start network manager’, changing from Bridged Adapter back to NAT, thinking that the VirtualBox upgrade might have changed things.
But setting to NAT didn’t work, and it contradicts Installing Home Assistant/Hass.IO (4.11) on Windows 10 (VirtualBox/Virtual Machine) - Community Guides - Home Assistant Community (home-assistant.io) which says you should set it to Bridged Adapter not NAT.
I looked at some older HASS VM’s that I had and they were all set to Bridged Adapter so it seemed unlikely that that was the fix. Per the install guide I changed ‘Promiscuous Mode’ from Deny to Allow All, but my older VM’s all had Deny on them and they worked at the time.
I suspect the issue I had was with my router because even though my Mercusys mesh wifi was all showing as online, I couldn’t get in to administer it, and I couldn’t access my solar inverters on the local network.
Powered the router off and on again, rebooted the mesh network, shutdown the VM and restarted it and its all working fine - with Adapter 1 set to Bridged Adapter and configured to use my on board ethernet connection. I have my windows 10 host hard wired to the router; connecting via wifi I quickly found was flakey
I just wanted to add my solution to this mix. There are some solutions here, that I never really understood, so it left me a little confused.
I’m using VM Ware Workstation and Hassio
My cause was that the network bridge in the VMWare wasn’t connecting to my ethernet connection, even though it was set to automatic. I changed it, so that it had to call my ethernet driver. I think the issue was, that it was calling on the host only adapter, after some router issues.
My fix
Go to Edit > Virtual Network Editor
Use admin login to Change Settings
Find the Bridged type Network
Change Bridged to: to your physical ethernet adapter / your network card.
That helped me remove this message.
I’m running Home Assistant OS in Vmware Workstation Player and I have a similar but different issue. About a month ago, Home Assistant started loosing internet connection at random intervals from 24hrs to 5 days. I tried host shutdown then restarting the VM but I would get the same message as others observed during startup: Failed to start Network Manager.
The only fix I found is to reboot the host (Win 10) then start the VM. After reading this thread, I checked auto bridging and did find there was an extra adapter selected. I disabled it but I won’t know if that fixed it for a while.
Had the same problem and solved it by doing the following:
Run ip a to see the ethernet/wifi interface and also the network bridge
Check bridge device:
nmcli connection show
Update netplan if ethernet/wifi interface is wrong:
ls /etc/netplan/
and do sudo nano to the config file.
After updating the netplan, to apply it:
sudo netplan apply
To start the bridge:
sudo ip link set br0 up
Finally run ip a again and check the status of your bridge. Hope this helps!