Upgraded to latest hassio .84.4 now i can't bring up the web ui

Installation
1

i plugged it into a monitor to see where it is at and it loads, but the web ui doesn’t show up

I can ping it and I can ssh into it, but thats it, i can’t even migrade to the shared drive anymore on my mac, even though that was enabled

2

Any thing in the home-assistant.log in the config directory?

3

is ther a way to check from ssh? the shared drive isn’t loading

4

yep if you ssh to the machine, my config directory for example is in /home/homeassistant/.homeassistant

It holds all the YAML files etc and if local the database. look for a file called home-assistant.log. If you restart the HA services whilst you tail -f home-assistant.log, you will see the log scroll infant of you whist it loads and hopefully the error.

EDIT: open two putty/terminal sessions so in one you can tail the log and the other you can restart the services.

5

I rebooted my machine and was able to get to the home assistant log

2018-12-21 15:33:07 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "ip_port". Check lines 74 and 78.
2018-12-21 15:33:10 WARNING (MainThread) [homeassistant.config] Incomplete core configuration. Auto detected elevation: 0
2018-12-21 15:33:18 WARNING (Recorder) [homeassistant.components.recorder.migration] Database requires upgrade. Schema version: 7
2018-12-21 15:33:19 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=86 from 2018-12-21 23:16:09.718203)
2018-12-21 15:33:21 WARNING (MainThread) [homeassistant.loader] You are using a custom component for sensor.sonarr_upcoming_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2018-12-21 15:33:21 WARNING (MainThread) [homeassistant.loader] You are using a custom component for sensor.radarr_upcoming_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2018-12-21 15:33:23 WARNING (MainThread) [homeassistant.loader] You are using a custom component for media_player.alexa which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2018-12-21 15:33:25 ERROR (MainThread) [insteonplm] An aiohttp error occurred: Cannot connect to host hub1:25105 ssl:None [Name does not resolve] with status 999
2018-12-21 15:33:25 WARNING (MainThread) [insteonplm] Connection failed, retry in 1 seconds: Hub1
2018-12-21 15:33:27 ERROR (MainThread) [insteonplm] An aiohttp error occurred: Cannot connect to host hub1:25105 ssl:None [Name does not resolve] with status 999
2018-12-21 15:33:27 WARNING (MainThread) [insteonplm] Connection failed, retry in 2 seconds: Hub1
2018-12-21 15:33:29 ERROR (MainThread) [insteonplm] An aiohttp error occurred: Cannot connect to host hub1:25105 ssl:None [Name does not resolve] with status 999
2018-12-21 15:33:29 WARNING (MainThread) [insteonplm] Connection failed, retry in 3 seconds: Hub1
2018-12-21 15:33:30 WARNING (MainThread) [homeassistant.setup] Setup of insteon is taking over 10 seconds.
2018-12-21 15:33:31 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 30 seconds.
2018-12-21 15:33:33 ERROR (MainThread) [insteonplm] An aiohttp error occurred: Cannot connect to host hub1:25105 ssl:None [Name does not resolve] with status 999
2018-12-21 15:33:33 WARNING (MainThread) [insteonplm] Connection failed, retry in 5 seconds: Hub1
2018-12-21 15:33:34 WARNING (MainThread) [homeassistant.components.remote] Setup of platform harmony is taking over 10 seconds.
2018-12-21 15:33:34 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform ring is taking over 10 seconds.
2018-12-21 15:33:35 WARNING (MainThread) [homeassistant.components.camera] Setup of platform ring is taking over 10 seconds.
2018-12-21 15:33:38 ERROR (MainThread) [insteonplm] An aiohttp error occurred: Cannot connect to host hub1:25105 ssl:None [Name does not resolve] with status 999
2018-12-21 15:33:38 WARNING (MainThread) [insteonplm] Connection failed, retry in 7 seconds: Hub1
2018-12-21 15:33:46 ERROR (MainThread) [insteonplm] An aiohttp error occurred: Cannot connect to host hub1:25105 ssl:None [Name does not resolve] with status 999
2018-12-21 15:33:46 WARNING (MainThread) [insteonplm] Connection failed, retry in 11 seconds: Hub1
2018-12-21 15:33:47 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 30 seconds.
2018-12-21 15:33:57 ERROR (MainThread) [insteonplm] An aiohttp error occurred: Cannot connect to host hub1:25105 ssl:None [Name does not resolve] with status 999
2018-12-21 15:33:57 WARNING (MainThread) [insteonplm] Connection failed, retry in 17 seconds: Hub1
6

A quick look at that and I think the top error is the first to look at. The one about the configuration.yaml lines 74 & 78.

Start there and see if a service restart fixes it after you have sorted the two lines.

7

genius! :wink: thank you sir, had no idea an invalid config would cause the whole thing to crash…

1 Like
8

Perfect! Glad to help :+1:

9

Always do a config check before restarting after a config change. The single most common thing to cause the frontend to not load is config errors.

1 Like