URL unreachable - but can login to console with root. How can I get this back online?

Tags: #<Tag:0x00007f7393554868>

Hi guys, I hope I’m writing this in the right section.

I run HomeAssistant in a VM on unraid. I had to do some maintenance on host and I believe the VM had a hard shutdown. When I turn it back on now, the VM posts, and it even gets to a point where it wants me to login (I’m talking about through the console). However I’m not able to reach HA’s URL, both the local IP and the cloud URL show as down.

I can PING my local URL.

I can even login to the console with ROOT… but I’m not exactly sure what do to in here. I tried doing a snapshot restore… but even once it completes, URL is down.

the last change I did was successfully upgrade the OS to 3.03 (or what ever the latest is) via the supervisor.

my samba shares show as online too… it prompts me for my creds, I can login and see 5 folders in the root. This means that HA is running and some of it’s addon too!

so how do I get the web GUI back online?

Since samba is online, what do the logs say? There’s probably a clue there.

Where can I find the logs?
I’m in the config folder… but I don’t see something named log.

the addons folder is empty.
I have a “share” folder too, that’s empty
SSL folder has my lutron stuff,
and the Backup Folder has a few TAR files.

from the CLI, I log in with Root.
then I do “core check”


I don’t think “core” is the problem thought (I’m assuming thats what I’m in) I’d liek to know the command to start the web server.

core is the webserver :slight_smile: . Check line 395 and 396 of your configuration.yaml, as indicated by your check.

1 Like

ok, I fixed line 395 & 396

and I found my homeassistant.log. file.

2020-04-20 23:08:46 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/automations.yaml contains duplicate key "entity_id". Check lines 395 and 396.
2020-04-20 23:08:46 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-04-20 23:08:46 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for circadian_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-04-20 23:08:51 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=269 from 2020-04-21 02:07:18.326256)
2020-04-20 23:08:54 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry  @gmail.com for icloud
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 216, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/icloud/__init__.py", line 116, in async_setup_entry
    with_family = entry.data[CONF_WITH_FAMILY]
KeyError: 'with_family'
2020-04-20 23:08:55 ERROR (MainThread) [homeassistant.components.unifi] Error connecting to the UniFi controller at 192.168.16.10
2020-04-20 23:08:55 WARNING (MainThread) [homeassistant.config_entries] Config entry for unifi not ready yet. Retrying in 5 seconds.
2020-04-20 23:08:58 ERROR (MainThread) [homeassistant.components.wled] Error fetching wled data: Invalid response from API: Error occurred while communicating with WLED device.
2020-04-20 23:08:58 WARNING (MainThread) [homeassistant.config_entries] Config entry for wled not ready yet. Retrying in 5 seconds.
2020-04-20 23:08:58 WARNING (MainThread) [hacs] Configuration option 'theme' is deprecated and you should remove it from your configuration, HACS will know if you use 'theme' in your Home Assistant configuration, this option will be removed in a future release.
2020-04-20 23:08:59 WARNING (SyncWorker_7) [amcrest.http] <None:None> Trying again due to error: ConnectionError(MaxRetryError("HTTPConnectionPool(host='192.168.16.241', port=80): Max retries exceeded with url: /cgi-bin/magicBox.cgi?action=getMachineName (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at ADDRESS>: Failed to establish a new connection: [Errno 113] Host is unreachable'))"))
2020-04-20 23:08:59 ERROR (stream_worker) [libav.tcp] Connection to tcp://192.168.16.241:554?timeout=5000000 failed: Host is unreachable
2020-04-20 23:08:59 ERROR (stream_worker) [libav.tcp] Connection to tcp://192.168.16.127:554?timeout=5000000 failed: Host is unreachable
2020-04-20 23:09:02 ERROR (SyncWorker_7) [homeassistant.components.amcrest.camera] Could not get Amcrest Camera camera attributes due to error: CommError
2020-04-20 23:09:05 WARNING (SyncWorker_26) [homeassistant.components.flux_led.light] Failed to connect to bulb 192.168.16.118, Server Cabinet LED
2020-04-20 23:09:06 WARNING (MainThread) [homeassistant.components.light] Setup of light platform flux_led is taking over 10 seconds.
2020-04-20 23:09:06 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform tplink is taking over 10 seconds.
2020-04-20 23:09:14 WARNING (SyncWorker_8) [homeassistant.components.flux_led.light] Failed to connect to bulb 192.168.16.119, Kitchen Cabinet
2020-04-20 23:09:23 WARNING (SyncWorker_25) [homeassistant.components.flux_led.light] Failed to connect to bulb 192.168.16.120, Basement LED
2020-04-20 23:09:33 WARNING (SyncWorker_36) [homeassistant.components.flux_led.light] Failed to connect to bulb 192.168.16.125, Dining Room Ceilling
2020-04-20 23:09:43 WARNING (MainThread) [homeassistant.setup] Setup of xiaomi_aqara is taking over 10 seconds.
2020-04-20 23:09:43 ERROR (SyncWorker_14) [xiaomi_gateway] Cannot connect to Gateway
2020-04-20 23:09:43 ERROR (SyncWorker_14) [xiaomi_gateway] No data in response from hub None
2020-04-20 23:09:53 ERROR (SyncWorker_14) [xiaomi_gateway] Cannot connect to Gateway
2020-04-20 23:09:56 ERROR (MainThread) [homeassistant.components.switch] Setup of platform tplink is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2020-04-20 23:10:03 ERROR (SyncWorker_14) [xiaomi_gateway] Cannot connect to Gateway
2020-04-20 23:10:13 ERROR (SyncWorker_14) [xiaomi_gateway] Cannot connect to Gateway
2020-04-20 23:10:23 ERROR (SyncWorker_14) [xiaomi_gateway] Cannot connect to Gateway
2020-04-20 23:10:33 ERROR (SyncWorker_14) [xiaomi_gateway] Cannot connect to Gateway
2020-04-20 23:10:41 ERROR (Thread-7) [pychromecast.socket_client] [Basement speaker:8009] Failed to connect to service Google-Home-Mini-9041265d751a35ca5f3a7ab1855065fc._googlecast._tcp.local., retrying in 5.0s
2020-04-21 00:04:14 WARNING (Thread-4) [pychromecast.socket_client] [Living Room:8009] Heartbeat timeout, resetting connection
2020-04-21 00:04:33 ERROR (Thread-4) [pychromecast.socket_client] [Living Room:8009] Failed to connect to service Chromecast-Ultra-de75e186204408e547733f221d50a745._googlecast._tcp.local., retrying in 5.0s
2020-04-21 02:13:27 WARNING (Thread-3) [pychromecast.socket_client] [Kitchen Speaker:8009] Heartbeat timeout, resetting connection
2020-04-21 02:13:52 WARNING (Thread-5) [pychromecast.socket_client] [Max’s Speaker:8009] Heartbeat timeout, resetting connection
2020-04-21 02:17:55 WARNING (Thread-7) [pychromecast.socket_client] [Basement speaker:8009] Heartbeat timeout, resetting connection

Not according to the first line of that log file.

Did you restart?

Or better yet run a config check before restarting?

so I’m not sure what I did.
But it came back online.

I did a few of the available CORE commands; rebuild, update. … and she finally came back up.