DE

↑ ↓ select, Enter open, Esc close

Unban an IP address in Fail2Ban

caution rootSecuritydebian, ubuntu

Caution: This command changes the system. Understand what it does before you run it.

Adjust the values, the command updates live
root@server
fail2ban-client set sshd unbanip 203.0.113.25

Lifts the ban on an IP address in the given jail immediately. The output 1 confirms the unban, 0 means the IP was not banned in that jail. Useful when someone has locked themselves out with repeated wrong passwords.

Note: If Fail2Ban keeps banning the IP, add it to ignoreip in the jail configuration. On Plesk this can also be managed in the panel under IP Address Banning.

Open question before approval: Jail-Namen unter Plesk prüfen, siehe Eintrag zum Jail-Status.

Also searched as

  • how to unban ip fail2ban
  • fail2ban remove banned ip
  • customer locked out by fail2ban

Related one-liners

All in Security

Show the status of a Fail2Ban jail and banned IPs

#fail2ban-client status sshd
harmlessSecurity

Block a single IP address immediately with iptables

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

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

Create an IP blocklist set in nftables

#nft add set inet filter blocklist '{ type ipv4_addr; flags interval; }' && nft insert rule inet filter input ip saddr @blocklist drop
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.