[Action Required] Migrate your impacted OAuth out-of-band flow to an alternative method before Oct. 3, 2022

What is the problem you are having with rclone?

What does this mean and how do I fix it? Just got this email today.

Run the command 'rclone version' and share the full output of the command.

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

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

Paste command here

The rclone config contents with secrets removed.

Paste config here

A log from the command with the -vv flag

Paste  log here

hello and welcome to the forum,

that has been discussed forum,

and from the change log

1 Like

Hi @asdffdsa
I reviewed the links you have provided but I couldn't understand if there is anything we should do.
I use rclone 1.57 with Goggle Drive. Does upgrade to 1.58 will solve the issue with Goggle new Auth method?


hello and welcome to the forum,

using v1.57.0, could try rclone authorize

tho i would update rclone and test.
if the problem persists, then i would run
rclone authorize

Thanks for replying.
Not sure I understand what you mean about the problem persistent.

I have like 10 clients connected to gDrive at the moment, no issues.
But I also received this email saying they will deprecate the OOB.
So I'm not sure If there is anything I need to do in order to keep my clients working after Oct-2nd.

So if we are on rclone version 1.58+ we are good ? Can someone clearly confirm this since i also get this email from google.

Hi @asdffdsa
Appreciate your help here, please.


I think the above thread answers any and all questions.

You don't have to do anything if you use 1.58 or newer. You also don't have to do anything if you use 1.57 or older and don't plan on reconfiguring Rclone remotely.

I never received this email, btw. Is this because I never used remote authentication?

can you please explain how 1.58 solve this issue?

From the 1.58 release notes:


  • Disable OAuth OOB flow (copy a token) due to Google deprecation (Nick Craig-Wood)

It's not so much a fix as it simply doesn't allow you to use this Google-deprecated feature any longer. Any version older than 1.58 would still allow you to do it, thereby running into issues. 1.58 and newer will prevent you from doing so.

That's how I understand it anyway.

Hi @VBB ,
Thanks for the reply.
So basically everything in the flow to configure access to gDrive should be as it is today?

Thanks again,

Yes, as long as you use 1.58 or newer.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.