4.5. Site Health Tool¶
New in version 5.0.0.
WP fail2ban uses the standard WordPress Site Health tool to check things are configured correctly.
This works well for typical installations, but there are two things to note:
18.104.22.168. Running PHP with
PHP will not be able to access files outside the
chroot, so the health checks will not work.
If you really want them to work, you could ensure the
chroot includes the parent directory of the document root (you may already have done this and moved
wp-config.php outside the document root), and then use
nullfs to mount the
fail2ban install into the
chroot above the document root. You will then need to tell WP fail2ban where to find your
fail2ban install (see below).
Most people will simply disable the checks by adding this to
22.214.171.124. Non-Standard Install Path for
fail2ban install lives somewhere other than
/usr/local/etc/fail2ban you will need to tell WP fail2ban where to find it by adding something like this to
/** * Be sure to change the path to point to your fail2ban install */ define('WP_FAIL2BAN_INSTALL_PATH', '/var/fail2ban');
126.96.36.199. Other Reasons¶
There are, of course, many other reasons why PHP won’t be able to read the
fail2ban filter files, e.g. tighter
If you have a way to allow the health checks to run in any of these situations and think it may help others, please either write it up and submit a PR, or get in touch on the forums.