Home assistant not starting [bind failed: Address in use]

Hi all,

I have been running home assistant for about a year now without any problems, up to now. Hopefully someone can point me in the right direction.

I am running home assistant in a virtual environment on windows 10.

Since today, home assistant won’t start properly. It seems that home assistant core won’t start, see a screenshot of the console below:

The associated logging of the supervisor states a ‘Client timeout exceeded while awaiting headers’ exception while performing some get request

It seems that some port is already used? I assumed windows was already using port 8123 so I checked with

netstat -aon

I could not find any process using this port. I have restarted the pc and the virtual machine many times, each time with the same result. I even tried to start a new virtual machine from the most recent .vdi file. At first, home assistant seemed to work properly. However, after the first restart the problem again returned.

Does this look familiar to anyone? Does somebody have any idea of to resolve this?

Thanks in advance,

Stijn

I have the same issue. Just updated the operating system from 5.10 to 5.11. Could that have caused it? Did you update as well?

I just restored my snapshot from yesterday, now it starts again. But lost my work from the past 24 hours, and that was a lot. Spent all day modifying stuff…

@joro
Thank you for your response. I did not update from 5.10 to 5.11. I did install 2020.2.1 recently though. I have restored a snapshot via

ha snapshots restore [slug]

No difference though. I have also used two .vdi images from home assistant (one with 5.10 and one with 4.14. Both with the same problem. So it seems to be independent of the versions in my case.

I have the same issue and i just updated to 5.11 :frowning:

image

Repair of the Supervisor did the trick. Up n running aganin

Hi. How do you repair the Supervisor if HA won’t start?

FWIW my Pi 4 system didn’t start after HassOS 5.11 update. After leaving it overnight in that state though, power cycling it in the morning seems to have fixed the issue and it started right up.

That’s what I would like to know as well

SSH via Addon SSH

If HA doesn’t startup you can’t get to the addon… :upside_down_face:

ha yes :frowning: and well via the Proxmox console if using a VM

Thanks for the possible solution @esmeets. I tried this one, and unfortunately it did not resolve the problem for me.

I got home assistant working again. No clue what did the trick. I let the battery of my laptop completely drain and started windows and the virtual machine again. Suddenly it worked. Eventough I got it working I am now thinking about buying an intel nuc; I hope this would work more robustly than a virtual machine.