Concern about security of HASS.IO and external IP proxy error

Hi,
When it come to my home, security is top priority over any features. Recently I got concern since I received an error in the supervisor logs about my RP3 HASSIO trying to reach an external IP address 172.30.32.1:8123.

8-01-18 18:07:13 INFO (MainThread) [hassio.api.proxy] Home-Assistant /api/states request
18-01-18 18:07:13 ERROR (MainThread) [hassio.api.proxy] Client error on API stream request Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
18-01-18 18:07:13 ERROR (MainThread) [hassio.api.proxy] Client error on API states request Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

Since my configuration.yaml file also contain CLEARTEXT password for Add-ON (which so far need to be really change!), I’m getting worry if HASS it is review for those kind of hack as I don’t have time to review the entire code. I did setup a few logs from my router that I’m check occasionally but that error just got me more nervous of using it.

Running: RP3 Hass 0.61.1

Any have comments?
Eric

That IP is part of a non-routable IP subnet. It is not trying to communicate out to the internet, it is trying to communicate to another IP within the Docker system that is running on your pi.

1 Like

Thanks @flamingm0e for the info, I knew about 10.x.x.x and 192.168.x.x that was non-routable and reserved but wasn’t aware of this range 172.16.0.0 – 172.31.255.255.

https://en.wikipedia.org/wiki/Private_network.

1 Like