Unable to upload to Gsuite as of a couple hours ago

Help and Support
103

If the DNS thing works for you, you dont have to limit bw or transfers at all.

105

yea.... was sorta afriad to test it... but i always limit the bandwidth and transfers to limit the impact on streaming from the server... : )

106

Similar problems here as others have stated. On Ubuntu 20.04, I was able to get everything moving again once I changed the DNS as mentioned by @plex-sender (editing netplan via sudo nano /etc/netplan/01-netcfg.yaml followed by sudo netplan apply).

I did NOT flush DNS but did reboot the server and found everything working so left it as is. I used the Cloudflare DNS and Google DNS as the user mentioned initially (1.1.1.1 and 8.8.8.8 respectively) which seemed to work for about 24h until I started having the errors again. Going through the other comments, I decided to stick with only Cloudflare servers so this morning changed it to:

  nameservers:
    addresses:
      - 1.0.0.1
      - 1.1.1.1

I also then ran sudo nano /etc/systemd/resolved.conf and modified the DNS line to DNS=1.0.0.1 1.1.1.1. Finally, I flushed DNS this time via sudo systemd-resolve --flush-caches and restarted the resolve service via sudo systemctl restart systemd-resolved.

After doing all that, I am back up and running again this morning so we'll see how long this lasts.

1 Like
107

I am also on HETZNER Cloud and need help to usw google API again.

I changed already dns to cloudfare and google without any success to usw rclone again with gdrive?

/etc/systemd/resolved.conf

[Resolve]
DNS=1.1.1.1 1.0.0.1
FallbackDNS=8.8.8.8

When I use the resolvectl status command it shows me:

Current DNS Server: 1.1.1.1             
DNS Servers: 1.1.1.1             
             1.0.0.1             
Fallback DNS Servers: 8.8.8.8

Can anybody help me and give me a hint what to change? What exactly do I have to change in the /etc/netplan/50-cloud-init.yaml?

Do I have to delete the other server under addresses:? Or do I have to add the cloudfare server?

THX

108

did you flush the dns cache?

109

The file you want to edit is /etc/netplan/01-netcfg.yaml. Mine looks like this after the edit (some info redacted):

### Hetzner Online GmbH installimage
network:
  version: 2
  renderer: networkd
  ethernets:
    enp2s0:
      addresses:
        - [REDACTED]
        - [REDACTED]
      routes:
        - on-link: true
          to: 0.0.0.0/0
          via: [REDACTED]
      gateway6: fe80::1
      nameservers:
        addresses:
          - 1.0.0.1
          - 1.1.1.1
110

Gdrive + Hetzner + Ubuntu 18.04.4 LTS checking in with the same issue.
I'm still trying to clear out my config files for entries from the Hetzner DNS servers. I've tried all the files I can find, so far, but I still get

185.12.64.2
185.12.64.1

Popping up into my systemd-resolve --status file. It shows 1.1.1.1 and 1.0.0.1 that I manually entered into the /etc/systemd/resolved.conf file.

Hopefully, I can find the errant DNS entries and fix this up, or I'd be happy enough to start finding a new host in the ~€30/mon price range.

111

did you clear the dns cache?

sudo systemd-resolve --flush-caches

i had the same issue and with cloudflare it works

3 Likes
112

Having (had) the same issues. Did the DNS trick and forgot to do that flush (thank you @Lunixx lol) and once I did, everything is working.

1 Like
113

yea that was my experience to.... had to flush the dns cache to get it working : )

been working flawlessly now for 2 days and over a terabyte on this end.. : )

1 Like
114

thank you very much - that hint helped! Now I am able to transfer files again to gdrive! Great solution with the DNS change

THX to help me out

2 Likes
115

That would be the nearing end of an era :frowning:

The new DNS also solved my issue. I hope google wont change anything soon.

116

Thanks, I did run the flush multiple times, and I still have records of Hetzer's DNS servers in my systemd-resolve.

That said, 15hrs later, I ran it again, and tested more files to upload, and no 429 errors. I'll keep an eye on the logs to see if it's actually resolved.

117

Is anyone else’s upload speed extremely slow since this has happened? I used to get 70-80MB/s now I’m barely getting 4 when trying to upload to Google Drive.

118

Still good speeds for me.

119

Yes, i have the same problem!
Everything else seems to be working now.

120

Unfortunately for me, a day later those rate limit messages are back. Your mileage may vary, but the DNS thing only worked for me for a day.

121

no issue for me, since dns change. maybe add some more flags

--drive-upload-cutoff 1000T
--user-agent "Some text for client name"

122

Hey @Lunixx

Thanks for the tips! I am going to try those now - just wondering what --user-agent "Some text for client name" means though? How is this used?

123

Set the user-agent to a specified string (default "rclone/v1.61.1")

so you can set whatever you want, like Mozilla/5.0 (Windows NT 10.0; Win64; x64)