We were just talking about this the other day. As I recall, it is a Siteground configuration issue and they have to do something on their side to address it. The users that have reached out to them no longer have the issue.
tim
Siteground is EMPHATIC this is not something they can fix and it’s Wordfence’s problem. I’ve wasted two hours on this. How do we get this fixed or do we have to just bail and go with All in One Security instead?
Siteground makes it so hard to to setup your plugin firewall with php.ini. Half the time we can do it ourselves and other times following the same directions they have to do it.
-
This reply was modified 6 years ago by
sagency.
@wfsupport
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 to their Google server 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 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 6 years ago by
sagency.
Hey @sdagency,
Thanks for the update, and for sharing the information. I’m going to close this thread and link to another one that SiteGround has chimed in to help on.
https://wordpress.org/support/topic/unable-to-accurately-detect-ips-type-ip-detection/
Thanks,
Gerroald