verihy
By:
verihy

Google "We're sorry" issue

December 31, 2014 2.6k views

I got the message
"We're sorry...
... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now."
from Google when visiting http://scholar.google.com. This situation lasts for a long time and I've tried other methods like "disable ipv6", but not fixed.

5 comments
  • Hi! If you could provide more information, we might be able to help you better. Is this occuring on a DigitalOcean droplet? Are you using it as a remote desktop or are you doing some kind of automated scraping?

  • I encountered the same problem, as I switched from a NY droplet to a SFO. I live in China, you know, a place where Google cannot be reached. So I used DO as my personal gateway to access Google.com.

    It seems that Google has blocked the traffic from some IP ranges belonging to DO to its scholar search. I suggest you negotiate with Google.com, since they are likely to ignore the claims from individual users.

  • it appears that google is blocking a range of I.P.'s from digital ocean, as both my droplets are experiencing this. Perhaps one or more Digital Ocean subscribers are ruining things for the rest of us?

    For informational purposes, I'm running two servers, one I use as a VPN, the other just has a minecraft server on it, both have had a full network rundown an show no connections to google.

    the clients I connect with (linux an android) also show no active connections to google unless I try to initiate one.

  • I have the same problem, running a DO vpn server in Amsterdam. I notice multiple posts in the community about this issue, has this ever been addressed by DO?

  • Same issue with VPN in Amsterdam too... :(

5 Answers

and i have this problem too,so sad

This seems to be an issue in the NYC datacenter at the moment. I've posted on the google websearch help forum, but it might be helpful if someone from digitalocean staff were to reach out to google as well, and offer to work with them on finding what users are abusing the service in order to get them to unban all of digitalocean.

Just started happening to me this week. My droplet is in the NYC3 Region.

I have the same problem, running a DO vpn server in Amsterdam. I notice multiple posts in the community about this issue, has this ever been addressed by DO?

Have another answer? Share your knowledge.