WP fail2ban

Screenshots

fail2ban is one of the simplest and most effective security measures you can implement to prevent brute-force password-guessing attacks. WP fail2ban logs all login attempts – including via XML-RPC, whether successful or not, to syslog using LOG_AUTH. For example: Oct 17 20:59:54 foobar wordpress(www.example.com)[1234]: Authentication failure for admin from 192.168.0.1 Oct 17 21:00:00 foobar wordpress(www.example.com)[2345]: Accepted password for admin from 192.168.0.1 WPf2b comes with two fail2ban filters, wordpress-hard.conf and wordpress-soft.conf, designed to allow a split between immediate banning and the traditional more graceful approach. Requires PHP 5.3 or later. Other Features CloudFlare and Proxy Servers WPf2b can be configured to work with CloudFlare and other proxy servers. See WP_FAIL2BAN_PROXIES in the FAQ. Comments WPf2b can log comments. See WP_FAIL2BAN_LOG_COMMENTS. Pingbacks WPf2b logs failed pingbacks, and can log all pingbacks. See WP_FAIL2BAN_LOG_PINGBACKS in the FAQ. Spam WPf2b can log comments marked as spam. See WP_FAIL2BAN_LOG_SPAM in the FAQ. User Enumeration WPf2b can block user enumeration. See WP_FAIL2BAN_BLOCK_USER_ENUMERATION in the FAQ. Work-Arounds for Broken syslogd WPf2b can be configured to work around most syslogd weirdness. See WP_FAIL2BAN_SYSLOG_SHORT_TAG and WP_FAIL2BAN_HTTP_HOST in the FAQ. Blocking Users WPf2b can be configured to short-cut the login process when the username matches a regex. See WP_FAIL2BAN_BLOCKED_USERS in the FAQ.