Mark Maunder

Hi @sdayman,

We had an outage on the server that maintains the list of malicious URL’s as defined by the Google Safe Browsing list. The outage started slightly less than 4 hours ago. The server was brought back up 30 minutes ago. So this may have caused the symptoms you’re describing above.

Please do another scan and let me know if it’s working now.

Regards,

Mark.

Hi wwwolf. Just try a scan in a few seconds and you should be fine. We’re in the process of upgrading our infrastructure so this issue is temporary. We got slammed with growth during the last 2 weeks so we had to prioritize scans for paid customers for a little while, but it’s only temporary.

Regards,

Mark.

As @Barnez said, that’s how you repair Wordfence if any files are missing or if your installation is corrupt. This is one possible cause.

@graemetw in your case I’d guess your site is actually running out of memory. When we get new WF customers installing our product and they see a white screen, it’s usually a site with less than 64 megs of memory that is generating an out of memory error in the error log. You will inevitably run into this issue if you have a site that doesn’t have enough memory.

Regards,

Mark.

When we clear the cache, the way we do it is to schedule an event in WP to run immediately, then we hit the /wp-admin/admin-ajax.php URL so that the scheduled event will run.

So if you’re seeing this it’s possible that the request where the server connects back to itself does not execute as it should, even though the cache clearing has been scheduled.

When you manually clear the cache, we don’t use the scheduling mechanism, but clear the cache while you wait, that way we can return the real-time stats to you that you see in the result.

So do the following test: Do whatever action you expect will clear the cache. Then hit your site’s home page in a browser. Then wait a minute. Then check if the cache was cleared.

Hitting your home page will also trigger the scheduled clearing of the cache that should be triggered by your server connecting to itself.

Hope that helps – just trying to give you an internal view of what we’re doing in the hope of helping you diagnose the issue.

Regards,

Mark.

The code is compressed and I don’t have the time to decompress and interpret it, but based on a cursory look it does not look malicious.

Regards,

Mark.

In Wordfence you could also select the option under “How does Wordfence get IP’s” to use the CF-Connecting IP header. This is on your Wordfence options page towards the top.

Maybe damon can confirm that CF is still sending that header.

But I agree that if you are using cloudflare, you really want to either install their plugin or I think they also have an apache module that will make sure your WP install sees the correct IP’s and will disallow any other IP’s from connecting which saves you from getting attacked by someone just going around their reverse proxy.

Regards,

Mark.

Hi @koushikchere it looks like you are running out of memory at around 10 megs. You need to ask your hosting provider to upgrade your memory. 10 megs is very very small for a WordPress site and you’re going to keep running into this problem even if you stop using Wordfence.

Regards,

Mark.