yes... bionic...
and the etc/resolv file there is a symlink and says anything you edit in here will be overwritten...
so i could just delete that and make a real file there and that would fix this you think?
Yes. I am positive about that.
For the unlikely case it does not work just take a note of the current symlink and recreate it if necessary.
Hi, same issue here.
After hint for dns (i've used 1.1.1.1,8.8.8.8) and some tuning on config file helped me to fix the issue for now
config:
ExecStart=/usr/bin/rclone move /home/redacted/redacted/locale/ gdrive:Backups
--config=/home/redacted/.config/rclone/rclone.conf
--drive-chunk-size 256M
--tpslimit 5
--drive-upload-cutoff 1000T
--drive-acknowledge-abuse=true
-vvv
--delete-empty-src-dirs
##--fast-list
--bwlimit=50M
--use-mmap
--transfers=4
--checkers=8
--user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 Edg/109.0.1518.70"
##--max-transfer 740G
--drive-stop-on-upload-limit \
thanks for the dns idea.
if someone is not sure for dns in use can run this: resolvectl status
Cheers.
ha.... so your saying there might be a chance it won't work? : ) : (
would i still be able to login if it doesnt work? (i'm not a linux expert at all... but assuming yes, as you use an ip address to login remotely)
You just need to remove the symlink and recreate the file. It will work, since it won’t get overwritten
1 Like
Well, "never say never" I guess 
As for my experience doing this never failed on me.
You can also set multiple DNS servers in this file just in case one is failing. For example
nameserver 1.1.1.1
nameserver 1.0.0.1
Take note when doing this resolvectl will NO LONGER give correct results about the DNS server in use. The reason is that this tool simply asks resolved about the current configuration. However since resolv.conf does no longer point to resolved it cannot know that is not even used anymore.
As mentioned use nslookup on a random domain to get used DNS server for that query.
1 Like
So last night after switching to Cloudflare DNS (1.1.1.1 and fallback to 1.0.0.1) and flushing DNS cache, there was no change. I then killed all my services that use my rclone mounts and let the mounts sit with the cached files. This morning the files had been written back to the remote, and when doing the 4 GB bin file upload test, it succeeded with no issues. The issue seems to be resolved for me, for now at least. I'm on Ubuntu 22.04.1 LTS, I changed the global DNS via /etc/systemd/resolved.conf and changed the DNS for my ethernet adapter via /etc/netplan/01-netcfg.yaml. I had to restart and flush cache for resolved and had to netplan try and netplan apply for netplan.
Update: 4 hours later and still no issues.
Interesting how many different ways in Ubuntu seems to help. I am on 22.04 as well and netplan only did not help. I deleted symlink for /etc/resolv.conf and made it a real file in addition to the netplan changes. Now i can upload again (just uploaded 200gb), but due to several remounts i ran into a DownloadQuotaExceeded error 
Guess API hits where to heavy.
On Debian 11 I only changed the DNS in /etc/resolv.conf and worked like a charm... for now. I've actually been having that issue for a few days now, trying many many times a day worked so far, but the DNS solution is better.
Thanks fuck I only came here to check if I just totally went over the edge with my usecase or if there is something known to this new sudden issue and look: here we go.
I had my Plex server already switched to CF DNS since 2 days ago, ironically without knowing anything about this here, and it still seems to have issues tho. I just switched the Upload Server's DNS as well and will keep an eye on it.
For Ubuntu 22.04 on Hetzner, it uses netplan by default so just edit the file in /etc/netplan/01-netcfg.yaml and do netplan try and netplan apply.
In the worst case I could attach the gclone Container to gluetun using OVPN, but I have no mount containers yet for Plex.
i am also using ubuntu 22.04, but i dont see 01-netcfg.yaml file in the netplan folder, i only see this file "50-cloud-init.yaml." (are they similar) Do i need to create a new file called 01-netcfg.yaml and insert the dns?
Thanks
Regards..
worked perfectly for me as well as i slept it naturally hit the 750 gig mark with no issues 
so is anybody who has changed to cloudflare, rebooted, flushed the cache and verified they are using 1.1.1.1 at the moment they start a move... still having this issue?
i'm wondering if the ones who had problems, still got the error or who had the error return after a bit, hadn't got switched back to the hetzner dns servers randomly?
(which is what happened to me last night on my second move, when i got the errors again, freaked out, then checked the active dns ... and SOMEHOW, thats beyond me, without a reboot even.. the dns had gotten switched back to hetzner!?
changed it back to cloudflare again, and all was well with the world : )
I have not rebooted but switched DNS and flushed cache and still have it.
That's the Hetzner Dedicated Server default. Yours might be different ofc
I suspect that all people that are still having that issue were either hit by a temporary API IP ban due to the errors happening with the Hetzner DNS, or have not changed their DNS server properly.
What comes to mind as well, would be some sort of shared IP that is causing the bans. I don't know if VPS servers generally at Hetzner have a shared IP (with other VPS), but that could certainly be an issue.
I suspect that nobody with a root server who has properly switch the DNS server is still facing the issue. My VM backups are pretty large and I have practically uploaded all night long without a single issue (on multiple of our hypervisors).
1 Like
have you verified the cloudflare dns is actually the one being used?
Yeah ofc. No idea how people face trouble that it is being reverted, since my main Plex server with the DNS change from 2 days ago also still runs CF. That info is taken from resolvectl status:
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (eno1)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 1.1.1.1
DNS Servers: 1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001
maybe youve answered this already (if so forgive me im getting everyone mixed up at this point) : ) : (
but have you disconnected everything from gdrive and do a simple move with bandwidth limited to 35mbs and transfers to 1.
I have tried that too, and it didnt work.
No sorry, that's not too easy to do in my slightly larger setup 