@eBoon wrote:
I am currently running Homeassistant inside docker on Ubunto 18.04. Yesterday, I did an upgrade from 0.107.7 to 0.108.3 and I have been down ever since. The upgrade seemed to hang and long story short, I ended up just giving up and restoring from my nightly full backup. I followed the guide (under PREPARATION) so install the base Homeassistant and then installed the Google Drive Backup addon to restore my snapshot. This seemed to mostly work - until I restart HomeAssistant. After a restart, the HA UI never comes back. When I look at the Supervisor log (ha su logs) I see something like this:
20-04-12 20:27:14 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-04-12 20:27:19 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize 20-04-12 20:27:19 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon 20-04-12 20:27:19 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-04-12 20:27:24 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize 20-04-12 20:27:24 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon 20-04-12 20:27:24 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-04-12 20:27:29 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize 20-04-12 20:27:29 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon 20-04-12 20:27:29 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-04-12 20:27:34 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize 20-04-12 20:27:34 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon 20-04-12 20:27:34 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-04-12 20:27:39 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize 20-04-12 20:27:39 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon 20-04-12 20:27:39 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-04-12 20:27:44 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize 20-04-12 20:27:44 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon 20-04-12 20:27:44 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-04-12 20:27:49 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize 20-04-12 20:27:49 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon 20-04-12 20:27:49 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].Not sure what is going on, but I’m guessing that there is a problem with the Docker setup. Looks to me like it’s expecting to HA at 172.30.32.1:8123 but it’s not finding it there? I don’t know - I’m certainly no Docker expert!!
Any advice for me - looking at the containers from within Portainer looks normal to me:
Thanks in advance for any help you can give me to steer me in the right direction!
Tom
Posts: 1
Participants: 1