Been working on a problem with hassio that occurred last Wednesday. After a reboot of hassio virtual machine in VirtualBox my homeassistant installation didn’t come online (as in I couldn’t reach it via web-interface). Tried a proper shutdown and reboot a couple of times, but it didn’t help.
The first thing to do? Read the logs of course. But the only thing it said, was that it took longer than x second to set up this and that.
The second step to do? To the forum. Browsing the forum gave me the idea that it could have something to do with the homeassistant container not being able to reach the other containers.
So via VirtualBox UI I logged into the console of homeassistant. The UI was constantly bombarded with messages that port x entered blocking state, port x entered forwarding state, eth0 renamed from vethxxxxx etc. Searching the forum and googling resulted in more people having the same problem. For some people, it was fixed because they had a wrong configuration or they reverted a fresh update because of a bug. So tried all that with no luck.
Finally did a completely fresh install of hassio, without any luck, the same problem. And today I even fired up an old backup virtual machine which used to work, with the same result. No webinterface and no control over my devices.
I thought maybe it’s the network card so I switched from lan to wifi in virtualbox setup, again without any luck.
Since none of the hassio instances work I’m assuming something has changed in my host system (windows 10), the networksettings or virtualbox. But I have no clue how to validate or better fix it.
I’m hoping anyone has an idea where I can begin? I don’t want to reinstall my whole server, without first knowing if that’s causing the problem