Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WFMattR

    (@wfmattr)

    I haven’t seen that happen on a first scan before. There is a chance that there was a temporary problem on the server (I don’t know of any issues around the time of your post) or your host’s network.

    On the Wordfence Options page, can you click the link near the bottom that says “Click to test connectivity to the Wordfence API servers”, and post the results here?

    If all of the tests say that they “passed”, can you try running the scan again, and see if you have an error message again?

    -Matt R

    Hi, Matt.

    I did a scan a few minutes after I got the error and it all went through fine.

    Here are the results of the test:

    DNS lookup for noc1.wordfence.com returns: 69.46.36.8

    STARTING CURL http CONNECTION TEST….
    Curl connectivity test passed.

    STARTING CURL https CONNECTION TEST….
    Curl connectivity test passed.

    Starting wp_remote_post() test
    wp_remote_post() test to noc1.wordfence.com passed!

    Starting wp_remote_post() test
    wp_remote_post() test to noc1.wordfence.com passed!

    Plugin Author WFMattR

    (@wfmattr)

    Ok, great — it sounds like it was a temporary issue, then. If it does come back again, let us know.

    Just to confirm — are you the original poster above, just logged in with a different user ID?

    -Matt R

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Scan error when calling the 'is_safe_file' function.’ is closed to new replies.