Excessive 401s on login page (GET /api/v1/auth/me), even on latest develop image

[tardy summit]

Hi everyone. I'm trying to set up Seerr behind SWAG, which includes fail2ban. Every time someone loads the Seerr login page, they make a request to /api/v1/auth/me, which gets a 401 response (since they aren't logged in). This quickly gets them banned by fail2ban.

This is not new territory; I saw this issue which describes this exact behavior: https://github.com/seerr-team/seerr/issues/738

fallenbagel pushed a fix that sounds like it should have fixed it, and I've verified that the Docker image I'm running (just the Seerr develop image) contains those line changes. However, I'm still seeing this issue.

There's nothing applicable in the Seerr logs, but here's a sample from my nginx logs:

00.010.000.010 - - [13/Feb/2026:23:23:25 -0700] "GET /api/v1/auth/me HTTP/2.0" 401 123 "https://seerr.example.com/login" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0"

And my Seerr version:

> seerr@0.1.0 start
> NODE_ENV=production node dist/index.js

2026-02-14T00:40:00.979Z [info]: Commit Tag: 15be3d7475805a5a2a7771d4ec9acd0eb942f3d1
2026-02-14T00:40:01.832Z [info]: Starting Seerr version develop-15be3d7475805a5a2a7771d4ec9acd0eb942f3d1

Has anybody else been experiencing this? Considering nobody else is talking about it, maybe I'm setting it up wrong? Or is my fail2ban just too aggressive (it bans the IP after 5 401s)?

[tardy summit]

Additional references to this issue here: https://old.reddit.com/r/PleX/comments/17wbpm1/successfully_running_fail2ban_against_nginx_logs/

I'm also experiencing a similar issue with Bazarr. All this just leads me to think that the fail2ban 401 jail is way too restrictive. I'm just gonna loosen it a little to let these kinds of things pass by