-
-
Notifications
You must be signed in to change notification settings - Fork 968
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
fail2ban instructions fail with error on Ubuntu 20.04, fail2ban v0.11.1 #943
Comments
It should also be added that the fail2ban service needs to be enabled at startup Something like this: sudo systemctl enable fail2ban.service |
Fixed by #969 |
I don't think #969 is correct. It may remove the error, but the fix is incomplete, it doesn't enable the ddos filter as intended and only enables the basic sshd filters a second time with a different name. One solution would be to just remove the
Alternatively, if you really didn't want the "extra" filters, but you still want the "ddos" filters, you could enable them with:
But unless there is some specific reason to exclude the "extra" filters, this doesn't seem necessary. I can write a PR for this, I had just totally forgotten this issue existed until it was closed :) |
Please do 👍 |
Following the current instructions:
Results in the following error being logged:
The config I used ended up being:
aggressive
mode includesddos
modeThe text was updated successfully, but these errors were encountered: