#Everyone is getting fail2banned by my nginx-unauthorized jail
15 messages · Page 1 of 1 (latest)
Sounds like your fail2ban is misconfigured?
It's just the default one swag comes with - the nging-unauthorized
I don't have this issue, but this isn't an Overseerr issue
It's what fail2ban is doing, so you can maybe get help with that via the swag support channels?
(Just to be clear, I also use SWAG)
I looked at the logs and it seems overseer is throwing a bunch of 401s when its trying to do the ouath, thats why i figured it was an overseer issue
fail2ban just reads the logs of the app and bans..
[nginx-unauthorized]
enabled = true
port = http,https
filter = nginx-unauthorized
logpath = /config/log/nginx/access.log
I also have this jail, but again no issue.
XXX.XX.XX.XXX - - [19/Nov/2022:18:06:30 -0500] "GET /api/v1/auth/me HTTP/2.0" 401 123 "https://overseerr.XXX.com/login" "Mozilla/5.0 (iPhone; CPU iPhone OS 16_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.0 Mobile/15E148 Safari/604.1"
are you getting 401s when you auth with plex?
those are normal, just checking if you're logged in
do you have a fail2ban jail setup for overseer?
got it working by turning it off - i had enabled the one per the instructions on the website...but thought it was unrelated since nginx-unauthorized was the jail it was getting caught in