Web UI not accessible after restart

I am running Home Assistant + Hassio on a Raspberry pi.
OS Version: Home Assistant OS 6.4
Home Assistant Core: 2021.9.7

Today after a restart the Home Assistant core web UI never comes up (I get a “Unable to connect” error in the browser). I can get into Linux via SSH, and also interestingly whenever I restart HA core, I get a notification for one of my automation via the app on my phone (even though when I open the app it says it can’t talk to the server). To me this indicates that something is running just not the UI

So far, I have done a few things to try to pin this down:
ha core logs is just repeated copies of this:

[cont-finish.d] done.
[s6-finish] waiting for services.
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2021-09-24 21:10:35 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Node/Pro (' for airvisual integration not ready yet: Error while retrieving data: [Errno 113] Host is unreachable; Retrying in background

I was playing with python scripts at the time so I have commented out the python_script: line in configuration.yaml as well as renaming all of the python scripts so they are not .py files.

ha core validate looks clean to me

$ ha core validate
Processing... Done.

Command completed successfully.

I have restarted ha core several times with ha core restart including after making all of these changes. I have also restarted the entire machine several times.

$ ha core start --log-level debug
DEBU[0000] Adding homedir to searchpath                  homedir=/root
INFO[0000] No configfile found                          
DEBU[0000] Debug flags                                   apiToken=<removed> cfgFile= endpoint=supervisor logLevel=debug noProgress=false rawJSON=false
DEBU[0000] core start                                    args="[]"
DEBU[0000] [GenerateURI]                                 base=supervisor command=start section=core
⣾ Processing... DEBU[0000] [GenerateURI] Result                          uri="http://supervisor/core/start" url="http://supervisor/core/start" url(string)="http://supervisor/core/start"
⣟ Processing... DEBU[0021] Response                                      body="{\"result\": \"ok\", \"data\": {}}" fields.time=21.707543321s headers="map[Content-Length:[28] Content-Type:[application/json; charset=utf-8] Date:[Sat, 25 Sep 2021 04:27:21 GMT] Server:[Python/3.9 aiohttp/3.7.4.post0]]" received-at="2021-09-24 21:27:21.176758295 -0700 PDT m=+21.722503217" request="&{POST http://supervisor/core/start HTTP/1.1 1 1 map[Accept:[application/json] Authorization:[Bearer <removed>] User-Agent:[go-resty/2.6.0 (https://github.com/go-resty/resty)]] <nil> 0x2d51c8 0 [] false supervisor map[] map[] <nil> map[]   <nil> <nil> <nil> 0x241a0d8}" status="200 OK" statuscode=200
Processing... Done.

Command completed successfully.

Above I assume “No configfile found” is the command and not HA itself and so I can ignore it?

I didn’t see anything on the forums that seemed to cover this case, but I can’t find an error, so I don’t really know what I am looking for. Hopefully someone here can point me in the right direction. I am happy to provide more details, I just don’t know what else would be useful.


I ended up rebuilding. It wasn’t worth trying to track down what was going on.

For others ending up here, and perhaps this isn’t relevant, but I found that for some reason HA changed its interface’s IPv4 address.

Not sure why, but looks like static IP was disabled.

I found the actual IP using the HA cli with:
ha> network info

I was then able to load the web UI using that address, and reconfigured the network settings.