check your scripts/automations.
Any of these trying to login with no good password/auth token?
Are you using NMAP? If you’re seeing authentication failures from 127.0.0.1 and you’re using the nmap device tracker, you should [exclude the Home Assistant IP](https://www.home-assistant.io/components/device_tracker.nmap_tracker/#exclude) from being scanned.
Are you using Appdeamon?
Are you using reverse proxy like NGINX? You need to add similar there as well if you are using but I think it more likely from HA.
Docker actually don’t normally show up as localhost when authentication fail from external source, usually shows as 17x.xxx.xxx.xxx. Your issue may be actual local service like automation or something configured and coming from HA itself.
I don’t use nmap or nginx, but doesn’t appdeamon come standard with hassio? I’m unsure what it is and what it does, but I read somewhere that maybe you need to update it, but shouldn’t hassio updates do that? Because I’m not using any automations with webhooks or anything.
Is this caused by a configuration issue or is it a bug? With Home Assistant moving toward Version 1, we shouldn’t need to hack it to stop errors like this.
I have two clean installs of Version 0.100 and both throw these notifications about login errors. Everytime I access the interface, there is a notification of the failed login that corresponds with the time that I actually logged in.
Sometimes the failed login are from the localhost loopback (127.0.0.1) others from the IP of the device that successfully logged in.
Note: Issue happens even from a fresh install for me, before any device trackers are setup.
I found a lot of different threads regarding the topic “Login attempt or request with invalid authentication from 127.0.0.1”. It seems to me that this problem comes regularly to different people. Beside some special hints regarding e.g. Appdaemon, NMAP there is often no solution in the threads. Is there realy no way to get rid of these notification?
I would also be fine with a possibility to ignore this notification. But also for this problem I find no possibility…
I think it’s an issue with the latest android app, or the latest core update. I haven’t had any issues with this beforehand, and now I’m getting invalid logins from each of my two android phones, one of which is only running the Hassio app and nothing else.
I’m still getting these login error notifications, which are pretty annoying. I’m trying to check all the logs across all my add-ons and integrations, but my Home Assistant setup is getting pretty complicated, so I have no idea how to figure where these are coming from. I don’t really care about the notifications since nothing appears to be broken, so it would be nice if I could ignore these entirely so they don’t show up.
Same is happening to me also the weird thing that I can login to Home Assistant via ipadOS app with no problem, the problem just on my android phone.
Edit: I’m using home assistant connecting through wifi to my network which is not ideal, after I went to “configuration” then “add-ons, backups & supervisor” then “system” there click on “change” next to ip address under wlan0 click on “wifi” scan for your wifi and enter the password and save. That solved my problem. Hope it helps you too.
I think I fixed my problem with this message. I had set my home assistant server to a fixed IP address in the router, in “addons, backups and supervisor” > “system” > IP Address it was pointing to “DHCP”. When I changed it to “Fixed IP” this resolved the annoying messages. Thanks @mousawm for giving me a clue where to look.
10/02/22 - Update dammit the issue is back so no it wasn’t a fix. Sigh
I have been getting this error for about a month now and nothing has been changed. It just showed up and I can’t to the life of me figure out what is wrong. I have a static IP on the HA server which is a direct install to an Intel NUC. The system I am accessing from has a static IP and been the same since I built it over a year ago. No configuration changes have been made in over six months. Just the updates is all that has changed over the last few months, then it appeared.
I recently found the culprit of this error on my system to be a tablet running the HA app. I logged it out, then back in and haven’t had the error again since.
What fixed it for me was turning off “Can only log in from the local network” option in “Settings” > “People” > (person from whose phone the login attempt was coming from):
Been having this issue for the past few months, finally just noticed it was triggered when I tried (and failed) to log in via the Home Assistant Cloud ui.nabu.casa domain.
Taking @Neovision 's advice, I went looking at users and realized that the default Home Assistant Cloud user in my system is set up for “Can only log in from the local network”, a setting that can’t be changed for it.
So it seems like HAC is running authentication through localhost (127.0.0.1), which, if it’s not in the list of “trusted_proxies”, triggers the notification.
