| docs

Appearance

Fail2Ban Filters – adminbolt Admin Panel ​

The Fail2Ban Filters page lets you view and manage filter definitions used by Fail2Ban to detect malicious activity in log files. Filters define patterns that match failed logins or attacks for each jail.

URL: /admin/fail2ban-filters

Overview ​

Fail2Ban uses filters (regex patterns and logic) to parse service logs and decide when to trigger a ban. This page exposes the filters available on the server so you can see which ones are in use, edit them if the panel allows, or add custom filters for specific services.

Purpose ​

  • View the list of Fail2Ban filters (e.g. sshd, vsftpd, apache-auth).
  • See or edit filter patterns (failregex, ignoreregex) if the panel supports it.
  • Add or enable filters for additional services.
  • Troubleshoot why a jail is or is not banning IPs (filter pattern may not match your log format).

Prerequisites ​

  • Access to the admin panel in adminbolt.
  • Fail2Ban in the sidebar (Fail2Ban → Filters).
  • Fail2Ban installed on the server.

Interface Description ​

  • Page heading: Filters (h1). Sub-navigation: Filters (current), List view.
  • New Fail2BanFilter – Link to /admin/fail2ban-filters/create to add a new filter.
  • Search – Searchbox to filter the list.
  • Toggle columns – Button to show or hide table columns.
  • Table – Columns: Name (sortable), Actions. Rows list existing Fail2Ban filters; use Actions to edit or delete.
  • Fail2Ban – Fail2Ban overview (whitelist, banned IPs, settings).
  • Fail2Ban Jails – Jails reference filters; configure ban time and actions there.
  • Fail2Ban Logs – Fail2Ban daemon log; useful when debugging filter matches.
  • Fail2Ban Settings – Jails and actions configuration.

Fail2Ban → Filters

Notes ​

  • Changing a filter can affect all jails that use it; test in a dev environment or with a short ban time first.
  • Filter patterns are regex; invalid patterns can prevent Fail2Ban from starting or matching correctly.