WP fail2ban 5.4.0

Does WP fail2ban work with WordPress 6.7.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: 354.99 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.7.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 60,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=6bc392cf30
Aspect after-activation
HTTP status 200
Load time 0.693 s
Memory usage 3.81 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.203 s
Memory usage 3.68 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.174 s
Memory usage 3.72 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.192 s
Memory usage 3.72 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.171 s
Memory usage 3.72 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.159 s
Memory usage 3.72 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.184 s
Memory usage 3.72 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.815 s
Memory usage 3.8 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.287 s
Memory usage 3.76 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.224 s
Memory usage 3.53 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.345 s
Memory usage 3.91 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.367 s0.334 s-0.033 s3.48 MiB3.91 MiB+ 444.03 KiB
/wp-admin/edit.php0.232 s0.218 s-0.014 s3.54 MiB3.93 MiB+ 402.15 KiB
/wp-admin/post-new.php0.798 s0.908 s+0.110 s5.92 MiB6.3 MiB+ 384.27 KiB
/wp-admin/upload.php0.583 s0.577 s-0.006 s3.49 MiB3.85 MiB+ 363.65 KiB
/wp-admin/options-writing.php0.216 s0.220 s+0.004 s3.47 MiB3.83 MiB+ 367.7 KiB
/wp-admin/media-new.php0.337 s0.264 s-0.073 s3.46 MiB3.83 MiB+ 375.9 KiB
/wp-admin/edit-tags.php?taxonomy=category0.189 s0.208 s+0.019 s3.47 MiB3.85 MiB+ 381.57 KiB
/wp-admin/post-new.php?post_type=page0.587 s0.622 s+0.035 s5.92 MiB6.29 MiB+ 376.36 KiB
/wp-admin/options-discussion.php0.295 s0.273 s-0.022 s3.47 MiB3.83 MiB+ 364.2 KiB
/wp-admin/edit-comments.php0.214 s0.436 s+0.222 s3.49 MiB3.87 MiB+ 381.07 KiB
/0.329 s0.213 s-0.116 s3.47 MiB3.54 MiB+ 63.96 KiB
Average 0.377 s0.388 s+0.011 s3.93 MiB4.27 MiB+ 354.99 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.2%4,5973,31037
JavaScript0.6%2801
Markdown0.6%2801
JSON0.5%2301
CSS0.0%202
SVG0.0%101
Total 4,679 3,310 43

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