Support » Plugin: Wordfence Security - Firewall & Malware Scan » Getting an error when running a scan

  • Resolved enthusedmade

    (@enthusedmade)


    Here is the error message:

    Scan Failed
    The scan has failed because we were unable to contact the Wordfence servers. Some sites may need adjustments to run scans reliably. Click here for steps you can try.

    The error returned was:

    There was an error connecting to the Wordfence scanning servers: cURL error 7: Failed to connect to noc1.wordfence.com port 443: Connection timed out

    I have no idea where to even start to fix this. Any tips?

Viewing 7 replies - 1 through 7 (of 7 total)
  • This seems to be an issue with me as well. we have over 200 sites all with Wordfence installed, will this be an issue on all our sites after this update?

    Plugin Support WFAdam

    (@wfadam)

    Hello @enthusedmade and thanks for reaching out!

    Make sure you haven’t blocked Wordfence’s scanning server’s IP address range from accessing your site. Our servers are from 69.46.36.0 to 69.46.36.32. If your site is unable to connect to itself to start a scan, we get our scanning servers to connect to you to kick the scan off. If you’ve blocked our servers, your scans won’t start. The newest version of Wordfence has code that prevents you from blocking individual addresses in our range but you can still block our entire network, so make sure you haven’t done that. If you are unsure, check with your hosting provider and ask them if they are blocking outbound connections to our IP address range.

    Also if you are using Cloudflare, I would add these IPs to the whitelists.

    https://www.wordfence.com/help/scan/troubleshooting/ is also a great reference for troubleshooting scans.

    If this doesn’t help, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Thanks!

    Plugin Support WFAdam

    (@wfadam)

    @tvvitchy53 You can also follow these steps but:

    As per forum guidelines below can you open your own topic please:

    “Unless users have the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme, and configurations, then the odds are the solution for one user will not be the same for another. For this reason, we recommend people start their own topics.”

    I’ve sent the diagnostic information to the email as requested above. Looking forward to some insight in to this issue. As for the “starting a new topic” I don’t think the wordpress version has anything to do with it, I would assume we were working on the most up to date versions of everything. So i’m happy waiting for some further details in this forum thanks.

    Plugin Support WFAdam

    (@wfadam)

    @tvvitchy53 @enthusedmade

    After reviewing the diagnostic, the issue lies with the hosting provider.

    It is possible that:

    1. Your server is blocking outgoing connections
    2. There are some DNS resolution issues

    If your server is blocking outgoing connections, you should be able to check this with your web host. Ask if they have mod_security or anything similar which could be blocking your site from accessing Wordfence servers. It would then help to whitelist the Wordfence IP range. You can find more information about that on the Servers and IP Range page in our docs.

    If there are DNS resolution issues, you can investigate this yourself if you have shell access to your site. You would then in console while on the server try either of the commands below. Depending on what is installed on your server one or more may work:

    dig noc1.wordfence.com
    nslookup noc1.wordfence.com
    host noc1.wordfence.com
    getent hosts noc1.wordfence.com
    ping noc1.wordfence.com

    You should then see the IP 69.46.36.28 returned. If you are seeing anything other than that it’s possible that your host has a caching nameserver that isn’t respecting the TTL (Time To Live). This would mean that it’s keeping old records longer than it should.

    Let me know what you find on your end and if the host was able to resolve it.

    Thanks!

    Hello, and thank you for all your help. It was indeed a server issue with the IP being blocked. I’ve had to contact them to whitelist the IP and they have since been able to connect. I wouldn’t have gotten to that conclusion without your help.. Thank you.

    Plugin Support WFAdam

    (@wfadam)

    @tvvitchy53 Glad I could help you! Thank you for your support!

    @enthusedmade I hope this helps you as well!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Getting an error when running a scan’ is closed to new replies.