429 google drive errors back for anyone using Hetzner, even with cloudflare or google dns used?

Well, that depends in which IP-Range your Server is. I did some research and got answers from several other users at Hetzner in different DCs in FSN, NBG and even HEL experiencing the 429's.

There is just a simple reason why Google is blacklisting these IP-Ranges: A lot of users are daily reaching there API/Upload Limits (at least 8 out of 10!) and running into the 403's. If more and more users are showing such behaviour Google will blacklist more and more IP-Ranges.

To avoid such Problems there are normally some simple rules every user should follow:

  1. Do NOT run into your limits every day!
  2. Do NOT share your things on your personal or Teamdrives!
  3. Do NOT hammer the API with tons of requests around the clock!

3 simple rules .... and if everyone would obeying them ... we wouldn´t have the problem now.

Just fyi: I tried to switch the routing of my google traffic back to the hetzner network ... and gues what: Still getting the 429's today.

Yes, there is:

You just had to look into the post before yours.

  1. Rent a good, cheap VPS with at least 1Gbps Bandwidth and enough included Traffic
  2. Setup a wireguard network using this: How to install WireGuard VPN on Ubuntu Server - MMOAPI.COM
  3. Once you´ve got your wireguard network running add the following networks to your clients wireguard configuration AllowedIPs:

IPv4: 142.250.0.0/15, 172.217.0.0/16
IPv6: 2a00:1450:4000::/37

Done.

Now you can route all your traffic for Google through your VPS using wireguard.

1 Like