-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] jail configuration is ignored #31
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
I replied on the Discourse thread, but also wanted to point out here that I don't think this is a bug. The documentation says:
The jail is set as enabled in |
I see. That was probably my misunderstanding. I thought |
Is there an existing issue for this?
Current Behavior
I don´t know if this is a bug or expected behaviour, but I think it´s worth investigating.
As I created a custom jail by adding a custom
jail.d/jellyfin.local
, the corresponding[jellyfin]
section in thejail.local
file was ignored completely. The logs show that the file is loaded, but at the end of the logs, it says "No custom files found".The solution is to delete the
jail.d/jellyfin.local
file completely and move its content into thejail.local
file. But as long asjail.d/jellyfin.local
exists, the[jellyfin]
configuration is ignored without any warning or error.Expected Behavior
I followed the guide in the Jellyfin documentation and expected that creating the
jail.d/jellyfin.local
would add a valid jail for fail2ban. If this is not how fail2ban should be configured, I would expect a warning in the logs, that this jail will be ignored.Steps To Reproduce
Environment: Unraid 6.12 / linuxserver/fail2ban 2024-10-12
jail.d/jellyfin.local
with the following content:filter.d/jellyfin.local
with the following content:jail.local
with the following content:Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: