6.3.0 crashes site

Hi,
When you get this blank page, please check the server error log file for any error message that could reveal some reasons behind this issue.

You can get in contact with your web host if you don’t know where is this error log file, or edit (wp-config.php) file and replace this line:
define('WP_DEBUG', false);
with:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Now, when you get this blank page again, you can check this file (/wp-content/debug.log) for any error messages.

Let me know how it goes,
Thanks.

There are no errors in the server log.
I enabled debugging but no debug log is created.
I look at the source of the (blank) web page and it is entirely empty.
If I remove .htaccess it also works with wordfence enabled.

• This reply was modified 8 years, 1 month ago by tholius.

If I where you I would remove every snippet from “.htaccess” file one by one till I figure out which one is causing this issue, I don’t think it could be the Wordfence Firewall snippet that is causing this issue because if so, it should definitely show error messages in your server error log files.

Thanks.

• This reply was modified 8 years ago by wfalaa.

For some reason, today, removing .htaccess does not solve the problem. But disabling wordfence makes the site load again.

Using wf assistant and clearing out all tables, all live traffic data, all blocked IPs brings the site back. For awhile. I have done this before. It will die again in short order.

Today WF crashed all of my sites where it is installed. The routine of disable, wipe tables, re-enable, reset options, is getting old…

This is abnormal for sure and I’m sorry for the troubles you had while running the plugin, this white blank page you got when accessing any page on your website indicates some server faults, it should be reported in the server error log files to be able to fix it, but I’m not sure why it’s not there, please make sure you are checking the correct error log files, you can double check that with your web host when this issue happens again.

Also, a very common reason could be a memory limit issue, so it will be nice to try increasing “WP_MEMORY_LIMIT“.

Thanks.