Google Drive Client ID /secret authentication suddenly no longer working, possibly result of recent Google changes in OAuth console?

[eringiglio]

What is the problem you are having with rclone?

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.

rclone v1.65.0
- os/version: rocky 8.10 (64 bit)
- os/kernel: 4.18.0-553.22.1.el8_10.x86_64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.21.4
- go/linking: static
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

Google Drive (specifically trying to set up a shared google drive)

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone config breakfast:

The rclone config contents with secrets removed.

scope:
I'm so sorry, I do not understand "rclone config contents." Here's what I get when I execute the rclone config command:

Current remotes:

Name                 Type
====                 ====
MYdrive              drive
UMNdrive             drive
breakfast            drive
mouseTV              smb
rds                  smb

The drive in question is the third drive. It is configured as a standard remote Google Drive shared drive, set up on a remote (headless) machine.

A log from the command with the -vv flag

The difficulty is authentication. I can't reproduce this as a command.

[asdffdsa (jojothehumanmonkey)]

welcome to the forum,

@eringiglio

rclone v1.65.0

that is an old version of rclone, so before calling this a bug, please

1. run rclone selfupdate
2. delete the non-working remote
3. re-create the remote from scratch

@eringiglio

I'm so sorry, I do not understand "rclone config contents

run rclone config redacted

@eringiglio

set up on a remote (headless) machine.

sometimes easier to https://rclone.org/remote_setup/#configuring-by-copying-the-config-file

[eringiglio]

Thank you so much, I really appreciate it!

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

And of course, the new version info:

rclone v1.68.2
- os/version: rocky 8.10 (64 bit)
- os/kernel: 4.18.0-553.22.1.el8_10.x86_64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.23.3
- go/linking: static
- go/tags: none

[asdffdsa (jojothehumanmonkey)]

@eringiglio

The suggestion to try local config was a good one, so I tried deleting and recreating the remote on my local machine

about the web browser, make sure to logout of google, clear cookies.
then, run rclone config -vv for debug output

@eringiglio

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.
Got exactly the same error (" Something went wrong. Sorry, something went wrong there. Try again.") which is.... frustrating

where did you get the error, rclone command line, web browser or what?
post a screenshot snippet of the error(s)

[eringiglio]

Web browser. Here we go:

Give me a sec and I'll try a reload.

[asdffdsa (jojothehumanmonkey)]

as a test with v1.86.2, i created a new gdrive remote using client_id+secret and ran rclone lsd remote:
that all worked, no problems.

[eringiglio]

Slept on it, cleared my browser, didn't help.

Then something occurred to me: I use Firefox most of the time. Switched to Chrome and it worked fine.

I have no idea, y'all, but thank you all for the help!

[asdffdsa (jojothehumanmonkey)]

@eringiglio

Then something occurred to me: I use Firefox most of the time. Switched to Chrome and it worked fine

ok, good you found a workaround, but i highly doubt that is the real issue.

i only use firefox, do not have chrome installed on my machine.
i have been creating gdrive remotes for 5+ years, never had an issue.

@asdffdsa

as a test with v1.86.2, i created a new gdrive remote using client_id+secret and ran rclone lsd remote:
that all worked, no problems.

i used firefox on that test.

[throwawaythrowaway]

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.