Post #4153502
2026-07-28 03:20 UTC
Not sure why, but with the LAN I've needed to whitelist all hosts using #Jellyfin clients, otherwise their IP gets blocked by Fail2Ban after about an hour of watching. I fear this would happen to remote viewers too, but not sure I've ever watched more than an hour remotely. No idea if any other remote client services do the same, I've not let them run more than a few minutes.
Is this perhaps a #debian #ufw #Fail2Ban setting I should know about?
Replies (1)
-
@homelabista@mastodon.social 2026-07-28 13:10
@teledyn@mstdn.ca Worth seeing what's actually matching before you whitelist the LAN: sudo fail2ban-regex /var/log/jellyfin/log_*.log /etc/fail2ban/filter.d/jellyfin.conf --print-all-matched The jail in Jellyfin's own docs is maxretry=3 with findtime=43200. Three denied auths in twelve hours. That's not a brute-forcer, that's a house: one client sitting on a stale token, and the third strike lands mid-film. I'd shrink findtime long before touching the whitelist.