Skip to content
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

Error when trying to ban? #3663

Closed
mjessa12 opened this issue Jan 13, 2024 · 1 comment
Closed

Error when trying to ban? #3663

mjessa12 opened this issue Jan 13, 2024 · 1 comment

Comments

@mjessa12
Copy link

image

anyone know how to fix this issue? f2b running in docker reading NPM logs

@sebres
Copy link
Contributor

sebres commented Jan 16, 2024

  1. Why do you completely ignored the issue template, which is extremely important, and yes, maybe costs a bit of your time, but spares a lot of our time? This is also often considered rude, since indicate that your time should be thousand times more treasured than ours (and others people filling the issue templates completely).
  2. Posting a screenshot to the log excerpt, instead of (blackened) log excerpt itself is really bad manners, you know?
  3. The error looks like an after effect, so the log contains probably more errors previously...

Anyway it is hard to say without all info.
But my assumption - the jail name is too long for iptables related action: IIRC, the max length of iptables chain name is 30, and since fail2ban uses f2b- prefix for chains, the max length of jail name shall be 26 then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants