I have 36403 files I am trying to get backed up into my Google Drive. I have followed the steps at https://rclone.org/drive/ (under “Making your own client_id”) to make my own client ID and client secret. However, I never seem to get more than about 30% of the way through the backup set before rclone starts giving me 401 errors:
"error" : "invalid_client",
"error_description" : "The OAuth client was not found."
If I login to the Google API console, I can still see the client in there. If I do
rclone config and ask it to generate a new token - WITHOUT saying yes to editing the client ID and client secret - it will generate a token URL (this is a headless box) that gives me an HTTP
If I edit the client ID and client secret, and simply copy/paste the previous values as displayed by rclone, the token URL will work. I can then issue
rclone -v copy /mnt/zpool1/business crypt:/business, and it will run fine for a few hours, and then repeats the whole process from the beginning.
I can totally understand that I’m probably hitting some Google Rate Limit, but in my case I have the ownership of the Google Business account being used, so I could create more users/API keys, if rclone were able to round-robin between them, thus preventing me hitting the API limit. However, I can’t find any indication that this is a possible option; also, it doesn’t really explain to me why I have to issue an
rclone config and fake rclone into thinking I am editing the client ID and client secret in order to get a new, valid token. Can anyone help me understand what I’m doing wrong there? Also, is there any plan or mechanism in place to leverage multiple client IDs to get past the API rate limits?