Skip to Content

Self-Host Fail2ban: Brute-Force Protection for Your Homelab in 10 Minutes

Stop brute-force attacks automatically with Fail2ban — the lightweight, open-source intrusion prevention tool every homelab needs.

Your server is under attack right now. Not metaphorically — literally. Within minutes of exposing an SSH port or web service to the internet, automated bots begin hammering it with brute-force login attempts. Fail2ban is the lightweight, battle-tested shield that watches your logs and bans attackers automatically. In this guide, you'll have it protecting your homelab in under 10 minutes.

Why Self-Host Fail2ban?

Every internet-facing service — SSH, WordPress, Nextcloud, your Docker containers — generates authentication logs. Attackers scan for these services 24/7, trying common username/password combinations. Without protection, it's only a matter of time before they get in.

Fail2ban solves this by:

  • Monitoring log files for failed authentication attempts
  • Temporarily banning IP addresses that show malicious patterns
  • Integrating with your firewall (iptables, nftables, or ufw) to drop traffic
  • Supporting dozens of services out of the box — SSH, nginx, Apache, Postfix, and more

Unlike cloud-based WAFs, Fail2ban runs locally, requires no external dependencies, and works even on a $5 VPS.

Prerequisites

  • A Linux server (Ubuntu 22.04/24.04, Debian 12, or similar)
  • Root or sudo access
  • SSH exposed to the internet (or any authenticated service)
  • Docker + Docker Compose installed (optional, but recommended)

Method 1: Native Installation (Quick & Simple)

For a traditional VPS, install Fail2ban directly:

# Ubuntu/Debian
sudo apt update
sudo apt install fail2ban -y

# Start and enable
sudo systemctl enable fail2ban
sudo systemctl start fail2ban

# Check status
sudo fail2ban-client status

Method 2: Docker Deployment (Recommended)

For containerized homelabs, run Fail2ban as a privileged container:

# docker-compose.yml
version: "3.8"

services:
  fail2ban:
    image: lscr.io/linuxserver/fail2ban:latest
    container_name: fail2ban
    network_mode: host
    privileged: true
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Chicago
    volumes:
      - ./config:/config
      - /var/log:/var/log:ro
      - /var/lib/docker/containers:/var/lib/docker/containers:ro
    restart: unless-stopped
mkdir -p fail2ban/config
docker compose up -d

Configuring SSH Protection

Create a jail configuration:

sudo tee /etc/fail2ban/jail.local << 'EOF'
[DEFAULT]
# Ban for 1 hour after 5 failures in 10 minutes
bantime = 3600
findtime = 600
maxretry = 5
backend = auto
banaction = iptables-multiport

[sshd]
enabled = true
port = ssh
filter = sshd
logpath = /var/log/auth.log
EOF

# Restart to apply
sudo systemctl restart fail2ban

Protecting Docker Services (Nginx, WordPress, etc.)

For containerized services, mount logs and create custom jails:

# Example: Protect nginx from brute-force login attempts
sudo tee /etc/fail2ban/jail.d/nginx.conf << 'EOF'
[nginx-http-auth]
enabled = true
filter = nginx-http-auth
logpath = /var/log/nginx/error.log
maxretry = 3
bantime = 7200

[nginx-limit-req]
enabled = true
filter = nginx-limit-req
logpath = /var/log/nginx/error.log
maxretry = 10
EOF

sudo systemctl restart fail2ban

Verification

Confirm Fail2ban is active and banning:

# Overall status
sudo fail2ban-client status

# Specific jail status (shows banned IPs)
sudo fail2ban-client status sshd

# Test with a simulated attack (from another machine)
ssh root@your-server-ip
# Enter wrong password 5+ times — you should get banned

# Check firewall rules
sudo iptables -L -n | grep f2b

Expected output:

Status for the jail: sshd
|- Filter
|  |- Currently failed: 0
|  |- Total failed: 12
|- Actions
   |- Currently banned: 2
   |- Total banned: 2
   `- Banned IP list: 45.155.205.234 185.220.101.4

Advanced: Persistent Bans & Notifications

For repeat offenders, extend bans or make them permanent:

# Add to jail.local
[DEFAULT]
# 1 week ban for second offense, permanent for third
bantime.increment = true
bantime.factor = 168
bantime.maxtime = -1

# Email notifications (requires mail server)
destemail = [email protected]
sender = [email protected]
action = %(action_mwl)s

Next Steps

Fail2ban is your first line of defense, not the only one. Pair it with:

  • SSH hardening: Disable password auth, use keys only
  • CrowdSec: Community-driven threat intelligence with shared blocklists
  • WireGuard: Replace exposed SSH with a private VPN
  • Wazuh: Full SIEM for deeper security monitoring

Your homelab doesn't need to be a fortress — it just needs to be harder to crack than the next target. Fail2ban makes you that target.

Self-Host Prometheus: Production-Grade Metrics & Monitoring in 15 Minutes