Yesterday, 09:34 AM
(This post was last modified: Yesterday, 10:53 AM by Tone. Edited 2 times in total.)
Ok, last update:
It's a fail2ban limitation.
It just reads the files at start and jellyfin always has a different names for the current log (date), so f2b will always work just a day if you're not restarting it daily.
So the offical documenation (https://jellyfin.org/docs/general/post-i...d/fail2ban) doesn't really work, which is very dangerous, because people test it and it will work, but after a day, it's all over.
PLEASE make at least a warning in the documentaion for now, so that people do not lull themselves into a false sense of security.
In the meantime, I created this feature request:
https://features.jellyfin.org/posts/3541...an-support
As a workaround, you probably can fiddle around with the logging.json as described here
https://github.com/jellyfin/jellyfin/iss...2089208548
It's a fail2ban limitation.
It just reads the files at start and jellyfin always has a different names for the current log (date), so f2b will always work just a day if you're not restarting it daily.
So the offical documenation (https://jellyfin.org/docs/general/post-i...d/fail2ban) doesn't really work, which is very dangerous, because people test it and it will work, but after a day, it's all over.
PLEASE make at least a warning in the documentaion for now, so that people do not lull themselves into a false sense of security.
In the meantime, I created this feature request:
https://features.jellyfin.org/posts/3541...an-support
As a workaround, you probably can fiddle around with the logging.json as described here
https://github.com/jellyfin/jellyfin/iss...2089208548