Displaying Module On Lovelace Views Causes Invalid Login Attempt Warnings

[danieledwardgeorgehitchcock]

I have been having these warnings for a long time, and have never been able to trace the culprit:

Log Details (WARNING)
Logger: homeassistant.components.http.ban
Source: components/http/ban.py:114
Integration: HTTP (documentation, issues)
First occurred: 8:46:11 AM (1 occurrences)
Last logged: 8:46:11 AM

Login attempt or request with invalid authentication from myhomednsrecord.com (myhomeip) (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36)

However, I have stripped back my views to try and resolve this issue and have found that the Lovelace Aarlo card seems to be what is triggering it.

Steps to recreate:

Have Home Assistant working behind a Reverse Proxy with trusted_hosts set to Reverse Proxy IP and use_x_forwarded_for set to true

Any recent version of Home Assistant (I am using the beta, but the releases do the same - the beta just has more verbose logging)

Default Home Assistant authentication

IMPORTANT PART

Restart Home Assistant, then refresh the Lovelace dashboard - This triggers the warning on any devices where the page hasn't been refreshed since the restart.

Also sometimes, if I haven't refreshed the browser in quite a while, then do something on it, I get the same warning.

This sounds to me like some sort of a cookie issue??

[twrecked]

I see the same things but never bothered to track it down.

I'll take a look.

[danieledwardgeorgehitchcock]

This looks like it may be a bit more of a wider issue with Home Assistant displaying camera previews: Month of WTH some fixes have been suggested...

[twrecked]

I'll keep an eye on that thread and see what I need to do.