brightervision
Forum Replies Created
-
I wanted to follow-up on this as this is continuing to persist and it is 100% due to the WF DB entry named emailedIssuesList in WFConfig.
We are seeing the memory limit needing to be set to nearly 1GB in order for this to de-serialize.
Hi Gerroald,
Sorry for so many replies. We have been actively looking into this.
We operate 5k+ WordPress websites and so we have a fairly large pool to look at.
Last week, approximately 1% of accounts on our network had this issue. It was fixed by removing WordFence. This week, over the weekend, another 1% had this issue. We are now digging in deeper and trying to troubleshoot the issue as opposed to just deleting WordFence.
We strongly believe this has to do with a corrupted WF DB entry named emailedIssuesList in WFConfig. When we re-name that entry, the site (with WF installed), runs without issue.
After doing this, I was able to login and email the Diagnostics report to wftest@wordfence.com. I have emailed this Diagnostics report to you from 2 different websites.
We have looked closely at 3 accounts so far and have found this WF DB entry named emailedIssuesList to be the problem in all 3.
We strongly feel that this is the cause of these 500 errors.
Our team is continuing to investigate to see if we can get to the root of this more clearly.
If you’d like to communicate directly with me, my email address is perryr AT brightervision dot com
As an update:
This server is on MySQL 5.7.
Storage engine appears to be mostly myisam, with three using innodb
===
# ls -1tr /var/lib/mysql/REDACTED_wpXXX/ | awk -F\. ‘{print $NF}’ | sort | uniq -c | sort -n
1 opt
3 ibd
68 MYD
68 MYI
71 frm
===The three tables using innodb are:
===
ls -1 /var/lib/mysql/REDACTED_wpXXX/*.ibd
wptf_wfls_2fa_secrets.ibd
wptf_wfls_settings.ibd
wptf_wprss_logs.ibd—-
As my team has dug into this further, if a website is experiencing this issue, we are able to get the site to load if we refresh it and kill the loading at just the right time, before WordFence has had a chance to wipe the output and kill the site.
Basically, if you keep mashing refresh randomly you will eventually get the site to load. Our working theory is that WF is hooking in after the site has been rendered, cleaning the output buffer, doing some checks, and crashing. If you get the timing just right, it will load.
We are happy to provide access to a broken site, but I would need to be able to communicate this in a non-public forum 😉
Hi Gerroald,
My MYSQLinformation is 7.3 and we use Litespeed.
What additional information can I provide? We are finding more and more accounts like this.
Thank you
Hi Gerroald,
I would be glad to do this, but the problem is I cannot get into the website with WordFence activated. I need to de-activate WordFence in order for the 500 error to go away.
If I change the Plugin name to fix the site, log in, and then revert the plugin name back to the proper name, I can then attempt to activate the plugin. However, it triggers a Critical Error and WP automatically de-activates.
Is there a way to get the Diagnostics report via FTP? Or via phpmyadmin? I deleted it off of the most recent account with this issue, but I feel confident we will encounter it again unfrotunately.
For additional context:
– This has happened across multiple servers of ours, with about 30 sites so far. A small number compared to how many we manage, but certainly significant.
– This appears to only have started Sunday.
– All our servers utilize Litespeed
– PHP Versions = 7.3We just tested disabling Litespeed in case that was the cause but that did not work either.
Hi James,
Here is one of them: https://evolvecounselingutah.com
We then put on a test and tried this out on a clean install of WordPress without an SSL cert: http://www.brightervisionrules.com
We received an error message when trying to connect again, but never received the email to the Admin stating the details.
Here was the email for evolvecounselingutah.com:
“Howdy!
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, Jetpack by WordPress.com.
First, visit your website (https://evolvecounselingutah.com/) and check for any visible issues. Next, visit the page where the error was caught (URL Removed as the URL is not throwing off the same error anymore)
Error Details ============= An error of type E_ERROR was caused in line 5732 of the file /home/evolvecounseling/public_html/wp-content/plugins/jetpack/class.jetpack.php. Error message: Uncaught Error: Call to a member function add_nonce() on null in /home/evolvecounseling/public_html/wp-content/plugins/jetpack/class.jetpack.php:5732 Stack trace: #0 /home/evolvecounseling/public_html/wp-content/plugins/jetpack/class.jetpack.php(5587): Jetpack->verify_json_api_authorization_request() #1 /home/evolvecounseling/public_html/wp-includes/class-wp-hook.php(286): Jetpack->login_form_json_api_authorization(”) #2 /home/evolvecounseling/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(”, Array) #3 /home/evolvecounseling/public_html/wp-includes/plugin.php(465): WP_Hook->do_action(Array) #4 /home/evolvecounseling/public_html/wp-login.php(489): do_action(‘login_form_jetp…’) #5 {main}
thrown
Bump. Same issue here.