The best way to get help with WP fail2ban is to use Contact Us in the WP fail2ban dashboard.

The form automatically includes diagnostic information about your installation, so we have the details we need to start investigating your problem.

If you email us instead, we'll probably have to ask for that information anyway. That can mean several emails back and forth before we can even start looking at the problem, wasting your time and ours.

Support is available to both Free and Premium users, with Premium requests given priority.

Questions before installing?

Not sure whether WP fail2ban will work with your hosting setup, or have a question before you install it?

Email support@wp-fail2ban.com and we'll be happy to help.

Check wp-config.php

Using WP fail2ban Free? If you've configured WP fail2ban by adding WP_FAIL2BAN_* constants to wp-config.php, check that you've put them in the right place. WordPress loads wp-config.php in a particular order. Configuration added after WordPress has started loading will be too late for WP fail2ban to use. Your definitions need to appear before WordPress loads […]

Using WP fail2ban Free?

If you've configured WP fail2ban by adding WP_FAIL2BAN_* constants to wp-config.php, check that you've put them in the right place.

WordPress loads wp-config.php in a particular order. Configuration added after WordPress has started loading will be too late for WP fail2ban to use.

Your definitions need to appear before WordPress loads wp-settings.php, as shown in the example below.

Using WP fail2ban Premium?

Premium provides a settings interface for most configuration, so you won't normally need to edit `wp-config.php`. If you've deliberately configured settings using constants, however, the same placement rules apply.

---

The bottom of the standard wp-config.php file looks like this:

/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* For information on other constants that can be used for debugging,
* visit the documentation.
*
* @link https://wordpress.org/support/article/debugging-in-wordpress/
*/
define( 'WP_DEBUG', false );

/* Add any custom values between this line and the "stop editing" line. */

//// WPf2b defines go here ////

/* That's all, stop editing! Happy publishing. */

/** Absolute path to the WordPress directory. */
if ( ! defined( 'ABSPATH' ) ) {
define( 'ABSPATH', __DIR__ . '/' );
}

/** Sets up WordPress vars and included files. */
require_once ABSPATH . 'wp-settings.php';

The single most common reason WPf2b doesn't work as expected is that the define() statements are added too late in wp-config.php.

They absolutely must be added before the line that says:

/* That's all, stop editing! Happy publishing. */

Check the documentation (again!)

Check the “Last 5 Messages” Widget

Check what’s actually being logged