Hi guys, my setup has been fine for ages but recently I keep getting short bans?
My setup is as follows
ExecStart=/usr/sbin/rclone mount gcrypt: /mnt/gdrive \
–buffer-size 512M \
–dir-cache-time 72h \
–drive-chunk-size 32M \
–log-level INFO \
–umask 002 \
–vfs-read-chunk-size 128M \
–vfs-read-chunk-size-limit off \
–drive-v2-download- min-size 0
ExecStop=/bin/fusermount -uz /mnt/gdrive
I’m getting a ban basically every day. I’m not doing full scans with Plex (using Plex_autoscan script) but I’m still getting booted off.
They don’t seem to be 24 hour bans, more like 8 hour bans or something? Anyone have any idea why? This setup has been working perfect for ages. Only one machine is connected to the drive too?
What’s the error message you are getting?
I full scan all the time so that isn’t it.
Do you use your own API key or the generic rclone key?
Do you have any logs during that time?
What version are you running?
Where you getting banned before you added –drive-v2-download- min-size 0?
Seemingly not, but I got a good week or so with it active with no bans!
I get the download quota reached error on drive (but weirdly I can still download some files).
I wasn’t using my own API key but I’ve switched to my own one now, haven’t tested since.
Don’t think so, what logs shall I collect?
And the latest beta version of rclone (or near enough!)
- os/arch: linux/amd64
- go version: go1.11.1
I got banned a couple of days ago also with 403s. I have my own API credentials. And there is no way that I exceeded any kind of limits. Since other folks are reporting issues, I’m guessing it was some kind of gdrive issue.
Try to add thes parameter in your rclone mount service:
Added this, still received another ban. Literally no-one else has access to my drive
Edit: sorry misfire, looks like somehow my credentials got fucked up this time
Can you share what your API dashboard looks like? If you hit quotas and check your quotas per hour graph, I’d be curious to see what that is.
That’s mine for the last day.
I’ll return to this in a few hours, turns out rclone had an issue with my credentials today., Looks to be working now
Can you share the specific log and error you see when this happens too?
Seems like adding my own API credentials has fixed the issues and actually sped up rclone immensely. Will leave it a few more days just to make sure but it does seem pretty sound again