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

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

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 15 (1 by maintainers)

Most upvoted comments

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

Grappa2020 on Apr 10, 2020

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 😃

BarrettLowe on Apr 7, 2020

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.

frenck on Mar 9, 2020