Hello!
So I keep getting a notification regarding attempted login from the ip 172.30.33.3.
Doing a lookup leads me to https://www.iana.org/
Some dna management stuff. Anyone knows if it has something to do with duckdns or something else?
Isn’t that an internal we address? Im pretty sure that is within the subnet that Hass.io uses for communication between addons/supervisor/ha.
Well could be. Just put on ip ban and then my internal connection is banned, and I can only access it over lte until I have deleted the ip again.
But if it is somehow due to some internal communication, how do I fix it? 
the log says nothing else than wrong credentials
It seems I made the notifications dissappear by re-adding the api_password: under http in configuration.yaml.
I have double checked add-ons and other stuff, but nothing seems to use that password. Not even the iOS apps.
Anyone else experiencing this, after removing the api_password?
Hello,
Just read somewhere else that this is the IP address from the docker container that runs Hassio. I’m seeing some of these authentication errors as well. No answer for the problem so far, but at least we know where it’s coming from.