djanem
Forum Replies Created
-
Received the following response from Wordfence which seems to be specific to Bluehost. Followed their recommendations and it worked so wanted to share with others:
Very sorry to hear you are experiencing this issue. Are you with Bluehost? We have since back in December seen some issues on Bluehost because they install something called Endurance cache and some version of this cache is too aggressive and will actually cache the Wordfence blocked page and then serve it to every visitor to the site. This is why it doesn’t change when you deactivate Wordfence. It’s not actually Wordfence that is serving the page, it’s the cache. We believe that it is one of the early versions of Endurance cache that is faulty, but it seems like on many sites it has not been upgraded to newer versions.
The easiest way to solve this may be to contact Bluehost and ask them to remove the faulting Endurance Cache from your website. If you want to try disabling it yourself you can:
1. Look in wp-content/mu-plugins and delete the endurance cache plugins from there
2. Check your .htaccess and manually remove any trace of the Endurance cacheHere’s the message:
Your access to this site has been limited
Your access to this service has been temporarily limited. Please try again in a few minutes. (HTTP response code 503)
Reason: Access from your area has been temporarily limited for security reasons.
Important note for site admins: If you are the administrator of this website note that your access has been limited because you broke one of the Wordfence advanced blocking rules. The reason your access was limited is: “Access from your area has been temporarily limited for security reasons.”.
If this is a false positive, meaning that your access to your own site has been limited incorrectly, then you will need to regain access to your site, go to the Wordfence “options” page, go to the section for Rate Limiting Rules and disable the rule that caused you to be blocked. For example, if you were blocked because it was detected that you are a fake Google crawler, then disable the rule that blocks fake google crawlers. Or if you were blocked because you were accessing your site too quickly, then increase the number of accesses allowed per minute.
If you’re still having trouble, then simply disable the Wordfence advanced blocking and you will still benefit from the other security features that Wordfence provides.
If you are a site administrator and have been accidentally locked out, please enter your email in the box below and click “Send”. If the email address you enter belongs to a known site administrator or someone set to receive Wordfence alerts, we will send you an email to help you regain access. Please read this FAQ entry if this does not work.
This response was generated by Wordfence.
Forum: Plugins
In reply to: [Authenticator for WordPress] Invalid authentication tokenI get the same thing. I had to deactivate the plug-in because I couldn’t get it to work with my Google Authenticator app. I tried manually adding the key as well and that didn’t work either.