Supervisor: ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host

[ciechompl]

The problem

I see error (presented below) in the System logs.

20-02-19 22:15:40 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 is seems to be in the logs even just after clean installation not yet even configured or any plugin added.

Environment

• Home Assistant release with the issue: 0.105.5
• Last working Home Assistant release (if known): n/s
• Operating environment (Hass.io/Docker/Windows/etc.): HassOS 3.11 on ESX as VM
• Integration causing this issue: don't know
• Link to integration documentation on our website: n/a

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

[andker87]

Same here.

Hassio 0.105.5 via docker on raspbian on rpi 3b+

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

[andker87]

Here someone says that

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.

[ciechompl]

but IP 172.30.32.1 is not even mine ? this is somehow internal IP within hassio so why not to eliminate such confusing error if this comes with the default package.
not sure even which addons can it be :(

[Vingen168]

im pretty sure its "node-red-contrib-home-assistant-websocket" causing it.

untick the "I use the Home Assistant Add-on" and fill in Base URL with a access Token
the error message haven't show up for few days for me.

[fernmac2]

Same here.

[frenck]

It is indeed normal to have such an error in the logs.

When an add-on (or other system part) tries to connect to Home Assistant Core (but it isn't fully started yet), that connection would fail.

That is not a bad thing, it just reports that it happens. Connections will be picked up again when Home Assistant finished starting.

These things will happen during boot or Home Assistant Core restarts (e.g., manually invoked or during upgrade).

The 172.30.32.x is an internal network, which Home Assistant uses for internal communications between the different elements of the ecosystem. Which is right and not weird.

I'm closing this issue, as it is not a bug, but expected behavior.

[szczepaxn]

but i am affraid that is flooding in logs all the time... and it may cause to provide a delay for any events updates or state changes

[dereitz]

This happens for me after my HASSIO has been running for a while and seems to get worse over time. And it happens for various tabs at various times (sometimes Superviser, sometimes ESPHome, sometimes other tabs). I'm unable to replicate reliably b/c the error appears completely at random and then will clear (as shown in the HASS GUI) and a restart usually alleviates. I'm not sure if it matters, but I used the install.sh script to install HASSIO into an existing Ubuntu 16.04 installation.

Given the number of issues I've seen logged for this type of issue (plus my personal experience), I'm thinking there might be an underlying issue here that deserves more investigation.

[BarrettLowe]

I agree with @dereitz - there is something going on out of the ordinary. Sometimes I can fix it by restarting my supervisor, other times I just have to reboot the whole machine. I'll try and get some logs next time it happens instead of just treating the symptom :)

[Grappa2020]

i'm facing the same problem for the last month assuming one of the update started that.
after HA restart from web GUI beside that log error also getting that message on notifications:

Invalid config
The following integrations and platforms could not be set up:
homekit
zeroconf
ios
default_config
Please check your config.

restarting the Pi solve the problem

[szczepaxn]

And sometimes these are endless until reboot or it connected after some random time period...
restarting supervisor (ssh) gives the same logs and pure similar behavior

[Gooman-rus]

I have the same problem on Supervisor page. Resource http://local_ip:8123/api/hassio/app/entrypoint.js returns 502 error. I can’t access the Supervisor page. Version 0.109.2.

Logs:

Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed (‘172.30.32.2’, 80)]

Due to this problem I can't even restart the homeassistant using web interface:

Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]

Only hard physical reboot solved the problem.

[Grappa2020]

Update.
Uninstalling Almond add-on solved the problem for me.

[Gooman-rus]

I have again this issue and superviser is not working.

[thundergreen]

Does homeassistant start at all? When I watch the logs of homeassistant it stops at a certain point but webinterface connection refused with errors mentionned here. Rebooting or setting I tables won't help.

I have the spervised install on ubuntu 20.04