search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
4.8k stars 959 forks source link

Cannot connect to host 172.30.32.1:8123 (Fails to boot sometimes) #224

Closed Fusseldieb closed 5 years ago

Fusseldieb commented 5 years ago

Hi, I've been experiencing this bug since I first knew Home Assistant (and it's still there with 0.80.3), so I'm not so sure if this can be resolved in HassOS, but following does happen sometimes when I restart Home Assistant:

Sometimes when I restart Home Assistant, it doesn't come up again. The page says Connection Refused and that's it. The first time this happened to me I almost freaked out, but now I know that a simple router restart fixes it. It's strange, Today it happened to me again and I wanted some concrete proof of what is happening so that I can submit this here.

So, the SSH Server still runs normally during this time, so there it is where it errored out: (Log was collected while HA was attempting to restart)

core-ssh:~# hassio su logs
Error decoding json invalid character '\x1b' looking for beginning of value: 18-10-21 06:26:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 06:56:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 07:26:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 07:56:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 08:26:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 08:43:56 INFO (SyncWorker_9) [hassio.docker.interface] Stop homeassistant/armhf-addon-mosquitto Docker application
18-10-21 08:43:57 INFO (SyncWorker_9) [hassio.docker.interface] Clean homeassistant/armhf-addon-mosquitto Docker application
18-10-21 08:44:00 INFO (SyncWorker_19) [hassio.docker.addon] Start Docker add-on homeassistant/armhf-addon-mosquitto with version 2.0
18-10-21 08:44:34 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services access from core_configurator
18-10-21 08:44:34 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/events access from core_configurator
18-10-21 08:44:34 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from core_configurator
18-10-21 08:56:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 09:29:43 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services/homeassistant/restart access from core_configurator
18-10-21 09:29:43 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-10-21 09:29:43 INFO (SyncWorker_15) [hassio.docker] Run command 'python3 -m homeassistant -c /config --script check_config' on homeassistant/raspberrypi3-homeassistant
18-10-21 09:30:30 INFO (MainThread) [hassio.homeassistant] Home Assistant config is valid
18-10-21 09:30:30 INFO (SyncWorker_6) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant Docker application
18-10-21 09:31:02 INFO (SyncWorker_6) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant Docker application
18-10-21 09:31:03 INFO (SyncWorker_8) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.80.3
18-10-21 09:32:50 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services access from core_configurator
18-10-21 09:32:50 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/services: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
18-10-21 09:32:50 ERROR (MainThread) [hassio.api.proxy] Error on API for request services
18-10-21 09:35:01 INFO (MainThread) [hassio.api.security] /homeassistant/logs access from core_ssh
18-10-21 09:35:13 INFO (MainThread) [hassio.api.security] /supervisor/logs access from core_ssh

Note: The HA log contains no error at all, just normal initialization things as usual. Note 2: A supervisor restart doesn't resolve it, I need to restart the whole router and then restart Home Assistant (again). Idea: Maybe this can be fixed by disabling and re-enabling the ethenet port on the RPi, if that specific error happens, causing the RPi to refresh it's IP, DHCP and whatnot. Would be great if someone could implement this on a newer build. I would for sure test it out.

mpgoebel commented 4 years ago

I just updated to .103 and am also seeing this. I haven't seen any issues with anything not working, just this error.

caiocaminoski commented 4 years ago

I have just updated to v103 as well and I am also getting this error...

sivastola commented 4 years ago

same here with 103. Is it possible this is related to the information about python on the ReleaseNotes page? It says support for python3.6 is deprecated and we should move to python3.7 I'm running HA on unbuntu 18.04 and here python3.6 is default. I don't like to change the default packages normally.

pricard32 commented 4 years ago

I've update python to 3.7 and the error disapear...!

soylant commented 4 years ago

also updated to 103 and having the same problem

fillilutten commented 4 years ago

Having the same problem running 103. Everything is running just fine though.

blamaz commented 4 years ago

Same issue here on 0.103.6. I'm having this error since a long time but everything seem to be running ok so I ignored it. Still hope someone figure it out.

JANogueira commented 4 years ago

Same here with HassOS3.8 + Home Assistant 0.103.6 and the errors are always having node red related messages:

20-01-15 14:30:06 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-15 14:30:06 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-15 14:30:06 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-15 14:30:11 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-15 14:30:11 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-15 14:30:11 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-15 14:30:14 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-01-15 14:30:16 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-15 14:30:16 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-15 14:30:16 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-15 14:30:21 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-15 14:30:21 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-15 14:30:21 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-15 14:30:26 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-15 14:30:26 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-15 14:30:26 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-15 14:30:31 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-15 14:30:31 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
mattclar commented 4 years ago

same problem here on 0.104.2

kic883 commented 4 years ago

Same here I am using Pi 4, with

My System log 


20-01-22 02:57:23 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:57:28 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:57:28 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:57:28 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:57:33 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:57:33 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:57:33 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:57:38 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:57:38 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:57:38 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:57:40 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-01-22 02:57:43 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:57:43 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:57:43 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:57:45 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
20-01-22 02:57:48 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:57:48 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:57:48 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:57:53 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:57:53 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:57:53 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:57:58 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:57:58 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:57:58 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:03 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:03 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:08 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:13 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:13 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:13 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:18 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:18 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:18 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:23 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:23 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:23 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:28 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:28 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:28 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:33 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:33 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:33 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:38 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:38 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:38 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:43 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:43 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:43 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:48 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:48 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:48 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:53 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:53 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:53 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:58:58 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:58:58 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:58:58 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:59:03 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:59:03 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:59:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:59:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:59:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:59:08 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:59:13 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:59:13 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:59:13 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:59:18 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:59:18 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:59:18 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:59:23 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:59:23 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:59:23 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:59:28 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:59:28 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:59:28 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:59:30 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
20-01-22 02:59:33 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:59:33 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:59:33 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-01-22 02:59:35 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
20-01-22 02:59:35 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.104.3
20-01-22 02:59:35 INFO (SyncWorker_9) [hassio.docker.interface] Cleanup images: ['homeassistant/raspberrypi4-homeassistant:0.104.2']
20-01-22 02:59:38 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
20-01-22 02:59:38 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
20-01-22 02:59:39 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request running
20-01-22 03:24:27 INFO (MainThread) [hassio.host.info] Update local host information
20-01-22 03:24:27 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-01-22 03:24:27 INFO (MainThread) [hassio.host.services] Update service information
20-01-22 03:24:27 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-01-22 03:24:27 INFO (MainThread) [hassio.host.network] Update local network DNS information
20-01-22 03:24:27 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-01-22 03:37:47 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
20-01-22 03:37:47 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
20-01-22 03:37:49 INFO (MainThread) [hassio.store] Load add-ons from store: 63 all - 0 new - 0 remove
20-01-22 03:46:43 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
20-01-22 04:29:24 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
20-01-22 04:37:47 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
bschatzow commented 4 years ago

Saw it again on .104.2. Had to reboot router to load HA. Any setting changes to make to avoid this issue?

mattclar commented 4 years ago

@pvizeli any chance we could reopen this issue?

sanderlv commented 4 years ago

Same here with 0.104.3

seems to have to do with node red

bschatzow commented 4 years ago

Just did a reboot due to a HACS update and it fails again. Rebooting router lets it load. This needs to be opened as many people are having this issue.

Count0Int commented 4 years ago

I am getting this error on 104.2. Causes my web interface to not be accessible, but automations are stillworking. Mine also seems to be related to nodered.

bschatzow commented 4 years ago

Are you saying if node red is not installed you don't have this issue?

Count0Int commented 4 years ago

Not sure if that would correct it, or if that is the actual problem, but there are mention of nodered in the logfile near the error. I will see if I can disable nodered from SSH and will report back. Here is a snippet of my logfile:

20-01-28 15:34:22 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-01-28 15:34:22 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-01-28 15:34:22 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-01-28 15:34:27 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-01-28 15:34:27 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-01-28 15:34:27 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

EDIT:

Stopping Nodered, and restarting HA didn't fix the web interface issue. Also noticed that I am not able to access the nodered website on 1880 either. Will see if any other web admin pages are broken as well..

Checked for other admin pages, the only one I could find that was installed was Tasmoadmin, and it is working fine.

To clarify, when I go to my default HA webpage, it does the redirect to .\lovelace and displays the error 'Unable to connect to Home Assistant' with the logo.

bschatzow commented 4 years ago

It looks like it is some type of security issue. The only fix that has worked for me is to reboot my router. My HA runs just can't access the Lovelace interface until router is restored.

sanderlv commented 4 years ago

Yes, if nodered is not installed this problem is not there.

ashmodai6 commented 4 years ago

I do have the same issue on a fresh install of the latest HassOS with homeassistant. No nodered installed yet so it is unlinked ...

r3m0dul8 commented 4 years ago

Recently changed from running in a ubuntu docker to a rPi and getting this same issue. Rebooted my pfSense and no change, it has to be something to do with docker surely? I really need a fix please!

bschatzow commented 4 years ago

Removed node red, have rebooted twice with no issues. Did several updates to HACs integrations where rebooting required and No issues.

sanderlv commented 4 years ago

How could this issue be solved if it is still there?

richardguinness commented 4 years ago

I have never had Node-RED installed and I am experiencing this problem. I am running Hass.io within a Ubuntu VM on a Debian host

sanderlv commented 4 years ago

Strange that "nodered" is mentioned in the error: 20-02-05 10:28:39 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 10:28:39 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-02-05 10:28:39 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-05 10:28:44 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 10:28:44 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-02-05 10:28:44 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-05 10:28:49 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 10:28:49 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-02-05 10:28:49 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-05 10:28:55 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 10:28:55 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-02-05 10:28:55 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

solidminds commented 4 years ago

Same problem on 0.104.3 version. But with Almond this time:

20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] WebSocket access from core_almond 20-02-05 19:52:37 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] WebSocket access from core_almond 20-02-05 19:52:37 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] WebSocket access from core_almond 20-02-05 19:52:37 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] WebSocket access from core_almond 20-02-05 19:52:37 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] WebSocket access from core_almond 20-02-05 19:52:37 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-05 19:52:37 INFO (MainThread) [hassio.api.proxy] WebSocket access from core_almond 20-02-05 19:52:37 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

EspElement commented 4 years ago

I am having this as well, it does seem to be Node Red related though. I get this error when I deploy in Node Red.

bschatzow commented 4 years ago

Updating to .105 caused issues again. Seeing:

service_worker.js:1 Uncaught (in promise) TypeError: Failed to fetch net::ERR_CONNECTION_REFUSED 20-02-06 16:04:19 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. How can we get this issue reopened?????

StijnVdd commented 4 years ago

I did also just update and have the same error image

Arkadije commented 4 years ago

Same problem here after update. I restarted hass.io and did not solve the issue. After I restarted ProxMox VM the issue was resolved.

AndyKassell commented 4 years ago

Same issue after updating to 105.2

karsie1994 commented 4 years ago

Same issues

kayloehmann commented 4 years ago

Same here. Node Red issue?

20-02-09 17:50:31 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-09 17:50:31 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-02-09 17:50:31 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 20-02-09 17:50:31 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-09 17:50:31 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered

crus1313 commented 4 years ago

me too, hassio on pi, 105.2

viktak commented 4 years ago

Just updated to 105.2 and I also get 12 copies of this error: 20-02-10 07:25:39 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

whundahl commented 4 years ago

Getting the same error and I have restarted as well to no avail. --

20-02-10 15:12:39 ERROR (MainThread) [hassio.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:63069 ssl:None [Connection refused]

bschatzow commented 4 years ago

It seems everyday, more and more people are having similar issues and we can't even get this issue reopened? Issue was closed by the bot. How do we get this addressed?

SteveRMann commented 4 years ago

I am starting from a new system and I started getting these errors after installing Node-Red.

20-02-10 22:42:53 INFO (SyncWorker_7) [hassio.docker.interface] Restart homeassistant/raspberrypi3-homeassistant 20-02-10 22:42:53 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str 20-02-10 22:42:53 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API connection is closed 20-02-10 22:42:58 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 20-02-10 22:42:58 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-02-10 22:42:58 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. I do know that the 172 address is the Docker, but beyond that I am clueless.

I sure hope that someone figures it out.

sanderlv commented 4 years ago

Please re-open this issue.

solidminds commented 4 years ago

Please reopen. I have this problem with Almond container. But before installed the Almond addon, I had this issue with Nodered addon. Seems to only happen when I restart Hassio. After that no errors.

Vingen168 commented 4 years ago

made a new hassio install with few regular addons(mqtt etc etc), nothing added and this error pops up in system logs, so it cant be the flow causing it.

solidminds commented 4 years ago

I now set Almond addon to not autostart at startup. And problem occurs again with Nodered container. Maybe is has something to do with how long an addon takes to start. I'm running on rpi4 with 12 addons and a continues cpu load between 30% and 45%.

holnburger commented 4 years ago

Same problem from my side. After upgradeing to 105.2 I first had this issue with almond. After i uninstalled almond I now have this problem with node red

20-02-15 19:04:12 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 20-02-15 19:04:12 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

This error repeats every couple of seconds, sometimes followed by a random restart of Home Assistant.

20-02-15 19:03:55 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home Assistant Docker! 20-02-15 19:03:55 INFO (SyncWorker_14) [hassio.docker.interface] Start homeassistant/qemux86-64-homeassistant

bschatzow commented 4 years ago

I bit the bullet and reinstalled everything. Nothing is not working. Not sure why the update kept failing.

DJ600V commented 4 years ago

Yup, same here, after last updates:

20:46:12 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

Cant access to HA via webside. Server refused connection on both interfaces/address (LAN, WLAN). I'm fighting with it last 4 days.

cogneato commented 4 years ago

Your addons (node-red, almond, appdaemon) cannot connect with Home Assistant when it is restarting. All of these pairs of messages are normal to see when Home Assistant Core is restarting.

sanderlv commented 4 years ago

So having errors during start is the new normal? There should be so time wait to avoid these errors then...

Swiftnesses commented 4 years ago

Count me in, started today on latest beta, resorting back to the last stable release doesn't help.

mkh595 commented 4 years ago

Updated to HassOS 3.11 and error disappeared.

crus1313 commented 4 years ago

I can confirm.