DE

↑ ↓ select, Enter open, Esc close

Show the status of a Fail2Ban jail and banned IPs

harmless rootSecuritydebian, ubuntu
Adjust the values, the command updates live
root@server
fail2ban-client status sshd

Shows the monitored log sources for the given jail, the number of current and total failed attempts and the list of currently banned IP addresses. Without a jail name, fail2ban-client status lists all active jails. Useful for checking whether Fail2Ban is working at all.

Note: On Plesk the jails are named differently than in a standard Fail2Ban setup. So list all jails first.

Open question before approval: Jail-Namen unter Plesk prüfen: Plesk legt eigene Jails an (vermutlich ssh, plesk-apache, recidive usw.), sshd gilt für ein Standard-Fail2Ban.

Also searched as

  • fail2ban list banned ips
  • fail2ban-client status jail
  • check if fail2ban is working

Related one-liners

All in Security

Unban an IP address in Fail2Ban

#fail2ban-client set sshd unbanip 203.0.113.25
cautionSecurity

Block a single IP address immediately with iptables

#iptables -I INPUT -s 203.0.113.25 -j DROP
cautionSecurity

IP addresses with the most failed SSH logins

#journalctl -u ssh --since "24 hours ago" --no-pager | grep -oE 'Failed password for .* from [0-9a-f.:]+' | awk '{print $NF}' | sort | uniq -c | sort -rn | head -20
harmlessSecurity

Add an IP address to an nftables blocklist

#nft add element inet filter blocklist '{ 203.0.113.25 }'
cautionFirewall

Ban an IP address manually in CrowdSec

#cscli decisions add --ip 203.0.113.25 --duration 24h --reason 'manual ban'
cautionFirewall

Block an IP address or subnet with ufw

#ufw insert 1 deny from 203.0.113.0/24
cautionFirewall

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.