System log error: Connection refused, but I'm not using that private network range

Installation Home Assistant OS
1

Hi all
Apologies I’m not sure when this started as I don’t look at my System log as often as maybe I should.
I have about half a dozen errors that look like this…

20-03-09 01:56:46 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-03-09 01:56:46 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-03-09 01:56:49 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for mqttuser
20-03-09 01:56:49 ERROR (MainThread) [supervisor.homeassistant] Error on call http://172.30.32.1:8123/api/: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]

Each error is always preceeded by either the appdaemon call or mosquitto’s. Nothing seems to be wrong with the way AppDaemon or my MQTT host is running.

I suppose what has me scratching my head is why the host is referred to here as being on a 172. private network range? My installation is on the 192.168. range.

Any ideas why that discrepency?

2

Hass.io is using Docker container(s). 172.30.x.x are “internal” IPs for the different containers. They are assigned from Docker. :slight_smile:

Check the documentation here: https://docs.docker.com/engine/reference/commandline/network_connect/

3

Ah, I see. Thanks @paddy0174
My system’s reverse-proxy is handled “outside” of my home assistant installation. Could that be contributing to the errors? I wonder if I can just ignore them, as I am very happy with how my system is running.

1 Like
4

In my case, I do ignore them, because normally these are just refused connections, because something isn’t ready at that point. :slight_smile:

For example, the app_daemon message, I do always get, when I restart HA. As I do restart the HA container, the AppDaemon container can not connect, same for the mqtt container (from your example).

I’d look for any errors, that take place outside a restart or something like that for the main HA container. :slight_smile:

EDIT:
This is what it looks like, when I restart HA.

ha_200309_log
ha_200309_log1413×710 58.9 KB

1 Like
5

That gives me some piece of mind - thanks

1 Like