frigate-hass-card: JSMPEG view generates a lot of "login attempt failed" errors in HA
It only happens with frigate-jsmpeg. If I switch to webrtc I don’t see these.
2021-10-09 02:43:59 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from G37.axel.dom (10.1.10.41). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4644.0 Safari/537.36 Edg/96.0.1032.0)
2021-10-09 02:44:05 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from G37.axel.dom (10.1.10.41). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4644.0 Safari/537.36 Edg/96.0.1032.0)
2021-10-09 02:44:11 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from G37.axel.dom (10.1.10.41). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4644.0 Safari/537.36 Edg/96.0.1032.0)
2021-10-09 02:44:17 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from G37.axel.dom (10.1.10.41). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4644.0 Safari/537.36 Edg/96.0.1032.0)
2021-10-09 02:44:24 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from G37.axel.dom (10.1.10.41). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4644.0 Safari/537.36 Edg/96.0.1032.0)
2021-10-09 02:44:31 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from G37.axel.dom (10.1.10.41). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4644.0 Safari/537.36 Edg/96.0.1032.0)
2021-10-09 02:44:39 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from G37.axel.dom (10.1.10.41). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4644.0 Safari/537.36 Edg/96.0.1032.0)
2021-10-09 02:44:46 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from G37.axel.dom (10.1.10.41). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4644.0 Safari/537.36 Edg/96.0.1032.0)
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 53 (24 by maintainers)
Dermot, for what it’s worth, I’m not seeing these errors. If you need me to test anything please let me know.
I would recommend you don’t bother testing this right now, and wait for the next build as I am hopeful it will resolve it. I’ll ping this thread when the build is ready, probably within the next week.
I am initializing JSMpeg in the web UI with audio disabled. I don’t think it has anything to do with this issue, but it should prevent that console message.
Wow, I just tested here. No more errors since the PR from what it seems!
That’s very nice!
@oramirite I understand the frustration, and agree it is difficult to debug these errors. I also agree these are small issues and that it is unfortunate HA labels them as serious issues when they are not. However, these issues are an error with the cards. From HA’s perspective, it’s receiving an invalid/unauthorized request. I could imagine improvements in logging (e.g. only log it if it repeatedly happens, or – perhaps a much better option – allow security tokens to persist through restarts or allow some other mechanism of communication between cards and HA). If you’re a paying Nabu Casa customer, this could be an issue to try to draw their attention to, if you’re not in a position to contribute improvements yourself.
Anyway, I hope I’ve improved this for this card with the attached PR. @felipecrs I could reliably reproduce this on HA restart (in particular with the HA Android app), and after this fix I cannot reproduce it – so maybe …
Sent you a discord invite!
But let me play around with it a little. Knowing it happens to you on restart gives me something to start with.
Dermot, I can confirm the problem is fixed, I only had 1 event since I installed it, and it was a couple of hours after the upgrade to this latest pre-release version. 😃
Everything’s working smoothly, great job, thank you so much for the support, I appreciate it.
Alessandro
I was waiting for it…😃
Installed it a couple of hours ago…will let you know…thanks a lot.
If I find something I’ll let you know…thanks for your support.
It’s a pleasure helping you devs, I learn something new while doing it every time. Now I know a little bit how JS stuff is being debugged. 😃
Thanks for the explanations, I really appreciate you taking the time to do it instead of simply saying you can’t reproduce it.
I’m on 2021.10.x of HA. I just upgraded to 10.3 and 1.2 of your card. Will let you know if behaviour is still the same. If I don’t see the login issue anymore right now, but it’s too early to say. Will keep you posted.
Thanks for everything you are doing and the great support here.