• Resolved pca2014

    (@pca2014)


    In the last 24-hours Wordfence has been failing on all of my websites that are on completely different servers, which use Cloudflare on the frontend. In the past five years I’ve had these websites, I’ve never had to whitelist WordFence IPs in Cloudflare.

    I think I’ve narrowed the problem down to Cloudflare. When I disable their proxy it works. So I reenabled their proxy and added the suggested IPs. Now is works sometimes, which makes no sense.

    69.46.36.0/24
    54.68.32.247

    If the IP address are the issue then how does the scan reach the third stage “Malware Scan” and then fail half way through claiming it cannot connect.

    Finally, if I repeat the scan a dozen times on each website, a few scans will complete but most will fail.

    I predict this is either a Cloudflare or Wordfence issue.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfphil

    (@wfphil)

    Hi @pca2014

    I think you may be misunderstanding the situation. Cloudflare is likely blocking your server IP address when the Wordfence scanner is sending requests back to WordPress to start new scan forks. I suspect that if you whitelist your server IP address in Cloudflare the scanner will work.

    Thread Starter pca2014

    (@pca2014)

    No, it wasn’t Cloudflare.

    I’ve never had to whitelist my server(s) IP or the Wordfence IPs and doing so didn’t change anything. Wordfence wasn’t having any issue reaching its IP address and the diagnostics confirmed that.

    The problem is that the Wordfence failure notice was erroneous, which sent me off on a wild goose chase. The problem was that my host changed the abort configuration and the scan process would be aborted half way into a scan, a scan that could not have started if the IP was being blocked. I added the no abort option for Lightspeed to the htaccess file and that appeared to solve the issue.

    Wordfence should have known the IPs were not blocked. You might want to fix that.

    Plugin Support wfphil

    (@wfphil)

    Hi @pca2014

    Thank you for the update.

    With the original information provided it appeared that Cloudlfare was blocking your server from sending requests back to itself which we see sometimes.

    I am glad that you found out the cause of the failed scans.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wordfence Failing in the past 24-hours (multiple websites/servers)’ is closed to new replies.