Is WP fail2ban compatible with PHP 8.4 and 8.5?

Works on PHP 8.0–8.5, with deprecation notices from 8.4

No removed PHP features found in WP fail2ban 5.5.0. It uses 17 deprecated feature(s) that only log notices today.

PHP 8.0

✓

PHP 8.1

✓

PHP 8.2

✓

PHP 8.3

✓

PHP 8.4

⚠ 17

PHP 8.5

⚠ 17

✓ no problems · ⚠ deprecation notices only (still works) · ✗ uses something removed in that PHP version

Check your whole site, not just one plugin. The free PHP Upgrade Check plugin scans every plugin and theme you have installed (including premium and custom ones) and explains each problem. It runs on any host.

Deprecated (works today, logs notices)

File:line	What
`admin/admin.php:179`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $page.
`admin/config.php:130`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $title.
`admin/lib/tab.php:238`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $input.
`admin/lib/tab.php:518`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $suffix.
`admin/lib/tab.php:646`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $value.
`admin/lib/tab.php:686`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $value.
`admin/lib/tab.php:712`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $value.
`feature/plugins.php:246`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $message_slug.
`lib/compat.php:86`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $remote_addr.
`lib/ip-range-list.php:39`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $cacheTag.
`lib/ip.php:284`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $cacheTag.
`lib/loader.php:723`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $settings.
`lib/loader.php:744`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $settings.
`lib/loader.php:784`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $settings.
`lib/loader.php:801`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $settings.
`lib/syslog.php:141`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $remote_addr.
`lib/syslog.php:191`	Implicitly marking a parameter as nullable is deprecated since PHP 8.4. Update the type to be explicitly nullable instead. Found implicitly nullable parameter: $remote_addr.

Plugin page on WordPress.org: wp-fail2ban