WP fail2ban 5.4.1

Does WP fail2ban work with WordPress 6.8.1 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
No PHP errors, warnings or notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Looks good! No problems were detected.
Performance

Memory usage: 436 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: insignificant.
The plugin didn't make the site noticeably slower.

Environment
WordPress version6.8.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 70,000+
WordPress.org page https://wordpress.org/plugins/wp-fail2ban/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 11

WP fail2ban ‹ Test site — WordPress

Page screenshot: WP fail2ban ‹ Test site — WordPress
URL /wp-admin/admin.php?page=wp-fail2ban-menu
Requested URL /wp-admin/plugins.php?action=activate&plugin=wp-fail2ban%2Fwp-fail2ban.php&plugin_status=all&paged=1&s&_wpnonce=3b0a14df4b
Aspect after-activation
HTTP status 200
Load time 0.532 s
Memory usage 3.86 MiB
JS errors None
Resource errors None

WP fail2ban

Page screenshot: WP fail2ban
URL /wp-admin/admin.php?page=wp-fail2ban-menu
Aspect menu-item
HTTP status 200
Load time 0.210 s
Memory usage 3.71 MiB
JS errors None
Resource errors None

WP fail2ban → Settings

Page screenshot: WP fail2ban → Settings
URL /wp-admin/admin.php?page=wpf2b-settings
Aspect menu-item
HTTP status 200
Load time 0.178 s
Memory usage 3.75 MiB
JS errors None
Resource errors None

WP fail2ban → Settings → syslog

Page screenshot: WP fail2ban → Settings → syslog
URL /wp-admin/admin.php?page=wpf2b-settings&tab=syslog
Aspect menu-item-tab
HTTP status 200
Load time 0.171 s
Memory usage 3.75 MiB
JS errors None
Resource errors None

WP fail2ban → Settings → Block

Page screenshot: WP fail2ban → Settings → Block
URL /wp-admin/admin.php?page=wpf2b-settings&tab=block
Aspect menu-item-tab
HTTP status 200
Load time 0.148 s
Memory usage 3.75 MiB
JS errors None
Resource errors None

WP fail2ban → Settings → Remote IPs

Page screenshot: WP fail2ban → Settings → Remote IPs
URL /wp-admin/admin.php?page=wpf2b-settings&tab=remote-ips
Aspect menu-item-tab
HTTP status 200
Load time 0.195 s
Memory usage 3.75 MiB
JS errors None
Resource errors None

WP fail2ban → Settings → Plugins

Page screenshot: WP fail2ban → Settings → Plugins
URL /wp-admin/admin.php?page=wpf2b-settings&tab=plugins
Aspect menu-item-tab
HTTP status 200
Load time 0.161 s
Memory usage 3.75 MiB
JS errors None
Resource errors None

WP fail2ban → Add-Ons

Page screenshot: WP fail2ban → Add-Ons
URL /wp-admin/admin.php?page=wp-fail2ban-menu-addons
Aspect menu-item
HTTP status 200
Load time 0.881 s
Memory usage 3.88 MiB
JS errors None
Resource errors None

WP fail2ban → Upgrade  ➤

Page screenshot: WP fail2ban → Upgrade  ➤
URL /wp-admin/admin.php?page=wp-fail2ban-menu-pricing
Aspect menu-item
HTTP status 200
Load time 0.274 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.203 s
Memory usage 3.56 MiB
JS errors None
Resource errors None

Dashboard ‹ Test site — WordPress

Page screenshot: Dashboard ‹ Test site — WordPress
URL /wp-admin/index.php
Aspect new-meta-boxes
HTTP status 200
Load time 0.304 s
Memory usage 4.01 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.333 s0.319 s-0.014 s3.51 MiB4.01 MiB+ 515.05 KiB
/wp-admin/edit.php0.189 s0.209 s+0.020 s3.57 MiB4.03 MiB+ 470.38 KiB
/wp-admin/post-new.php0.770 s0.765 s-0.005 s6.06 MiB6.56 MiB+ 514.3 KiB
/wp-admin/upload.php0.575 s0.542 s-0.033 s3.52 MiB3.95 MiB+ 434.3 KiB
/wp-admin/options-writing.php0.200 s0.187 s-0.013 s3.5 MiB3.93 MiB+ 438.36 KiB
/wp-admin/media-new.php0.274 s0.251 s-0.023 s3.49 MiB3.93 MiB+ 446.55 KiB
/wp-admin/edit-tags.php?taxonomy=category0.188 s0.185 s-0.003 s3.5 MiB3.95 MiB+ 452.23 KiB
/wp-admin/post-new.php?post_type=page0.616 s0.614 s-0.002 s6.05 MiB6.55 MiB+ 510.38 KiB
/wp-admin/options-discussion.php0.322 s0.250 s-0.072 s3.5 MiB3.93 MiB+ 434.86 KiB
/wp-admin/edit-comments.php0.196 s0.432 s+0.236 s3.52 MiB3.96 MiB+ 449.3 KiB
/0.304 s0.190 s-0.114 s3.43 MiB3.56 MiB+ 130.23 KiB
Average 0.361 s0.359 s-0.002 s3.97 MiB4.4 MiB+ 436 KiB

Code Statistics

Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.

PHP
Language % Lines of code Comment lines Files
PHP98.7%4,6093,31037
JavaScript0.6%2801
Markdown0.6%2801
CSS0.0%202
SVG0.0%101
Total 4,668 3,310 42

PHP Code Analysis | More results »

Lines of code 3,696
Total complexity 628
Median class complexity 11.0
Median method complexity 1.0
Most complex class org\lecklider\charles\wordpress\wp_fail2ban\SiteHealth
Most complex function plugins_loaded()
Classes 14
Methods 149
Functions 79

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

Options wp_options 4

Meta Boxes

{
    "dashboard": {
        "wp_fail2ban_last_messages": {
            "title": "[WPf2b] Last 5 Messages",
            "context": "normal"
        }
    }
}

PHP Error Log

The log file is empty.

See also: All tests for this plugin, How to Hide WP fail2ban Admin Menus and Widgets