I recently removed the legacy password from my config. Since then I keep getting the following error every few hours:
Login attempt or request with invalid authentication from 172.30.33.0.
Apparently 172.30.33.0 is the internal Hassio Docker IP?
How can I track down what’s causing the invalid login attempts? I’ve checked all my addons and can’t see what could still be using the legacy password.
I am having this problem too. Now updated to HA 0.97.0
Seems to be random. Occurs without any user input.
I assume it is related to the IOS App on my iPhone and maybe the HASSIO nginx add-on.
I tried trusted_networks: 172.30.33.0/24 but no luck.
Perhaps I had to remove nginx for that to work?
My nginx config is the HASSIO default, except for my duckdns domain name.
Edit:
ifconfig shows 172.30.33.3 which is my HA instance.
The invalid login comes from 172.30.33.4 which is another HA Docker container. I suspected it was my NGINX add-on.
I uninstalled the NGINX add-on and put this into configuration.yaml
On my router I forward port 8123 to 8123 and access HA from https://redacted.duckdns.org:8123
This works on my internal network (Also using DNSMASQ) and over LTE using iPhone App.
A little annoying to have to use the 8123 port but at least I don’t get invalid login attempts from my own HA and I don’t get myself banned!
Same issue here, although I think it is somehow related to the iOS app. I also tried different configuration for trusted_networks:, but I keep getting the error/notification.
I have another use case with NGINX running on a second Raspberry PI. In that case, I replaced the above IP address with the IP address of the second Raspberry PI.