WP fail2ban 5.3.4

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: 380 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 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=7c1a82b6e3
Aspect after-activation
HTTP status 200
Load time 0.398 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.176 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.162 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.147 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.139 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.144 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.144 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.814 s
Memory usage 3.81 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.279 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.177 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.239 s
Memory usage 3.98 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.306 s0.316 s+0.010 s3.48 MiB3.84 MiB+ 371.08 KiB
/wp-admin/edit.php0.177 s0.188 s+0.011 s3.54 MiB3.86 MiB+ 329.2 KiB
/wp-admin/post-new.php0.700 s0.763 s+0.063 s5.92 MiB6.23 MiB+ 311.31 KiB
/wp-admin/upload.php0.561 s0.466 s-0.095 s3.49 MiB3.92 MiB+ 434.63 KiB
/wp-admin/options-writing.php0.214 s0.184 s-0.030 s3.47 MiB3.9 MiB+ 438.69 KiB
/wp-admin/media-new.php0.253 s0.225 s-0.028 s3.46 MiB3.9 MiB+ 446.88 KiB
/wp-admin/edit-tags.php?taxonomy=category0.177 s0.198 s+0.021 s3.48 MiB3.92 MiB+ 452.55 KiB
/wp-admin/post-new.php?post_type=page0.507 s0.535 s+0.028 s5.92 MiB6.36 MiB+ 447.34 KiB
/wp-admin/options-discussion.php0.266 s0.246 s-0.020 s3.47 MiB3.9 MiB+ 435.19 KiB
/wp-admin/edit-comments.php0.190 s0.187 s-0.003 s3.49 MiB3.94 MiB+ 452.05 KiB
/0.442 s0.360 s-0.082 s3.48 MiB3.54 MiB+ 61.06 KiB
Average 0.345 s0.333 s-0.011 s3.93 MiB4.3 MiB+ 380 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,6373,32637
JavaScript0.6%2801
Markdown0.6%2801
CSS0.0%202
SVG0.0%101
Total 4,696 3,326 42

PHP Code Analysis | More results »

Lines of code 3,753
Total complexity 638
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