• A handful of my sites using wordfence is giving this error.

    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: Fake Google crawler automatically blocked

    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 firewall rules. The reason you access was limited is: “Fake Google crawler automatically blocked”.

    I have not changed setting or anything recently but this is after most recent update. And obviously it’s me, site admin trying to acess the site. should I be disabling this feature to prevent this?
    is this an bug on newest version?

    https://wordpress.org/plugins/wordfence/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter bulewold

    (@bulewold)

    On top of that, it seems like wordfence is adding my server IP to deny list within htaccess???

    causing everything to just error out…

    I went in there and manually removed and fake google crawler block came out… this is very weird…

    I’m having the same issue on one of my sites. I disabled the “Fake Google crawler automatically blocked” setting and that seemed to work.

    Plugin Author WFMattR

    (@wfmattr)

    @bulewold: It sounds like your site is using a “reverse proxy”, so Wordfence cannot see the visitors’ actual IP addresses. You will need to set the option “How does Wordfence get IPs” on the Wordfence Options page. Depending on what software your server is using, you probably need to choose the X-Real-IP or X-Forwarded-For option. More details on the options are here:
    How does Wordfence get IPs

    After setting the option, you can verify it is working by looking at the Live Traffic page, and visiting the site in a separate browser where you are not logged in, and verify that your own IP appears in your own visits. (If Live Traffic is disabled, try logging in using the second browser, since logins and logouts are still recorded.)

    @sylviabass: Thanks for pitching in — this may be the same case for your site as well. Disabling the “fake google crawler” option is a good temporary solution. Some other features can be affected by incorrect IP addresses coming through as well. (There is a similar case if you use CloudFlare, and there is a separate option in the “How does Wordfence get IPs” field for sites with CloudFlare too.)

    -Matt R

    Thread Starter bulewold

    (@bulewold)

    What about the behavior that WF was adding my server IP as deny? I had to add my own server IP where website is hosted into whitelist to prevent this from happening.

    Plugin Author WFMattR

    (@wfmattr)

    That is usually what happens if the server has a reverse proxy. Basically, the visitor reaches the proxy (like Varnish) instead of reaching your web server, then Varnish connects to the web server, so Wordfence sees the IP where Varnish is. (There are other similar proxies, but this is the one we hear about most.)

    Did you get to try the option I mentioned, and check Live Traffic, to see if it changes how the visitors’ IPs are showing up for new visits?

    -Matt R

    Thread Starter bulewold

    (@bulewold)

    Gotcha. So the whole thing is probably caused by Varnish since I do have that enabled.

    I haven’t check live traffic since i have falcon engine enbaled…. But I added my server ip to whitelist and turned off block google fakebot and had no trouble ever since.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘fake googlebot error’ is closed to new replies.