Hi, what DNS server are you using on Hetzner, have you static entries in your host file? I had this VPN working well using the same VPS provider using Cloudflare DNS but then 2 weeks later it started giving 429s
Hey,
i´m using the CF DNS Servers on every one of my servers, regardless if they are at Hetzner or on other locations. I do NOT have static entries in my hosts files.
If you get the 429s again it shows that the traffic is not routed through wireguard.
In the meantime I rented a second VPS and now I´m splitting the traffic through both VPS ... with that I have 80TB of traffic each month 
Ok, I am watching it here and not all my uploads to googleapis.com are going over the tunnel. This is from my wg-client.conf
AllowedIPs = 172.26.3.155/16,142.250.0.0/15,172.217.0.0/16,216.58.192.0/19
And here is the output of a lookup
Non-authoritative answer:
Name: www.googleapis.com
Address: 142.250.185.234
Name: www.googleapis.com
Address: 172.217.16.138
Name: www.googleapis.com
Address: 142.250.186.138
Name: www.googleapis.com
Address: 172.217.18.10
Name: www.googleapis.com
Address: 142.250.181.234
Name: www.googleapis.com
Address: 142.250.185.170
Name: www.googleapis.com
Address: 142.250.186.170
Name: www.googleapis.com
Address: 142.250.186.106
Name: www.googleapis.com
Address: 172.217.16.202
Name: www.googleapis.com
Address: 142.250.186.42
Name: www.googleapis.com
Address: 142.250.185.74
Name: www.googleapis.com
Address: 142.250.185.202
Name: www.googleapis.com
Address: 142.250.185.138
Name: www.googleapis.com
Address: 142.250.186.74
Name: www.googleapis.com
Address: 142.250.184.202
Name: www.googleapis.com
Address: 142.250.185.106
So do you have IPv6 enabled on your network interface from your server? If yes, the IPv6 traffic won’t be routed via wireguard if you have not configured wireguard for IPv6 also.
Disable IPv6 on your server or add IPv6 support to your wireguard setup.
Ok that was it, I disabled ipv6, all going over the tunnel now
For the future I would recommend to enable IPv6 via Wireguard also as you will have more connections to googles API when using v4 and v6 simultanously.
Yeah, that's the plan, I've just not got my head around IPV6 yet
1 Like
Here is a quick guide i made based on googling, research and other guides
2 Likes
still perfect on my hetzner... since adding the like 5 original ips someone suggested to add in the hosts file... like 2 months ago... haven't even had to add/change those...
how is everyone else doing atm?
Still fighting the 429s without wireguard ...
And what is your upload speed to Google?
like 100 megs if i want to... but i alwats cap my bandwidth at 35 megs so as not to interfere with streaming etc : )
still working perfectly with the first batch of ips the first one that suggested the hosts file edit....
i'm convinced there is another variable here...
I have two servers @ hetzner
1st with modified dns servers and the hosts file hack (as I got 429 errors as many of us):
2nd, brand new box, no modification, out of the box ubuntu linux install with the latest rclone (--bwlimit 15M):
but no 429 google drive errors on both
@alneven can you tell me more details about the instance that works? I have two dedicated auction servers (One in FSN-DC1 and one in HEL1-DC2) from hetzner and they are both getting the 429 error.
I tried the above mentioned fixes bit haven't found one which works.
I also have an oracle cloud instance (the free one) as the alternative planned but it's ARM based and i don't have the best experience with it at the moment.
It is an auction server, and it is located in FSN1-DC11 (the other one is DC7)
I started noticing this problem today,
I don't know if it's been affecting me longer, as it wasn't until I jumped on my server to troubleshoot a different issue, and tailed syslog, that I saw all these errors.
Sure enough vfc/stats shows a queue of uploads that it's waiting to process.
My server is in HEL1-DC3, in case anyone's interested.
Think I'm going to go down the VPS split tunnel route to resolve this, and possibly look to move away from Hetzner completely if google are going to block whole IP ranges for a few bad apples.
I just started getting this issue now too
geez, now I had this on my new server last night as well
I had issues yesterday (noticed yesterday could've been an issue for days) started getting 429s while using VPN. I quickly uncommented the googleapis IP addresses in the host file to get it working as I don't have time to diagnose. I'll investigate at the weekend
Did everyone else who was getting 429's also get slapped with the "Pooled storage limit exceeded" emails.
I'm wondering if Google is taking a stance against Hetzner users, or if I was just unlucky.