Need to reboot twice for Hass.io to start

I’ve seen this behavior consistently over the past months.

Every time to reboot my Ubuntu Server 18.04.1, the first time it comes back online Hass is unable to start.

Specifically, the homeassistant/amd64-hassio-supervisor keep recreating itself every approx. 6 sec. This can be spotted using ‘docker ps -a’.

I then reboot Ubuntu Server again and Hass.io starts the second time. Also, the first time I reboot it usually takes Ubuntu Server longer time to come back online and accessable using SSH.

What is causing this and how do I fix it?

I generally need to reboot on every update of HA. So this issue happens fairly frequent.

No one else experiencing this?

I’ve actually been experiencing the same thing, but I have Home Assistant in a Docker container.

The first time I get a 404 from Traefik (which is a reverse proxy in front of Home Assistant) even though docker ps will list my Home Assistant container as being up. In the Home Assistant log I don’t see a request coming in from the browser at all when I try to access the UI.

I than restart the container for a second time and now, it will indeed restart quite a bit faster , load the UI and thus have something like the following in the logs:

[homeassistant.components.http.view] Serving / to <local Docker IP>

I found a solution: https://github.com/home-assistant/hassio/issues/915#issuecomment-463573936