Ip banned when viewing camera

I have integrated my CCTV system using the camera generic platform which presents me snapshots of my cctv system as expected. But i have noticed that when i am viewing the snapshot in hassio in my PC, a notification appears that " Login attempt or request with invalid authentication from 192.168.xx.xx"…which is my PC’s IP itself. If I continue to view the image which refreshes itself every 2 second( scan Rate), my PC IP is banned from hassio as i have set a threshold of 5 for banning IP. I dont know why this happens even when i have added my PC address to trusted_proxies in config. Please advise what to do. These are the the log that appears during this.

Error getting camera image: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
3:59 PM components/generic/camera.py (ERROR) - message first occured at 3:45 PM and shows up 588 times
Unhandled exception
3:59 PM /usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py (ERROR)
Login attempt or request with invalid authentication from
3:59 PM components/http/ban.py (WARNING)```

are you using HTTPS in HA?

no…i am not using https

Possibly not even related, but I have a couple of WiFi cameras that allow only one stream. If I am viewing the camera on my phone, I would get a similar error on my PC.

but why hassio detects it as invalid authentication

Ah OK, I was getting a similar issue when HTTPS was on but now I’ve turned it off it happens less.

I still occasionally get invalid auth errors however, but not enough to trigger a ban.

In my case if you check logs, the error has happened over 500times in less than 10 minutes.

I’m seeing the same issue, i’ve added a new rtsp camera and it results in banning my current ip. I suspected that it might be because of an incorrect setup of the camera which results in alot of traffic when it tries to establish a connection.

But then I have two other cameras, 1mjpeg and 1 android ip cam and they both work intermittent without causing a ban?

Any thoughts

I have this issue too, see here

I now dont have this issue, i haven’t done anything specific to change but it rectified in some updates.

Thanks, good to know, I’ll give it a try again. I haven’t received notice from my github issue(s) that it’s fixed, so it will be interesting to see.