After a reboot Hassio stopped working - web interface not coming up

Installation Home Assistant OS
1

Hello all - I have a daily cron job that performs a full system reboot. I configured it to deal with HUSBZ Zigbee service becoming unresponsive randomly. Been working perfect for about a year or so.

This morning none of my lights were working based on the node-red flows. Logged in via ssh and checked docker and that seemed fine:

commandcontrol@haunit:~$ sudo docker ps
CONTAINER ID        IMAGE                                    COMMAND                  CREATED             STATUS              PORTS                                                                NAMES
d588ad68e29f        hassioaddons/node-red-amd64              "/init"                  6 minutes ago       Up 6 minutes                                                                             addon_a0d7b954_nodered
ecf73fb022cb        homeassistant/qemux86-64-homeassistant   "/bin/entry.sh pytho…"   17 minutes ago      Up 50 seconds                                                                            homeassistant
d753e1ebaff1        homeassistant/amd64-addon-samba          "/run.sh"                17 minutes ago      Up 17 minutes                                                                            addon_core_samba
6cd2c0ad87a8        homeassistant/amd64-addon-mosquitto      "/run.sh"                17 minutes ago      Up 17 minutes       0.0.0.0:1883-1884->1883-1884/tcp, 0.0.0.0:8883-8884->8883-8884/tcp   addon_core_mosquitto
cb9159cef318        hassioaddons/sonweb-amd64                "/init"                  17 minutes ago      Up 17 minutes       0.0.0.0:9541->9541/tcp                                               addon_a0d7b954_sonweb
6ec4106f336e        homeassistant/amd64-hassio-supervisor    "python3 -m hassio"      37 minutes ago      Up 45 seconds                                                                            hassio_supervisor

But the hassio web interface would not load.

Checked logs and it’s just scrolling the following:

Dec 20 10:10:28 haunit hassio-supervisor[6741]: #033[32m18-12-20 15:10:28 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/config access from a0d7b954_nodered#033[0m
Dec 20 10:10:28 haunit hassio-supervisor[6741]: #033[31m18-12-20 15:10:28 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/config: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]#033[0m

I think one error is related to node-red. I can reach the node-red interface, log in and all, but it can’t reach hassio.

Home assistant connection failed with error: Connection to home assistant could not be established with config: http://hassio/homeassistant <password redacted>

I’ve restarted several times and went through everything in this thread, but still can’t get the web interface to load.

  1. I did not upgrade the system or OS.
  2. I did not upgrade hassio.
  3. I have not modified the configuration in over a month.
  4. I don’t have the discovery.json he’s describing in that thread.

Other than the errors above, I don’t have anything else pointing to a problem. I don’t know what else to look at.

Is there a way to turn on the ssh for hassio via docker commands on the host OS? I have ssh addons installed, just can’t enable them.

hassioaddons/ssh-amd64                   3.0.1               e64bedf54cd9        5 months ago        227MB
hassioaddons/ssh-amd64                   latest              e64bedf54cd9        5 months ago        227MB
homeassistant/amd64-addon-ssh            3.7                 c913782a70b3        6 months ago        68.3MB
homeassistant/amd64-addon-ssh            latest              c913782a70b3        6 months ago        68.3MB

For awareness, I have installed hassio on Ubuntu, using this guide: https://www.home-assistant.io/hassio/installation/ … So right now I have ssh access to the host OS, not to hassio. I’m not sure if this limited ssh to the host OS prevents deeper troublshooting of hassio(?)

I’m running hassio 0.79.3

Any ideas?

Thanks in advance!

2

To add, port 8123 is not listening

commandcontrol@haunit:~$ sudo netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      3462/smbd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1155/sshd
tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN      6903/node-red
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      3462/smbd
tcp6       0      0 :::139                  :::*                    LISTEN      3462/smbd
tcp6       0      0 :::8883                 :::*                    LISTEN      1828/docker-proxy
tcp6       0      0 :::8884                 :::*                    LISTEN      1778/docker-proxy
tcp6       0      0 :::22                   :::*                    LISTEN      1155/sshd
tcp6       0      0 :::1883                 :::*                    LISTEN      1851/docker-proxy
tcp6       0      0 :::1884                 :::*                    LISTEN      1840/docker-proxy
tcp6       0      0 :::445                  :::*                    LISTEN      3462/smbd
tcp6       0      0 :::9541                 :::*                    LISTEN      1862/docker-proxy
3

Just showed up in the logs - randomly as I have tail -f running.

https://hastebin.com/aduqobinus.sql

4

The last entry in the log is referencing the custom hue component. You might try commenting out the hue entries in your config files, and renaming the hue.py file temporarily.

File "/config/custom_components/sensor/hue.py", line 7
    <!DOCTYPE html>
    ^
SyntaxError: invalid syntax
1 Like
5

Yep! and that was exactly it!

I think it may have been something that changed/updated in the hassio hypervisor the same night of the reboot and it broke the hue component?

Just noticed an update to the hue component as well on github: https://github.com/robmarkcole/Hue-sensors-HASS

Not really sure, but certainly odd behavior considering all that took place was a reboot. But everything appears to be back in order!

Thank you!