Articles

Support Forum Changes

2025/11/11: Bureaucracy, News

I’m moving the support forums to new hosting and blocking access from UK IPs. This will be done as soon as possible - weeks, not months. This keeps the forum open globally without forcing surveillance‑style age checks on everyone. If Ofcom insist geoblocking isn’t enough, I’ll close the forums. Life is too short for bureaucracy.

<Read more>

Upgrading to Version 6.0

2025/09/16: Feature Change, New Feature, Premium, v6.0, WPf2b

A summary of steps to take and things you should be aware of before upgrading to v6.

<Read more>

PM0001: syslog Tag Issue

2025/01/31: Free, postmortem, v5.4, WPf2b

In WP fail2ban 5.4.0, an issue arose where the syslog tag changed to WordPress (capital W, capital P), causing existing fail2ban filters to stop working.

<Read more>

Version 5.4.0 Changes

2024/11/08: Canonical, Free, GitHub, News, Premium, v5.4, WPf2b

Background

In September I had no intention of creating v5.4 at all; v6.0 was nearly ready for public Beta testing and I was 100% focused on that.

Then in October and seemingly out of nowhere, the WP vs. WPE drama started. For a while it looked like anything with "WP" in the name was at risk, so I paused work on v6.0 and started building v5.4 - just in case.

Although it turned out that an emergency release wasn't needed, the WordPress environment is now fundamentally and permanently different.

The changes in v5.4 directly address the new reality. <Read more>

Upgrading to Version 5

2023/01/16: Feature Change, Free, New Feature, Premium, v5.0, WPf2b

A summary of steps to take and things you should be aware of before upgrading to v5.

<Read more>

Release Notes

Release 6.2.0

2025/12/08: Premium, v6.2, WPf2b

  • Event log by IP. Premium only
  • Improve IP Tools (IP Summary). Premium only
  • Add zoom functionality to graphs. Premium only
  • Update MaxMind & Freemius libraries.

Release 6.1.0

2025/11/21: Premium, v6.1, WPf2b

  • Ignore IP List (h/t Kyle Reid). Premium only
  • Update Freemius library.

Release 6.0.1

2025/10/25: Premium, v6.0, WPf2b

  • Fix database initialisation for new installs. Premium only

Release 6.0.0

2025/10/01: Premium, v6.0, WPf2b

  • Dashboard.
  • Quick-start Settings.
  • Honeypot. Premium only
  • Geolocation: Premium only
    • Add support for Cloudflare.
    • Add blocking with 451 error.
  • fail2ban: Improve filters:
    • Merge rules for performance.
    • Add tags to enhance action capabilities.
  • syslog: Change defaults:
    • Now uses LOG_AUTHPRIV by default; see WP_FAIL2BAN_USE_LOG_AUTH.
    • LOG_USER is mapped to LOG_AUTHPRIV; see WP_FAIL2BAN_USE_LOG_USER.
    • Pingbacks and Trackbacks: Improve filtering and blocking.
    • WAF: change default facility to LOG_AUTH. Premium only
    • Update Freemius library.

Please read the notes before upgrading.

Release 5.4.1

2025/04/21: Canonical, Free, LTS, Premium, v5.4, WPf2b

  • Fix compatibility for WordPress 6.8.
  • Fix incorrect dependency requiring PHP>=8.1. Premium only
  • Add license for Packagist.

Archive

Cyber Week 2022

2022/11/28: Archive

50% discount this week only - use code CyberWeek2022 at checkout.

See here for more details.

v5b1: Event hooks

2022/10/10: Archive, Beta, New Feature, Premium, v5.0, WPf2b

Premium users can now run whatever code they’d like when an event occurs.

<Read more>

v5b1: Site Health Check

2022/10/10: Archive, Beta, Free, New Feature, Premium, v5.0, WPf2b

Probably the most common reason WP fail2ban doesn't work “properly” is out-of-date fail2ban filters. <Read more>

v5b1: Updated fail2ban Filters

2022/10/09: Archive, Beta, Feature Change, Free, Premium, v5.0, WPf2b

Moved "Authentication attempt for unknown user" to wordpress-soft.conf
Moved "extra" Comment messages to wordpress-soft.conf

<Read more>

Release v5.0.0-beta.1

2022/10/04: Archive, Beta, v5.0, WPf2b

This is a major feature BETA release. You MUST update your filters; several features have changed and will not work with older filters.
Premium Users: The v5 database schema is NOT compatible with v4; to revert to v4 you will need to restore your database from backup.

<Read more>