dwinden

@woo-cash

Ok, your symptoms are a little bit different.
And max_allowed_packets is already pretty high (64MB).

Looks like there is a problem inserting (file change detection) data into the wp_options table.
WordPress tries to execute ‘SHOW FULL COLUMNS FROM wp_options’ first …
which fails for some reason.
Try and run ‘SHOW FULL COLUMNS FROM wp_options’ manually from phpMyAdmin and see what happens.

What collation do the columns from this table use ? (utf8mb4_unicode_ci)

dwinden

@ryan

To get a better understanding of the brute force notices a (Xdebug) error stacktrace would be helpfull.
For more info on Xdebug visit this link.

dwinden

@whax

Not sure what is happening with the brute force notices …

But the SSL related deactivation warning is a newly introduced bug in the 5.2.0 release.

To fix it change the following line in the better-wp-security/core/modules/ssl/setup.php file:

add_action( 'itsec_modules_do_plugin_deactivation', array( $this, 'execute_deactivate' )          );

into:

//add_action( 'itsec_modules_do_plugin_deactivation', array( $this, 'execute_deactivate' )          );

But honestly it’s better to downgrade to the 5.1.1 release and wait for iThemes to fix all the issues introduced in the 5.2.0 release.
Skip this release and wait for the next update. Can’t give you any better advice.

dwinden

@alchemylife

No probably the settings are not lost. Unless you deleted the plugin from the Plugins menu option in WP Dashboard.

Also note that the Security Status section on the iTSec plugin Dashboard has been removed in the 5.2.0 release.

According to the 5.2.0 Changelog:

Feature Removal: Removed the “Security Status” portion of the Security > Dashboard page. This is in preparation for a new tool that provides suggestions tailored to the site and server that Security is running on.

dwinden

@efornes

Use the Hide Backend feature to prevent automated brute force attacks on the website login page (wp-login.php).
Disable (if possible) XMLRPC to prevent automated brute force attacks using XMLRPC (xmlrpc.php).

If you require no more assistance please mark this topic as ‘resolved’.

dwinden

@fadingmusic

According to the 5.2.0 Changelog:

Feature Removal: Removed the “Security Status” portion of the Security > Dashboard page. This is in preparation for a new tool that provides suggestions tailored to the site and server that Security is running on.

If you value the Security Status feature more than anything listed as fixed or enhanced in the 5.2.0 Changelog, simply download and install the previous (5.1.1) release.

dwinden

@alchemylife

Log into you web hosting env or use an FTP program and log into your website server and then check for the existance of the C:\Inetpub\vhosts\alchemylife.gr\httpdocs\wp-content\plugins\better-wp-security\lib\icon-fonts\load.php file …

If you don’t know how to do the above contact your web hosting.

Note the path(s) in the error(s) indicates your website is probably hosted on a Windows platform (not linux).

dwinden

@efornes

Ok, I see.

Would still be interested to see the full content of the email notification received.

Based on the provided info so far I cannot determin whether it is a temporary host lockout or a permanent host ban occurring (yes there is a difference).

Also check whether the “Immediately ban a host that attempts to login using the “admin” username” setting is enabled in the Brute Force Protection section of the iTSec plugin Settings page.

Last but not least, have you enabled the iTSec plugin Hide Backend feature ?

dwinden