Difficulties connecting to Google Drive API / client secret. That is, no matter how I input my OAuth credentials, Google won't proceed.... even when I scrap all existing projects, open up the account I want to access files from, create a testing project using that account, and follow all instructions in the setup. Google also constantly informs me that it is phasing out the existing OAuth system and encourages me to transfer to the new setup, saying the old system will be available for only a few more days.
When I log in with the correct Google account, I get this message:
Something went wrong
Sorry, something went wrong there. Try again.
I am about ready to storm Tokyo over this; my workflow has been completely kneecapped and I don't know why or how to fix it. I suspect Google updated and broke something, but I'm a researcher in a totally separate field just trying to make my familiar tools play nicely so I can do my job.
Run the command 'rclone version' and share the full output of the command.
Updated both my remote cluster's version of rclone and my local machine's version to 1.68.2 and tried again with the OAuth credentials... and got exactly the same Google error after correctly authenticating the account.
The suggestion to try local config was a good one, so I tried deleting and recreating the remote on my local machine. Got exactly the same error (" Something went wrong. Sorry, something went wrong there. Try again.") which is.... frustrating. Thanks, Google.
Thank you for the explanation of the rclone config request. Here's mine:
[MYdrive]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
team_drive =
token = XXX
[UMNdrive]
type = drive
scope = drive
token = XXX
team_drive = XXX
root_folder_id =
[breakfast]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
[mouseTV]
type = smb
host = XXX
pass = XXX
domain = XXX
[rds]
type = smb
host = XXX
pass = XXX
### Double check the config for sensitive info before posting publicly
I ran into this issue too, and the only thing that fixed it for me was opening the verification link in a chromium browser (brave, in this case). opening in firefox caused the "something went wrong" error, and same with opening in a fork of firefox (zen). just wanted to toss in my experience, just in case it helps someone else.