• Resolved deeveearr

    (@deeveearr)


    Hi,

    Been using this plugin for ages now, but a couple of issues have just arisen.

    Firstly, whilst looking around for solutions to the main problem, I noticed in Tools> Diagnosis that there is an error showing in the PHP Environment, in that the ‘Process Owner’ is unavailable.

    So on to the main problem.

    Coming into the ‘Scan’ options, on starting a new scan, it tries to start, but then almost immediately, I’m getting the error message ‘[JUL 20 22:40:20] Scan stop request received’ – which it wasn’t (not by me anyway) and is accompanied by a big yellow box stating:

    ‘Scan Failed The scan has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself. Click here for steps you can try.’

    From the steps to try, I’ve tried starting scans remotely, made sure that no ‘under construction’ plugins are running, and similarly no password protection of wp-admin is running, all to no avail.

    I’ve no idea on where to whitelist the WordFence servers, but I set up Cloudflare this morning, so it might be that?

    **Edit**
    Yes, it was the Cloudflare thing.

    Just tried running a scan with Cloudflare paused and the scan went straight through.

    So where do you whitelist ip addresses in Cloudflare so that I don’t need to keep pausing it for a scan?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter deeveearr

    (@deeveearr)

    Ok so I found the ip addresses that need whitelisting:

    69.46.36.0 to 69.46.36.32

    How do you create an ip address range so that I dont need to put 32 different ip addresses into Cloudflare?

    WFSupport

    (@wfsupport)

    Thanks for reaching out.

    I think on Cloudflare in the past I have used this:
    69.46.36.0/24
    You’d also want to whitelist the Wordfence Central server IP address.
    54.68.32.247

    I also recommend that you whitelist your server IP address since that’s how scheduled jobs are called in WordPress.

    Tim

    Thread Starter deeveearr

    (@deeveearr)

    Hi @wfsupport

    Yes, that works fine now.

    I’d already tried the first range with no success, but adding the WordFence central server ip seems to have done the trick.

    Thanks!

    pca2014

    (@pca2014)

    In the last 24-hours I’ve been having a similar problem with several different websites 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 4 replies - 1 through 4 (of 4 total)

The topic ‘Problems Happening’ is closed to new replies.