PM0001: syslog Tag Issue
2025/01/31:
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.
2025/01/31:
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.
2024/11/08:
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>
2023/01/16:
A summary of steps to take and things you should be aware of before upgrading to v5.
2020/05/12:
For a the last year or so, Bots have been attempting to login with empty usernames.
2020/04/01:
TL;DR: https://forums.invis.net/
In the early days of WPf2b the WP (WordPress.org) support forum was a friendly place and covered more than just support. As WPf2b matured so did the forum, but recently things have changed – and not for the better.
2025/04/21:
2025/01/27:
2025/01/08:
2024/11/11:
2024/10/17:
2022/11/28:
50% discount this week only - use code CyberWeek2022
at checkout.
See here for more details.
2022/10/10:
Premium users can now run whatever code they’d like when an event occurs.
2022/10/10:
Probably the most common reason WP fail2ban doesn't work “properly” is out-of-date fail2ban filters. <Read more>
2022/10/09:
Moved "Authentication attempt for unknown user" to wordpress-soft.conf
Moved "extra" Comment messages to wordpress-soft.conf
2022/10/04:
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.