Hey @orrton,
We’d love to take a look at this for you, but we need your site’s URL to do any kind of targeted troubleshooting.
Jetpack’s Protect function looks at the incoming IP address when you try to login, and compares it against our network of blocked IPs. This works pretty well, unless Jetpack’s Protect is being told the wrong IP address by your site’s server.
In some cases, hosts report their own IP address to Protect, which means that every single time someone with a WordPress site on the same hosting server as yours entered the wrong password, Protect thought it was the same person. If your hosting provider has several hundred WordPress sites on the same server/IP, that adds up fast, leading to a ban on the IP.
Thread Starter
orrton
(@orrton)
Hi @jenhooks,
Thanks for responding! That is interesting to know… the URL is http://waterpurificationguide.com/newposts
Any further help you can give would certainly be appreciated!!
Thank you. It does appear that are some configuration issues with the way your site stores and reports its visitors’ IP addresses. All visitors are currently identified with the same IP address, the address of the server where your site is hosted.
Could you reach out to your hosting provider, and ask them to take a look at your site’s configuration so IP headers (HTTP_X_FORWARDED_FOR, HTTP_X_REAL_IP, REMOTE_ADDR) can store and report the correct IP addresses of your site’s visitors?
Until that issue is fixed on your server, I’m afraid I can only recommend that you deactivate the Protect feature from your site.