We’ll go ahead and close this post since the original poster said they were able to fix the issue.
If you have the problem, please open a new post for the issue so we can track how widespread it is.
We’ve been investigating these reports but haven’t been able to find a common denominator yet and can’t reproduce it on our side. As Gerroald said, we do have our senior QA staff actively looking for a solution. Establishing commonalities is a crucial first step to solving the issue, especially if we are unable to reproduce it on our test servers which are on most of the popular hosting providers like GoDaddy, Bluehost, etc.
One thing to note, that if you see an error in your logs about running out of memory, it may not be the same issue. It might be a case of needing to allocate more memory to PHP. PHP memory is cumulative. That means the amount set in php.ini is shared between all your plugins, your theme, and WordPress, plus any other non-WordPress apps you have installed in the site folder. We recommend changing it to 256M and upgrading to PHP 7 or above, which introduced better memory handling. If that doesn’t help, please try one of the other solutions mentioned here.
If it is your own server or a VPS:
– Try restarting mysql and check if Wordfence works
– Try restarting PHP-FPM (or Apache if not using FPM), and check if it works
If using shared/managed hosting, or if the above did not help:
– Add define(‘WORDFENCE_ALLOW_DIRECT_MYSQLI’, false); to wp-config.php, and check if it works
– Remove and reset Wordfence, with Wordfence Assistant
Regardless of whether or not something worked for you, please send a diagnostic report to wftest [at] wordfence [dot] com. You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Please add your forum username where indicated and let us know in your post after you have sent it.
Thanks all. We appreciate the help in figuring this out.
Tim
