This isn’t directly after an update so I don’t know what caused it. I just woke up one morning and HA was down. Couldn’t SSH in either. Logged in directly on the machine (VM).
VM was created directly from the official image.
Any action I take fails. ex. supervisor info
result in Get http://supervisor/supervisor/info: dial tcp 172.30.32.2:80 connect: no route to host
and core info
results in Get http://supervisor/core/info: dial tcp 172.30.32.2:80 connect: no route to host
Any attempts to reload or start result in similar messages.
Is this the supervisor dead? I can’t tell what the issue is or how to resolve it.
Were you able to find a solution to this? I had the same problem. Running on VirtualBox on OSX. Finally gave up and completely rebuilt from scratch–not even using an old backup. A few days later, I shutdown the host computer, and here I am back to the same problem… Sounds like it might be related to the supervisor which automatically updates itself?
If I rebooted without removing the file, I was stuck in a boot-loop. I was able to restore a VM snapshot and investigated for hours.
Manually trying to restart the supervisor docker container would give the error above. It was telling to look at a running system and see the output of docker network list, docker network inspect hassio and docker container inspect hassio_supervisor compared to the same commands on my failing system.
The network inspect showed a latent “endpoint” related to a prior run of hassio_supervisor. I found no way to clean up the metadata, other than to delete the local-kv.db file.