Title: Blocking Chrome
Last modified: August 31, 2016

---

# Blocking Chrome

 *  Resolved [geopal](https://wordpress.org/support/users/geopal/)
 * (@geopal)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/blocking-chrome/)
 * Plugin just blocked Google Chrome!
    Is it normal?
 * Request URI: /?blackhole=a062fccfbb
    IP Address: xxx.xx.xxx.xxx User Agent: Mozilla/
   5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109
   Safari/537.36
 * [https://wordpress.org/plugins/blackhole-bad-bots/](https://wordpress.org/plugins/blackhole-bad-bots/)

Viewing 8 replies - 1 through 8 (of 8 total)

 *  [Michael](https://wordpress.org/support/users/mkalina/)
 * (@mkalina)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7082903)
 * Just got a similar e-Mail:
 * > 2016/02/19 @ 09:28:23 pm
   > Request URI: /?blackhole=e9ef8840d4
   >  IP Address: REDACTED User Agent: Mozilla/
   > 5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko)
   > Chrome/41.0.2272.89 Safari/537.36
   > Whois Lookup:
   > Deferred to specific whois server: whois.ripe.net…
   > % This is the RIPE Database query service.
   >  % The objects are in RPSL format.%%
   > The RIPE Database is subject to Terms and Conditions. % See [http://www.ripe.net/db/support/db-terms-conditions.pdf](http://www.ripe.net/db/support/db-terms-conditions.pdf)
   > %ERROR:106: no search key specified
   >  % % No search key specified
   > % This query was served by the RIPE Database Query Service version 1.85.1 (
   > DB-3)
 *  Plugin Author [Jeff Starr](https://wordpress.org/support/users/specialk/)
 * (@specialk)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7083002)
 * [@geopal](https://wordpress.org/support/users/geopal/):
 * Actually that’s not how it works. The plugin only blocks by IP address. Not by
   User Agent. No Chrome users are blocked except for the one person or bot who 
   is reported as using Chrome. Again, this plugin does not block by User Agent,
   only by IP.
 * [@michael](https://wordpress.org/support/users/michael/):
 * That error comes from the geo-lookup service and just means that there was an
   error with the IP lookup. There is not much to be done about it, but understand
   that it does not affect the functionality of the plugin. It just means that a
   lookup fails, which is to be expected every now and then. If it keeps happening
   for every lookup, then please let me know; there are other lookup services that
   we can try as alternates.
 * Thanks for the feedback from both of you.
 *  [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7083036)
 * I am seeing something similar. After getting two email reports of bad bots blocked,
   we started receiving emails from our users that they’ve been banned from the 
   site. When logged-out, I am also getting banned on my Chrome.
 * Clearing page cache and varnish does not solve the issue. Only when I deleted
   the two “bad bots” from the list, were I able to access the site again. It seems
   that the “IP based filtering” either doesn’t work, or the user agent detection
   is mistreating my Chrome for a bad bot’s user agent…
 * I am deactivating the plugin for now… just to be on the safe side…
 *  Plugin Author [Jeff Starr](https://wordpress.org/support/users/specialk/)
 * (@specialk)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7083048)
 * Hi Bowo, the plugin only blocks IP addresses. So if your visitors are visiting
   the Blackhole, they are going to get blocked. Again, the plugin does not block
   by user agent, so there is no way that Chrome would be blocked. It’s all based
   on IP address.
 *  [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7083049)
 * Thanks Jeff. I will test the plugin again on another occasion. It is still an
   attractive solution. I just don’t want to take any risk on this particular site,
   and it appears that the performance issue we had earlier is not caused by bad
   bots, so we are good for now.
 *  [abulaye](https://wordpress.org/support/users/abulaye/)
 * (@abulaye)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7083080)
 * Hi, I’ve been having the same issue as posted by Michael and Bowo. First, when
   I installed the plugin I tested the link and it just delivered the page with 
   the message, since I was logged-in it was easy to clear my IP, but after I logged-
   out I was denied access, so I had to remove the plugin and still suffering the
   same problem. To make things worse, the day that I activated the plugin pretty
   much everybody had access denied, including authors and user of the blog, I got
   word of the problem thanks to my readers. Since then I tried several other times
   to re-activate the plugin but the problem still remains.
    Also, there are blaclisted
   IPs that I’m not able to remove using the plugin settings. Regards EGA
 *  Plugin Author [Jeff Starr](https://wordpress.org/support/users/specialk/)
 * (@specialk)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7083081)
 * Hi abulaye, it sounds like you are running a caching plugin, correct? If so, 
   Blackhole is not yet compatible (but will be in a future update). I recommend
   uninstalling until the plugin is compatible. Uninstalling will remove all plugin
   settings and all blacklisted IP addresses.
 *  [abulaye](https://wordpress.org/support/users/abulaye/)
 * (@abulaye)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7083082)
 * Hi Jeff, thanks for replying, I don’t have yet activated any caching plugin yet,
   but the host that I use does have Varnish Caching. So I will wait until you got
   that new version. Thanks a lot for your advice
    Regards EGA

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Blocking Chrome’ is closed to new replies.

 * ![](https://ps.w.org/blackhole-bad-bots/assets/icon-256x256.png?rev=1471215)
 * [Blackhole for Bad Bots](https://wordpress.org/plugins/blackhole-bad-bots/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/blackhole-bad-bots/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/blackhole-bad-bots/)
 * [Active Topics](https://wordpress.org/support/plugin/blackhole-bad-bots/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/blackhole-bad-bots/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/blackhole-bad-bots/reviews/)

 * 8 replies
 * 5 participants
 * Last reply from: [abulaye](https://wordpress.org/support/users/abulaye/)
 * Last activity: [9 years, 10 months ago](https://wordpress.org/support/topic/blocking-chrome/#post-7083082)
 * Status: resolved