WP fail2ban 5.4.0.1

Does WP fail2ban work with WordPress 6.7.2 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: 392.66 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.2
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=de40860156
Aspect after-activation
HTTP status 200
Load time 0.461 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.151 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.158 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.146 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.141 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.140 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.151 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.830 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.254 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.217 s
Memory usage 3.54 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.299 s
Memory usage 3.96 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.307 s0.297 s-0.010 s3.48 MiB3.96 MiB+ 485.98 KiB
/wp-admin/edit.php0.179 s0.174 s-0.005 s3.54 MiB3.98 MiB+ 444.09 KiB
/wp-admin/post-new.php0.714 s1.027 s+0.313 s5.93 MiB6.34 MiB+ 426.27 KiB
/wp-admin/upload.php0.515 s0.478 s-0.037 s3.5 MiB3.89 MiB+ 405.59 KiB
/wp-admin/options-writing.php0.211 s0.199 s-0.012 s3.47 MiB3.87 MiB+ 409.65 KiB
/wp-admin/media-new.php0.246 s0.251 s+0.005 s3.46 MiB3.87 MiB+ 417.84 KiB
/wp-admin/edit-tags.php?taxonomy=category0.183 s0.191 s+0.008 s3.48 MiB3.89 MiB+ 423.51 KiB
/wp-admin/post-new.php?post_type=page0.514 s0.572 s+0.058 s5.92 MiB6.33 MiB+ 418.3 KiB
/wp-admin/options-discussion.php0.456 s0.247 s-0.209 s3.48 MiB3.87 MiB+ 406.15 KiB
/wp-admin/edit-comments.php0.202 s0.193 s-0.009 s3.5 MiB3.91 MiB+ 423.02 KiB
/0.285 s0.186 s-0.099 s3.48 MiB3.54 MiB+ 58.9 KiB
Average 0.347 s0.347 s+0.000 s3.93 MiB4.31 MiB+ 392.66 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,5973,31037
JavaScript0.6%2801
Markdown0.6%2801
CSS0.0%202
SVG0.0%101
Total 4,656 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