WP fail2ban Blocklist

Description

There are many plugins that use a database to check for malicious IPs after they connect, and of course fail2ban stops repeated attacks, but what if bad IPs could be blocked before they attack?

By working collaboratively – sharing attack data – WP fail2ban Blocklist does exactly that.

The Blocklist Network Service (BNS) collects attack data from participating sites, performs some analytical magic, and sends back a list of IPs that are attacking sites now but haven’t yet attacked that site. In other words, each site periodically gets a unique list of IPs to block preemptively.

GDPR

The BNS doesn’t collect personal data, and bots don’t have rights.

That said, the BNS only collects the minimum data required (time, IP, event), and only for IPs that have behaved maliciously.

Of course, it is possible that some data is generated by people behaving maliciously, but the BNS has no way to differentiate – and nor should it: an attack is an attack.

Freemius

To work, the BNS must know:

• which sites are running the blocklist add-on,
• which version is in use,
• and a shared secret for secure communication.

Freemius already provides all these, and WP fail2ban already uses Freemius; why reinvent the wheel?

Therefore, unlike the core WP fail2ban plugin, you must opt into Freemius for the blocklist to work.

Screenshots

Installation

1. Ensure WP fail2ban is installed. N.B. Requires version 4.4.0 or later.
2. Install via the Plugin Directory, or upload to your plugins directory.
3. Activate the plugin through the ‘Plugins’ menu in WordPress.
4. Opt into Freemius; the Blocklist will not work without without this.
5. The Blocklist Network Service (BNS) uses the WordPress REST API to communicate. If there is another security plugin installed be sure it allows access to the blocklist endpoint: /wp-json/wp-fail2ban/v1/blocklist
6. Important: ensure you set maxretry = 1 in your wordpress?hard or wpf2b?blocklist?hard jail; the add-on will not work otherwise.

Details of the configuration steps can be found here.

FAQ

Why am I not receiving updates?

The main reason updates fail is that the Blocklist Network Service (BNS) cannot connect to your site.

The BNS communicates exclusively via secure connections (SSL/TLS). To ensure you receive updates, verify that your site is accessible by navigating to https://<your site>. If you encounter any issues it is crucial to resolve them so that the BNS can deliver its updates.

Reviews

Prevenire e meglio che curare

Mac Boris Perc May 27, 2024

WP fail2ban Blocklist – Superb Wordpress plugin Prevention is better than cure.

Contributors & Developers

Changelog

2.2.1

• Fix issue with opting into Freemius (h/t @Nyanchovy).
• Fix Site Health passing test reported as failing (h/t @Patmos).
• Improve debug code.

2.2.0

• Add WP_FAIL2BAN_ADDON_BLOCKLIST_DEBUG.
• Add WP_FAIL2BAN_ADDON_BLOCKLIST_DEBUG_TRY_ALL_KEYS.
• Improve i18n.

2.1.1

• Fix harmless warning with PHP 8.1.
• Compatibility changes for upcoming WPf2b release.

2.1.0

• Add Site Health checks.
• Fix REST authentication issue (CORS headers) with some web servers.

2.0.1

• Fix harmless warning in dashboard widget; appears only before first polling.
• Fix REST authentication when both free and premium installed.
• Fix help links.

2.0.0

• IPv6 support. (Requires WP fail2ban 5.0 or later).
• Change filter filenames to start with wpf2b- instead of wordpress-.
• Add queue info to admin dashboard widget.

1.1.2

• Add mouseover hints to dashboard widget.
• Improve secret key lookup.

1.1.1

• Fix bug with secret key lookup.

1.1.0

• Add event queue info to dashboard widget.
• Increase maximum queue to 16384 events.
• Fix bug handling too many events.

1.0.2

• Minor bug-fix.

1.0.1

• Minor bug-fix.

1.0.0

• First WordPress directory release.