Hass.io keeps blocking hassio-supervisor IP 172.30.32.2 and it breaks hass.io

Installation Home Assistant OS
1

Over the last few days I’ve noticed hass.io blocking 172.30.32.2 on failed login attempts.

First it happened on 0.74, but I unbanned it and downgraded to 0.73.2.

EDIT: I don’t believe it’s happening on 0.73.2. I may have just received a delayed notification since my ip_bans.yaml was empty after downgrading.

Once that IP is banned, I noticed my automations stop working and hass.io just becomes a little less fun to be around.

Looks like 172.30.32.2 is the supervisor container?

drsprite@hass:~$ sudo docker ps
CONTAINER ID        IMAGE                                    COMMAND                  CREATED             STATUS              PORTS                                                                NAMES
9c0da4668caf        homeassistant/amd64-hassio-supervisor    "python3 -m hassio"      9 hours ago         Up 9 hours                                                                               hassio_supervisor
3159b3a50521        homeassistant/qemux86-64-homeassistant   "/bin/entry.sh pytho…"   17 hours ago        Up 17 hours                                                                              homeassistant
8244a8bbfabd        homeassistant/amd64-addon-ssh            "/run.sh"                17 hours ago        Up 17 hours         0.0.0.0:2222->22/tcp                                                 addon_core_ssh
f48529769fbe        homeassistant/amd64-addon-samba          "/run.sh"                17 hours ago        Up 17 hours                                                                              addon_core_samba
c9ba32c0162e        homeassistant/amd64-addon-mosquitto      "/run.sh"                17 hours ago        Up 17 hours         0.0.0.0:1883-1884->1883-1884/tcp, 0.0.0.0:8883-8884->8883-8884/tcp   addon_core_mosquitto
2159cd2cd973        hassioaddons/appdaemon3-amd64            "/init"                  17 hours ago        Up 17 hours         0.0.0.0:5000->5000/tcp, 0.0.0.0:5050->5050/tcp                       addon_a0d7b954_appdaemon3

drsprite@hass:~$ sudo docker inspect 9c | grep "IPAddress"
            "SecondaryIPAddresses": null,
            "IPAddress": "172.17.0.2",
                    "IPAddress": "172.17.0.2",
                    "IPAddress": "172.30.32.2",

Any thoughts on why this happening and how to stop it?

image

2 Likes
2

Similar situation here. Yesterday I upgraded to new version and now my log is full of this:

2018-07-25 13:11:59 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session 2018-07-25 13:12:10 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session 2018-07-25 13:12:12 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connection refused] 2018-07-25 13:12:21 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session 2018-07-25 13:12:31 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session

3

Notification popped when failed login attempts logged, it not necessary means that IP already be banned.

What version of hass.io supervisor you have? I believe there was an issue and it has been fixed.
And if you want to try again, do not upgrade to 0.74.1, go directly to 0.74.2 please.

4

It was banned. I had to unban it by removing the entry from ip_bans.yaml. After unbanning I went back to 0.73.2.

Supervisor version is 121

5

I changed ipban logic in 0.74, so a single failed login would not be banned, a successfully login will reset the counter.

Maybe you should try on 0.74.2

6

I’m still getting 127.0.0.1 errors but I have managed to not lock myself out for a week now and now on 0.74.2
Great work you’re doing @awarecan

7

Not sure. The docker IP was banned and I had to manually remove it… that’s why I made this post.

I’ll upgrade to 0.74.2 and see what happens.

8

I think I figured out why

Please see https://github.com/home-assistant/home-assistant/issues/15595

9

OP is on the version included the fix

10

That version was just released yesterday. The original post is within that time. I am thinking that the probably existed but is no longer seen because of the update. Meanwhile other things are also being tried. Too many moving parts

1 Like
11

0.74.2 had no issues with overnight automations.

Will keep an eye on it and will let you know.

Thanks everyone

12

I had the same problem. I upgraded over the weekend and I couldn’t figure out what was causing it. Then I realized that I had the HA interface loaded on my office computer’s browser which was still running the old version of the interface. When I got to the office, HA is showing a notification that it was using an older version of the interface. I just pressed F5 to refresh the page, cleared the invalid attempts notification and it never showed again. In fact, if you look at the logs above, it does say Unclosed Client Session

13

Hi there,

I have same issue that attempt failed.
My version is Hass.io supervisor 121 and Hass.io 0.74.2 version
Does removing from ip_bans.yaml fix it?
which is path, I looked it for in config directory?

thanks in advance

login%20attempt%20failed

14

It is only a notification for “login attempt failed”, you are not banned. Otherwise, you won’t see this card. So that you cannot find ip_bans.yaml