• Resolved reedk55

    (@reedk55)


    Hello,

    I have been using Wordfence on my website for years. Now, I am getting the following error when I try to run a scan on my website https://reedmigraine.com:

    Wordfence was unable to validate a test request to your website. This can happen if your website is behind a proxy that does not use one of the standard ways to convey the IP of the request or it is unreachable publicly. IP blocking and live traffic information may not be accurate.

    I have never seen this error appear. I’ve seen other people post the same question, so I followed the advice recommended by Wordfence support to solve the problem. Specifically, I did the following:

    1. Found my public-facing IP address at: https://whatismyipaddress.com/.
    2. Looked at Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs and cycled through the options there until it displayed the IP address I discovered, which ended up being “Use the X-Forwarded-For HTTP header. Only use if you have a front-end proxy or spoofing may result.”
    3. Saved the changes.

    After I completed those steps, I tried to run a scan again. The scan failed again, but this time for a different reason. This was the new error:

    The scan has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself.

    I already had set the scan to start remotely in the Diagnostics tab. In addition, I don’t have any “Under Construction” plugins.

    What I don’t understand is that I have two websites being hosted on the same server. The other one, which is stjudepaincenters.com, also has Wordfence installed on it. Wordfence is running scans on stjudepaincenters.com without any issue, so I would assume that the hosting company (GoDaddy) isn’t blocking any Wordfence IPs, right?

    I’m not sure how to proceed from here.

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @reedk55,

    I think after your investigation it’d be best for me to see what the error code or cause of the outbound or inbound connection might be from your diagnostics. It’s not impossible that a misconfiguration or issue on a shared hosting server could be causing an issue even if it’s working on another similarly hosted site.

    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.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,

    Peter.

    Thread Starter reedk55

    (@reedk55)

    @wfpeter – Sent. Thank you!

    Thread Starter reedk55

    (@reedk55)

    @wfpeter Hello. I just want to check to make sure you received my diagnostic report?

    Just as an update – I contacted my hosting company (GoDaddy), and they whitelisted the IP addresses I found on the following page that discusses WordFence scan troubleshooting: https://www.wordfence.com/help/scan/troubleshooting/.

    Specifically, the IP addresses they whitelisted were:

    44.239.130.172
    44.238.191.15
    35.155.126.231
    54.68.32.247
    44.235.211.232
    54.71.203.174

    Once they whitelisted those IP addresses, I logged out of the WordPress admin and then logged back in. I then started a new WordFence scan, but it returned the “Unable to accurately detect IP address” error again.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @reedk55,

    I noticed in your diagnostic that you’re using REMOTE_ADDR for IP detection, which resolved to a Sucuri cloud proxy server. I think you need to use X-Real-IP or X-Forwarded-For in Wordfence for reliable detection, which were both showing dynamic IP values more likely to be that of a site visitor.

    I appreciate you already ran this check using “whatismyipaddress”, but the Sucuri IP being yours doesn’t seem right to me.

    Thanks,

    Peter.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Scan Failed’ is closed to new replies.