Guido

@wfpeter sorry I have forgotten to mention your name in my reply yesterday.

sorry for the late answer, the corona virus catched me and I was not really able to test it. Now I am back to normal and just did the tests.

I nailed it down, since version 7.6.2 (also with version 7.7.0) the plugin is incompatible with the “All In One WP Security & Firewall” plugin.
If I do deactivate this plugins then wordfence is working fine.

But when both plugins are active, I do run on the login error:

I do enter the login information and the value for the calculation captcha, then the wordfence 2FA popup is shown, where I enter the 2FA code and then it goes back to the login and says, that the login information are incorrect.

https://snipboard.io/4NgHGA.jpg
https://snipboard.io/mOzwQX.jpg

• This reply was modified 2 years, 5 months ago by Guido.

Hi Peter @wfpeter

I just upgraded it again to 7.6.2, tried to login in an additional private mode window, got the error message after entering the 2FA code, did generate the diagnostic report in the original window and did sent it to you.

Afterwards I did logout, remove the plugin in the ssh console, did login in again and did reinstall and activate version 7.6.1, did logout and re-login and 2FA is again working fine.

best regards
Guido

@wfpeter in the meantime I had rolled back to version 7.6.1 on our productive website and everything is working fine again.
The problem is that we do have several other plugins and a special customized theme on our productive website.
So switching to the default theme would completely brake our website.
And also deactivating the other plugins would brake our website.

I will try to update our test website instance with the current setup and will check if the error does happen there also and will try it there then.

br Guido

@richieboo are you sure that 6.1.0.1 did not fix it for you?
The old error message you will have to delete first. That old error message will not disappear automatically.
At least on my side with MariaDB 10.8.3 it did fix it. The message did not reappear after the installation for 6.1.0.1

Jos @josklever you’re right, you have been earlier with your hint. ??
Probably your hint was just overseen.

I only had seen your post after I had already analyzed and posted it in another thread that was titled with “RANDOM_BYTES does not exist”
There I had also posted the link to the MariaDB Knowledge Base entry for RANDAM_BYTES which probably made it easier for Marcus to solve the problem.

best regards to the Netherlands
Guido

I do have the same error.

The function RANDOM_BYTES will only be introduced in MariaDB version 10.10.0 which is currently in alpha status. The latest version is currently 10.8.3
https://mariadb.com/kb/en/random_bytes/

Therefore RANDOM_BYTES should not yet be used in the plugin if a MariaDB is used which is quite often used together with WordPress.

For a MariaDB there should be used instead of for example RANDOM_BYTES(4) then SUBSTR(MD5(RAND()), 1, 4)

But running the changed sql statement UPDATE wp_20170105_114905_em_bookings SET booking_uuid= LOWER(CONCAT( HEX(SUBSTR(MD5(RAND()), 1, 4)), '', HEX(SUBSTR(MD5(RAND()), 1, 2)), '4', SUBSTR(HEX(SUBSTR(MD5(RAND()), 1, 2)), 2, 3), '', HEX(FLOOR(ASCII(SUBSTR(MD5(RAND()), 1, 1)) / 64) + 8), SUBSTR(HEX(SUBSTR(MD5(RAND()), 1, 2)), 2, 3), '', hex(SUBSTR(MD5(RAND()), 1, 6)) )) directly on the MariaDB database will not help since the plugin will still always try to update with the RANDOM_BYTES function and will always create the error.

Therefore the plugin itself needs to be corrected.

• This reply was modified 2 years, 7 months ago by Guido.