Debian 10 – Fail2ban Not Banning with nftables Backend – Jail Action Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Repeated brute-force attempts continue because fail2ban does not install active nftables bans.

Environment & Reproduction

Observed after migration from iptables actions to nftables on Debian 10 hosts.

Root Cause Analysis

Jail action uses incompatible backend or wrong chain/table names, so bans never apply.

Quick Triage

Run fail2ban-client status and verify whether nftables sets/chains are created during test bans.

Step-by-Step Diagnosis

Inspect jail.local actions, backend selection, and logs for command execution and permission errors.

Solution – Primary Fix

Set nftables-compatible action, reload jails, and validate that offending IPs are blocked immediately.

Solution – Alternative Approaches

Temporarily enforce static firewall rate limits while fail2ban policy is corrected.

Verification & Acceptance Criteria

Bans appear in nftables and repeated failed logins from test IP are denied.

Rollback Plan

Revert to known-good jail action template if custom chains conflict with existing firewall policy.

Prevention & Hardening

Keep jail action templates version-controlled and validate bans in post-change smoke tests.

Related Errors & Cross-Refs

fail2ban action start failed, No such file or directory for nft chain operations.

Related tutorial: View the step-by-step tutorial for Debian 10.

View all Debian 10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Fail2ban action.d documentation and Debian nftables backend implementation notes.