mitpub

“I was also able to fix the error – without an old version. I renamed the plugin folder, logged in and rewrote the permalink structure.”

For what it’s worth, I use a Custom Structure for permalinks, so maybe there’s an AIOWPS bug associated with non-default permalink structures?

I think it showed 404 not found.

Yes, renaming the plug-in folder allows login at the normal URL, but the previous (working) version of the plugin must then be restored from some backup to recover full functionality that was broken.

Inexplicably, when I made a backup of the older, working plugin and then updated the plugin again, it didn’t break, and I am now using Version 5.2.2 successfully.

I did not enjoy all the user interface / arrangement changes with the new version, however, and had to spend extra time checking/fixing all our settings after choosing Configure Manually, because I was unsure of the effects of Reactivate.

• This reply was modified 1 year, 7 months ago by mitpub.
• This reply was modified 1 year, 7 months ago by mitpub.
• This reply was modified 1 year, 7 months ago by mitpub.
• This reply was modified 1 year, 7 months ago by mitpub.

To make a very long story short, I was ultimately able to resolve the problem like this:

1. Disable AIOS plug-in 5.1.7
2. Update AIOS plug-in to 5.1.8

The problem happened when I did not disable the plugin before updating it.

FYI:

https://www.a2hosting.com/kb/does-a2-hosting-support/do-you-support-ipv6/

“A2 Hosting currently does not support IPv6.”

More testing:

• Disabled Custom Firewall Rules: Blacklist update still fails
• Removed User Agent rules: Blacklist update still fails.

But I made an Updraft Clone of the website, then updated the plugin to Version 5.1.8 and Blacklist update did *not* fail.

So I think the problem is with the A2 Hosting configuration, somehow.

Thank you for testing. Something changed in Version 5.1.8 that created the problem here, so we cannot use Version 5.1.8 currently, and we remain on 5.1.7. I will try to find what might cause the problem here that you do not experience. (We’re using A2 Hosting, which uses Litespeed server, but I don’t know if that matters.)

AIOS 5.1.8 *caused* the fatal error. Version 5.1.7 works OK.

So, I figured out how to capture a log and installed the 5.1.8 plugin that triggers the crash. Here’s the debug log:

[23-Apr-2023 20:08:08 UTC] PHP Fatal error: Uncaught Error: Call to a member function set_value() on null in /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/admin/wp-security-blacklist-menu.php:144
Stack trace:

0 /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/admin/wp-security-blacklist-menu.php(87): AIOWPSecurity_Blacklist_Menu->validate_user_agent_list(‘360Spider\r\nAdsB…’)

1 /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/admin/wp-security-admin-menu.php(48): AIOWPSecurity_Blacklist_Menu->render_ban_users()

2 /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/admin/wp-security-admin-menu.php(30): AIOWPSecurity_Admin_Menu->render_page(‘Blacklist manag…’)

3 /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/admin/wp-security-blacklist-menu.php(24): AIOWPSecurity_Admin_Menu->__construct(‘Blacklist manag…’)

4 /public_html/wp-content/plugins/all-in-one-wp-security-and in /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/admin/wp-security-blacklist-menu.php on line 144

It’s running WordPress 6.2 with the Twenty Seventeen theme, also running WordFence Premium and Hummingbird. I don’t want to recreate the problem on this production system (and am not sure how to get an error log).