WTH are those Login Attempt failed?

Archive Month of "What the heck?!" (2020)
44

Can you point me to that GitHub issue so I can subscribe?

45
1 Like
46

Ow , seems a long ongoing issue already

47

I get these every day.

48

Every day for 2 years for me.

1 Like
49

Just curious for those who have this issue, are you showing camera previews in your Lovelace UI?

1 Like
50

Yea a couple of times a day everyday for me.

camera previews??? not sure what that means…if you mean “Preload stream”, I don’t.

51

Every camera has a temporary url like /api/camera_proxy/camera.birdcam?token=extremelylongtokenyesitsverylongnoidontwantosharemine. If a client tries to access that url via an outdated token, the login attempt failed message pops up.

1 Like
52

Thanks. How would one determine this is the case? and then fix it?

53

They would fix it by providing an auth header as well as a URL param, so if outdated requests are authenticated properly, it wouldn’t mind it.

54

OK. I just opened up Chrome “Inspect” and on my home page there is a picture I have that uses the API you mentioned. As I was looking at the, the token actually changed!!! And in the course of composing this, it has changed yet again…
<img src="/api/camera_proxy_stream/camera.local_picture?token=03acc92blah blah blah" alt="Preview of the Local Picture camera.">

The fact that the token changes itself, does that mean this particular camera is not the problem of login attempt failures?

55

Well it should change itself, but if it fetches the image, and forgets to get the latest URL means any camera could be the cause. Anything that displays the entity-picture could be the problem (including the entities tab).

56

I get these from my tablet running HADashboard, whenever HA is restarted.

Oh, and my dashboard does have a webcam image on it.

57

The token does change. This is updated by the websocket. I think a way around this might be to replace the image with a placeholder when the socket disconnects or the user leaves the window/tab.

There may be a way of detecting whether the tab goes to sleep which I think is the issue, as well as disconnection. (although these might be one and the same)

I think the issue is all about timing with that 500ms or so that makes the image refresh

1 Like
58

Yes, I have multiple camera previews in my lovelace UI, which get frequently used.

59

Yes. 4 cameras configured with generic camera config and h.264 RTSP->AVC streams using the streaming component. Some devices use the live view, some don’t.

60

How do I do that for reverse proxy? These notifications are crazy.

61

Hi, I ended up here as well… have 4 instances of HA. 2 production and 2 dev/test. In all 4 I have this.

I get is from mobile browser access, mobile companion access and desktop browser access… both via direct “internal”, and external access via nabu casa and as well reverse proxy logins.

If I add the local network as trusted I get other weird behaviour like I suddenly have to login randomly and the browser seems not to remember the session (likewise the app).

How can I get rid of the mostly annoying messages?

62

@reinder83 did you succeed in configuring Home Assistant for a reverse proxy as @frenck suggested? If so would you mind sharing what steps you took?

I’d love to get rid of these warnings. As I have IP banning set-up sometimes I lock myself out of my home assistant…

Here are some examples of the warnings I get:

  • Login attempt or request with invalid authentication from a0d7b954-nginxproxymanager.local.hass.io (172.30.33.7). (Mozilla/5.0 (Linux; Android 11; AC2003 Build/RP1A.201005.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/89.0.4389.105 Mobile Safari/537.36)
  • Login attempt or request with invalid authentication from 192.168.0.158 (192.168.0.158). (Mozilla/5.0 (Linux; Android 11; SM-A705FN Build/RP1A.200720.012; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/89.0.4389.105 Mobile Safari/537.36)

Many people seem to be sufering from these kind of warnings as demonstrated by for example this post and this one but the topics don’t really contain pointers about how to go about solving the issue.

63

Yeah I did, the only difference is the IP addresses in the warnings are from the actual device instead of a docker IP, so im still getting those.