• Resolved webdash

    (@webdash)


    Hi – I’m getting the above error in my wordfence scan – first time I’ve ever seen this error, nothing changed at my side AFAIK.

    Any advice on how to resolve this please?

    Thanks in advance and kind regards

    Dave

    • This topic was modified 1 year, 10 months ago by webdash.

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

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

    (@wfpeter)

    Hi @webdash, thanks for reaching out.

    There’s a chance that something has changed at your host’s end such as addition of a proxy or load balancer that could be communicating IPs incorrectly to your site. Take note of your own IP – (note that this detection can sometimes not be 100% accurate on cellular phone network connections): https://www.whatsmyip.org

    Head over to Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs and reference the area under that section that says Detected IPs and Your IP with this setting. Start from the top and check to see if any of the settings show that both of those show the same IP as the site above does.

    If nothing seems to help, you can send a diagnostic report to wftest @ wordfence . com using the link 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 webdash

    (@webdash)

    Thanks for the response Peter.

    I disabled my litespeed cache, then toggled throught the IP detection options, starting a scan on each to see if it would resolve. When I went back to the default option, the scan got further (past the ‘server state’ check), but failed with a cron key error and retry fail while testing files.. I changed the number of attempts to 5 and sucessfully completed a test.. reactivating litespeed cache, i have sucessfully run another test.. so looks like all good now.

    guessing the issue must have been something provider-side as you suggested.. using litespeed and quic.cloud for reference.

    appriciate the assistance, markig as resolved, will come back to you if anything presents as an issue.

    Kind regards,

    Dave

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Unable to accurately detect IPs Type: IP Detection’ is closed to new replies.