Unifi connection error notification

Configuration
1

Dear community

Since some months I often get this error message as a notification:

Login attempt or request with invalid authentication from unifi.localdomain (192.168.1.1). See the log for details.

In the error log I see this line:

2024-04-04 09:34:31.732 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from unifi.localdomain (192.168.1.1). Requested URL: ‘/auth/token’. (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36)

It is not so often, once a day or once a week. Totally random. The integration is running well.

  1. Has somebody an idea what I can do or try?
  2. The integration is running well. So do you know how to disable this notification? It is annoying.

Thanks very much
Gilbert

2

I also get this message from time to time in my logs, but with no other symptom (Unifi integration seems to be working fine, camera streams behaving as well as can be expected).

Logger: homeassistant.components.http.ban
Source: components/http/ban.py:138
integration: HTTP (documentation, issues)
First occurred: 9:58:55 AM (1 occurrences)
Last logged: 9:58:55 AM

Login attempt or request with invalid authentication from unifi.localdomain (192.168.1.1). Requested URL: '/auth/token'. (HomeAssistant-Extensions-NotificationService/2024.1 (io.robbie.HomeAssistant.APNSAttachmentService; build:2024.535; iOS 17.3.0) Alamofire/5.6.4)
3

Http ban is only applicable to clients to home assistant and unrelated to the unifi integration

4

Look at your phone entries in unifi. I had a double of my phone suffixed with .localdomain. Deleting that from unifi stopped these warnings.

5

It says a plain text which OS the failed login comes from, you can’t have that many Devices at home
/auth/token , You could clear ALL in your Browsers caches(on all your devices), And delete OLD ACCESS Tokens, in You HA, Go to Profile / Security,

Same goes for you “Robbie”

6

You are correct, this was an iPad that had been powered down for a couple months (hence out-of-date iOS). I saw “unifi” in the log and assumed this had something to do with the Unifi integration, and was mistaken.

1 Like