Operating-system: Cannot connect to host 172.30.32.1:8123 (Fails to boot sometimes)

[Fusseldieb]

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.

[janningnetworks]

metoo ;) Did you solve this issue?

[Fusseldieb]

@janningnetworks No, it's quite rare to occurr, so I don't care that much, but I still put this here, so the devs can eventually fix this.

[thakkarrahul]

Hi,

I am having similar issues and have tried the above method but still the same. I am on HASSIO version 0.81.6

Here is the link to forum page where I have explained the issue.

https://community.home-assistant.io/t/hassio-no-web-interface/77208

If you have any solution, please help.

[Fusseldieb]

Bump. Still happening on 0.84.

[magin1]

Bump. Still happening on 0.85.

[TheZoker]

I have the same issue
@pvizeli any idea?

[SP410]

FYI, I have the issue in running HassIO in Docker on Ubuntu 18.04.1. For me it occurs after performing a snapshot restore...

[arissaraiva]

Hi same issue here openned another thread, I can´t access spotfy, darksky nd cloud all give me API error

[bratanon]

Same for me since 0.85. Running the default Hassio on rpi3

[bratanon]

and same with 0.85.1

[Fusseldieb]

Quick update on my findings:
If this happens, reconnecting the LAN interface on my router and then doing a "hassio su reload" over SSH makes it load everything again, so my assumption is right.

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.

[ahnernoch]

Same here. Sometimes Web Interface just wont come up.

[h4nc]

same here

My error looks like this:
[hassio.api.proxy] Client error on WebSocket API Cannot connect to host "IP" ssl:False [Connection refused].

Strange... I get this error serveral times when I restart homeassistant. I don't get it when I reboot the whole system (hassio).
Could someone confirm that?

EDIT: Maybe this is an expected behaviour. When I restart home assistant, hassio wil not be able to reach ha in the time it restart, so it throws that error.
When I restart hassio it can't try to reach ha.

[Obicom]

Same issue with new beta 0.87.0b0

[1iveowl]

Same issue w/ 0.87.1

[PreferHardware]

Same here, hassio 8.7.1 on NUC5PPYH with duckdns and ssl:

[homeassistant.components.hassio.handler] Client error on /supervisor/ping request Cannot connect to host 172.30.32.2:80 ssl:None [Connection refused]

The problems started as soon as I moved to ssl, duckdns, etc. No amount of messing around with yaml files made any difference, but a cold reboot magically cleared the errors.

[PreferHardware]

This behaviour could also, repeatably, be triggered by including a discovered media_player (samsungtv) in the yaml. Commenting out the line and rebooting (not simply restarting the containers) was the solution.

[h4nc]

Which line exactly do you mean? Ignore it in autodiscovery?

I indeed also have a samsung tv.

discovery:
  ignore:

[PreferHardware]

I tried adding the Samsung TV to a "Sitting Room" group by simply adding the line:

• media_player.television

in groups.yaml. This was the line that caused problems and was the line that I commented out before rebooting.

The process of discovery does not seem to be the problem. The problem only comes when the discovered entity is actually introduced into the yaml.

[h4nc]

Ok, I don't have my media_player's in a group.
I'm not sure we have the same issue.

I also noticed that the samsung media player entities are not reliable. Sometimes they show up sometimes not.
I think you onle get them when the TV is on when you start home assisant.

So if you restart ha and the tv is off, the entity does not show (I'm not a 100% sure about that, buts that'S my guess).

[radionerd1]

This is driving me nuts. Why is it trying an IP that is not on my network?
ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False

I have scene this for months now, I search forums with no fixes. My private network is 192.168.1.0/24 WTF???

[radionerd1]

Looks for invalid IP 172.30.32.1:8123, Won't update, rolls back.

19-03-15 04:42:42 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-03-15 04:42:42 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-03-15 04:42:42 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-03-15 04:42:46 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
19-03-15 04:42:46 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
19-03-15 04:42:46 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.88.2
19-03-15 04:42:46 INFO (SyncWorker_12) [hassio.docker.interface] Update Docker homeassistant/raspberrypi3-homeassistant:0.89.2 to homeassistant/raspberrypi3-homeassistant:0.88.2
19-03-15 04:42:46 INFO (SyncWorker_12) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.88.2.

[TheZoker]

@radionerd1 The IP 172.30.32.1 belongs to docker:
https://community.home-assistant.io/t/mqtt-why-172-30-32-1-gets-connected/46513/2

[tyborall]

Just add

  auth_providers:
    - type: trusted_networks
      trusted_networks:
        - 172.16.0.0/12

under homeassistant:

in your configuration.yaml...

@developers: I think this should be a default in configuration.

[DeviousPenguin]

- type: trusted_networks
  trusted_networks:
    - 172.16.0.0/12

Will this disable authentication at all? I have my HomeAssistant port exposed to the internet, and I'd like to keep auth enabled.

[tyborall]

Ah sorry, if you use nginx, yes it will. Then just allow that particular host.

[DeviousPenguin]

Ok, thanks, I just wanted to be sure before tinkering with the settings.

I've got it set under trusted_proxies: instead and and it seems to be working OK with NGINX + HA authentication so far.

[rover6s]

I had the same issue and removed all the Add-ons that I had added while learning HA. I had Configurator, Samba, and APPDaemon.

After removing the Add-ons I rebooted the RPi from the Hass.io-->System-->Host System menu and the error is gone. I have added the Configurator back and still no error in the System log. I really need the AppDaemon for the HADashboard so I'll add that back and see what happens.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cotwild]

After update to 0.96.3 I cannot access any dev-state, dev-info, etc. - the "developer-tools" link is new but doesn't work... So this is my System log under Hass.io -> System:

19-07-23 06:44:02 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/states/sensor.printer_status: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused] 19-07-23 06:44:02 ERROR (MainThread) [hassio.api.proxy] Error on API for request states/sensor.printer_status 19-07-23 06:44:03 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-07-23 06:44:03 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-07-23 06:44:03 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3 19-07-23 06:44:03 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-07-23 06:44:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-07-23 06:44:03 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused]. 19-07-23 06:44:07 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/states/sensor.printer_status: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused] 19-07-23 06:44:07 ERROR (MainThread) [hassio.api.proxy] Error on API for request states/sensor.printer_status 19-07-23 06:44:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-07-23 06:44:08 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize 19-07-23 06:44:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered 19-07-23 06:44:08 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_appdaemon3

[cotwild]

Stupid me.... Page refresh did the trick! sorry... how could if forget this and try to fix it for that long...

[pilot1981]

I have hassio 0.96 with same issue...

[Fusseldieb]

The stale bot is probably one of the most useless bots ever.
It closes the issue, essentially marking it as solved and therefore it won't appear in open issues anymore, making the devs think this is solved.
But it isn't.
Can anyone _please_ open this back up, because this is clearly not solved!?

EDIT: I personally think that whole Docker thingy is a mess. One docker container tries to communicate with another, for some reason can't and then messes everything up and leaves tons of people frustrated. Can't we simply integrate the whole Hassio in the OS like normal people? Docker only slows things down, particularly on lower end hardware like the RPi, and on top of that introduces errors that wouldn't even happen without it.
Relevant XKCD
Python is already relatively slow compared to other languages, and to top it all we add a lot of complexity layers on top. And then we run that on a RPi. And then we have 90+ seconds start up time. And sometimes it won't boot _for some reason_. Great!

Sorry for the little "outburst", but I think this needs to be said.

[Chuchodavids]

I know this is an old post. But I had this problem with the last HA update. I found a solution:
The problem is caused by a conflict in the ports

1. Stop all your containers except Portainer and HA + HA supervisor
2. Check if that solved your problem. If so.. continue to point three.
3. Activate one of your Docker containers and check if the problem persist.
4. Repeat number three until you find out which one is the container that is conflicting with HA.
5. When you find it, just stop the container and change the ports in which the container is running.
6. enjoy.

[Ailme]

I have this issue. hassio 0.100.2 - 0.101.2

[Tiilin]

I have the same issue. Hassio 0.101.3

[pilot1981]

Also me, during reboot action

[rant989]

I have the same issue. Hassio 0.101.3

[sebba12]

I have the same issue. Hassio 0.101.3 and not in any versions before.

[gdreelin]

Yep same here just started on version 0.101.3 never seen it before that.

[PietroMB]

I have same issue. Hassio 0.100.2

[RichardUUU]

I have it in Hassio 102.2. Running as a VM with no dockers. Do we need to open a new issue?

[dubbfredda]

I also have the same problem

[dubbfredda]

First I could not update Hassio and when I tried to update a second time it never come back up again after the update. The Homeassistant container is started but can't get any connection with the Hassio frontend. Get following error
19-11-26 20:34:25 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

[MalagaInternet]

+1 Hassio 102.2

[thomasfals]

+1 Hassio 0.102.3

[matteos1]

i have the same problem
19-11-30 21:47:34 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:47:39 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:47:39 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:47:39 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:47:44 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:47:44 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:47:44 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:47:49 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:47:49 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:47:49 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:47:54 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:47:54 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:47:54 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:47:59 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:47:59 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:47:59 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:04 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:04 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:04 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:09 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:09 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:09 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:14 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:14 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:14 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:19 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:19 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:19 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:24 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:24 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:24 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:29 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:29 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:29 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:34 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:34 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:34 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:39 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:39 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:39 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:44 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:44 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:44 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:49 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:49 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:49 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:54 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:54 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:54 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:48:59 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:48:59 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:48:59 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:04 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:04 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:04 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:09 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:09 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:09 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:14 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:14 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:14 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:19 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:19 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:19 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:24 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:24 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:24 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:29 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:30 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:30 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:35 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:35 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:35 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:40 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:40 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:40 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:45 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:45 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:45 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:50 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:50 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:50 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-11-30 21:49:55 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-11-30 21:49:55 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-11-30 21:49:55 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

[anklimov]

Is some progress to fix the issue? I have same. And have no idea how to recover it, except moving back to OpenHab

[pricard32]

This is the internal IP of your docker container.
I run hassio on a Ubuntu server, but every Hassio installation use docker.
Docker need two network, an external (your lan) and a internal (172.30.32.0/23).

I'm not sure why we all seeing this, maybe a docker expert can help us.
But in my particular case, exept seeing this, theres no error on my installation.

[bschatzow]

I have this issue when I updated to .103 in Hassio

[mpgoebel]

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

[caiocaminoski]

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

[sivastola]

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]

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

[soylant]

also updated to 103 and having the same problem

[fillilutten]

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

[blamaz]

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]

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]

same problem here on 0.104.2

[kic883]

Same here
I am using Pi 4, with

• HassOS 3.8
• Home Assistant 0.104.3
• NodeRed 6.0.2
• SSL with duckdns and let's encrypt

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]

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

[mattclar]

@pvizeli any chance we could reopen this issue?

[sanderlv]

Same here with 0.104.3

seems to have to do with node red

[bschatzow]

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]

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]

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

[Count0Int]

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]

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]

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

[ashmodai6]

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]

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]

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

[sanderlv]

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

[picklerick63]

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]

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]

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]

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]

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]

I did also just update and have the same error

[Arkadije]

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]

Same issue after updating to 105.2

[karsie1994]

Same issues

[kayloehmann]

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]

me too, hassio on pi, 105.2

[viktak]

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]

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]

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]

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]

Please re-open this issue.

[solidminds]

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]

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]

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]

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]

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

[DJ600V]

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]

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]

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

[Swiftnesses]

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

[mkh595]

Updated to HassOS 3.11 and error disappeared.

[crus1313]

I can confirm.

[mattclar]

Updated to HassOS 3.11 didnt help :(

actually scratch that, seems to have fixed it

[gyanev]

I just had a similar situation. Everything worked initially, after installing hassio on linux using this script https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh.
After the first restart I was not able to access some of the addons from the sidebar. In the log file I see a bunch of: ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Host is unreachable]
For me the issue was that the host firewall was in fact blocking access to 172.30.32.1. To test it out I've run iptables -I INPUT -s 172.30.32.0/23 -d 172.30.32.0/23 -j ACCEPT on the host and it worked for me.

Any chance some of you are affected by the same problem?

[bschatzow]

I am on a Raspberry Pi 3 B

[fernmac2]

Same error here, any update?

[dereitz]

One clue here for me is that my frontend is trying to connect to 172.30.32.2, but if I look at the output of ifconfig on my host, my current hassio interface is actually 172.30.32.1. Anyone know if the IP is dynamic?

[rlpowell]

OK, so, I have no idea if this is a general problem, but let me tell you how I fixed this for my system, which may just be about my system but who knows?, maybe it'll help you.

I have hass.io running under docker on my x86_64 Linux box, so if anything I'm saying seems wildly inapplicable, that's why. All the commands I give are run on the Docker host itself, unless otherwise specified.

The short version: This error means that your supervisor instance can't reach port 8123 on your homeassistant instance. docker uses iptables to set up the networking between instances, so inspect the iptables rules very carefully, and see if something wacky is going on.

The specific commands that solved my problem, but are unlikely to solve yours, are:

sudo iptables -I INPUT -s 172.16.0.0/12 -j ACCEPT
sudo iptables -I INPUT -d 172.16.0.0/12 -j ACCEPT

(If those commands actually do solve this problem for a bunch of people, then something super wacky is going on with the supervisor's docker setup and someone should open a new bug saying that these commands solve this problem, but that seems super unlikely.)

More details:

On my system, at least, I can test the issue directly by using "docker ps -a" to find the supervisor instance, then "docker exec -it [id] bash" and running "curl http://172.30.32.1:8123/", where 172.30.32.1 seems to be the normal IP for the homeassistant instance. You can also do "docker exec -it [homassistant-instance-id] bash" and run "ip addr" to confirm which IP is which.

If that curl hangs or is rejected, but the same curl works from the homeassistant instance, or works from the docker instance itself, then the issue is probably that the docker networking between the two instances is broken.

Here's the details of the specific issue that was blocking docker networking in my case, but "docker networking is broken" is a HUGE topic; there are literally tens of thousands of threads on such issues all over the web.

For myself, I have iptables locked down pretty tight; I have default deny turned on for the INPUT chain in iptables. That is, the last rule in the INPUT chain is:

-A INPUT -j REJECT --reject-with icmp-host-prohibited

, and above that I have a bunch of white-listed stuff like port 22 or whatever.

Maintaining such a whitelist for all of my Docker stuff is a huge pain in the ass and is also kind of pointless, since I don't really care about communications between two docker instances as long as nothing's talking to the internet, so I have a special Docker whitelist like so:

-A INPUT -s 172.17.0.0/16 -j ACCEPT -A INPUT -d 172.17.0.0/16 -j ACCEPT

This is the normal range of Docker instance IPs I've seen in the past.

It turns out, however, that for whatever reason, the instances the hass.io supervisor generates aren't in that range; they're in 172.30.0.0/16

The fix was to just grab the entire 172.16 private range, which I should have done in the first place.

In other words, these commands solved the problem for me; I would be surprised if they solved the problem for you, but who knows?:

sudo iptables -I INPUT -s 172.16.0.0/12 -j ACCEPT
sudo iptables -I INPUT -d 172.16.0.0/12 -j ACCEPT

[Devqon]

Same issue here, almost always after restarting HA it becomes unavailable. Sometimes a ha host reboot works, but more often I have to unplug the Raspberry Pi and replug it in, then it will start up everything. Very annoying to have to replug everytime I have to restart HA.

Running Hassio on Raspberry Pi 3b

[blamaz]

I start seeing this error right after the installation of Mosquito MQTT broker addon.

[Mecallie]

I start seeing this error right after the installation of Mosquito MQTT broker addon.

I did not made the link (installed some more addons) but indeed this seems to be causing an issue when upgrading!

My issue: after clicking update to 107.5 (from 107.1) the HassIO on my RPI3B fails to boot. I have to unplug it and reboot. The old version (.1) would then still be running, with the above error in the logs.

After disabling the mqtt broker addon and stopping it from running on boot the update went through fine! And enabling the addon after that does not seem to cause any issues anymore...

I don't know how docker get's it ip's, but is it possible that two containers are trying to use the same IP maybe? (Different port, thus generating the error...)

[blamaz]

I start seeing this error right after the installation of Mosquito MQTT broker addon.

I did not made the link (installed some more addons) but indeed this seems to be causing an issue when upgrading!

My issue: after clicking update to 107.5 (from 107.1) the HassIO on my RPI3B fails to boot. I have to unplug it and reboot. The old version (.1) would then still be running, with the above error in the logs.

After disabling the mqtt broker addon and stopping it from running on boot the update went through fine! And enabling the addon after that does not seem to cause any issues anymore...

I don't know how docker get's it ip's, but is it possible that two containers are trying to use the same IP maybe? (Different port, thus generating the error...)

Add your comment to issue #590, this one is closed.

mattclar mentioned this issue on 18 Feb
Reopen issue #224 #590