bunkerweb icon indicating copy to clipboard operation
bunkerweb copied to clipboard

Published 20 hours ago • verified publisher icon bunkerity

Has Fail2Ban been removed?

Open DeadPackets opened this issue 3 years ago • 2 comments

I was trying to get banned by running attacks on the server, and I do get banned. However it is not an IP ban like fail2ban, but instead is simply just a ban where I get 403 responses. I think its better to have an actual firewall block such as fail2ban.

DeadPackets avatar Dec 05 '21 22:12 DeadPackets

Hello @DeadPackets,

Yes fail2ban has been removed. I think a pragmatic solution would be to use the specific 444 code from NGINX. Users will have the choice between using 403 (forbidden page) codes or 444 (connection close).

fl0ppy-d1sk avatar Jun 05 '22 06:06 fl0ppy-d1sk

You can tie fail2ban to 403 errors.. https://codepre.com/configuring-fail2ban-to-ban-403-forbidden-requests-in-nginx.html

baradhili avatar Jun 06 '22 00:06 baradhili

Hello @DeadPackets and @baradhili,

We now support choosing between 403 (standard HTTP forbidden) or 444 (close connection) more info here : https://docs.bunkerweb.io/1.4/security-tuning/#deny-status-code

fl0ppy-d1sk avatar Aug 26 '22 18:08 fl0ppy-d1sk