Unable to accurately detect IPs Type: IP Detection

Hey @sdagency,

Do you have any caching plugins? If so, can you try clearing the cache to see if it helps?

You might also check for a conflict with either the theme or one of the plugins you’re using. Can you try temporarily switching to a default theme if you’re not already using one and disabling all other plugins then reactivating them one by one to see if the issue persists?

Please let me know.

Thanks,

Gerroald

It’s not caching or plugins or theme. Wondering if it is the same issue as reported here: https://www.ads-software.com/support/topic/wordfence-not-finding-correct-ips/

Contacting Siteground and will post results for the benefit of all.

It is interesting a number of other support posts here about other IP issues like whitelisting not working, but perhaps they are unrelated.

Siteground is emphatic this is a problem with Wordfence and has sent me back to you.

Reporting back so that anyone with Siteground may benefit.

After 4-5 hours of on again / off again chats and tickets and escalations they blame a recent migration and DNS propagation. I’m suspicious of that because it was one A record that was changed about 4 days ago at GoDaddy to point to Siteground’s new Google server. Never had a propagation last that long which leads me to wonder if it is a configuration issue.

My recommendation if you are a Siteground customer who they forced onto a new Google server and experience this issue is to put in a ticket about this and specifically ask for it to be escalated. My hope is after my incident and “Assertiveness” they have some documentation for their techs to either take care of the issue or advise you about the propagation. Dimitar Dimov
is a Technical Support Supervisor there and when he gave me the final report back on the ticket somehow magically the problem was fixed.

• This reply was modified 4 years, 8 months ago by sagency.

I am sorry to spam accross multiple tickets but the “issue” reported is the same so I will just quote my original reply.

Hristo from SiteGround here ??

There is no such thing as SiteGround configuration issue. We have migrated (almost) all our servers to Google Cloud Platform. There is an IP redirect in place for those customers who haven’t updated their A records. We’re fixing those with NS records pointed to us.

This is a regular redirect, triggering a false-positive error / warning on Wordfence’s plugin. Again, the brute force is another false-positive simply because ALL the traffic will be coming from the old server’s IP unless the A record is updated accordingly.

@hristo-sg
“There is an IP redirect in place for those customers who haven’t updated their A records.”

Our client properly changed their A record 4 days ago. Don’t you think an A record would have already propagated? Why would SSL be working if it hadn’t? All the DNS checkers indicated it was done, your own techs said it all looked fine, but the IP issue continued.

Was this a redirect somehow from your old server to the new Google one that was not removed in a timely fashion? Just trying to understand here and for the benefit of everyone else who runs across this warning in Wordfence.

• This reply was modified 4 years, 8 months ago by sagency.
• This reply was modified 4 years, 8 months ago by sagency.

Hey @sdagency,

Thanks for the updates.

Can you please check to make sure How Wordfence gets IPs is correctly identifying your IP? If it is, can you please try running the scan once more? You can check this in Wordfence > Tools > Diagnostics and Wordfence > All Options > How does Wordfence get IPs.

https://www.wordfence.com/help/dashboard/options/#general-wordfence-options

@hristo-sg – Thanks so much for chiming in and helping out. SiteGround is awesome!

Thanks,

Gerroald

@sdagency Hey mate! I am experiencing the same problem due to the siteground migration issue! will keep you posted on the outcome as suggested !

@wfgerald @dipaksaraf
The issue was resolved yesterday I think after a lot of persistence with Siteground escalation team. I really don’t think more propagation time after 4 days was the reason, it seems there is a temporary redirect Siteground puts in place so if people have their domain at another host the new server address will still work.

How and when that temporary redirect is removed by Siteground I don’t know, but in another post the Wordfence developer said other people contacted Siteground and *poof* the problem was gone. Leads me to believe there might be a way they can kill the original redirect which was mean to be helpful. I dunno. Server stuff is beyond me.

Siteground is a great host. Usually excellent service. Just some confusion over how this is happening and how some people seem to get it resolved with no issues and in my case it took about 4 hours of working with them between chats and tickets. 4 hours I could not bill my client.

@dipaksaraf I recommend making sure you update your domain settings exactly to the specs Siteground told you to and after 72 hours if IP detection is still off, contacting their escalation team and notifying them, asking them to check for a redirect issue.

• This reply was modified 4 years, 8 months ago by sagency.
• This reply was modified 4 years, 8 months ago by sagency.