Scope errors while installing Google Drive

Help and Support
1

Hi,

I tried to install Google Drive according to rclone config but it failed with this error:

Error creating config. Error: Request failed with status code 500

The opened Google login site reported this error:

Some requested scopes were invalid. {invalid=[https://www.googleapis.com/auth/https://www.googleapis.com/auth/docs, https://www.googleapis.com/auth/https://www.googleapis.com/auth/drive.metadata.readonly, https://www.googleapis.com/auth/https://www.googleapis.com/auth/drive]} Weitere Informationen zu diesem Fehler

Wenn Sie Entwickler von rclone sind, finden Sie in den Fehlerdetails weitere Informationen.

Fehler 400: invalid_scope

What’s wrong with it?

2

hi,
when you posted there was a template of questions for you to answer?

3

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

rclone v1.68.1

  • os/version: Microsoft Windows 10 Home 22H2 (64 bit)

  • os/kernel: 10.0.19045.5131 (x86_64)

  • os/type: windows

  • os/arch: amd64

  • go/version: go1.23.1

  • go/linking: static

  • go/tags: cmount

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

Google Drive

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


rclone rcd --rc-web-gui

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.


[GoogleDrive]

type = drive

client_secret = XXX

scope = https://www.googleapis.com/auth/docs,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.metadata.readonly

token =

client_id = XXX
4

what is that??
check the rclone docs for valid parameters and syntax

5

If you want to add all at once, comma separated it would be https://www.googleapis.com/auth/docs,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.metadata.readonly.

6

scope

7

It's much easier to not use rcd and just use the command to get going.

The values are not the full values you've shared as they are looking for:

Scope that rclone should use when requesting access from drive.
Choose a number from below, or type in your own value
 1 / Full access all files, excluding Application Data Folder.
   \ "drive"
 2 / Read-only access to file metadata and file contents.
   \ "drive.readonly"
   / Access to files created by rclone only.
 3 | These are visible in the drive website.
   | File authorization is revoked when the user deauthorizes the app.
   \ "drive.file"
   / Allows read and write access to the Application Data folder.
 4 | This is not visible in the drive website.
   \ "drive.appfolder"
   / Allows read-only access to file metadata but
 5 | does not allow any access to read or download file content.
   \ "drive.metadata.readonly"

Google drive

What are you trying to scope as you have things that don't really make sense together?

8

rclone config redacted

[GoogleDrive]

type = drive

client_secret = XXX

scope = drive

token =

client_id = XXX

rclone lsd GoogleDrive:

CRITICAL: Failed to create file system for "GoogleDrive:": drive: failed when making oauth client: failed to create oauth client: empty token found - please run "rclone config reconnect GoogleDrive:"

9

Did you run?

DId you just edit the file? Did you start with a fresh remote from a command line?

10

I just used "rclone config reconnect GoogleDrive:" to log into Google and Google said “Success! All done. Please go back to rclone.“ but still get the same error.

11

So then the file changed to 'drive' with zero intervention as you said you only ran:

This gets much easier as rather than sharing the least amount of information possible, you actually answer questions a bit more and take the time.

My recommendations.

  1. use the command line
  2. make a brand new remote
  3. test that new remote
12

rclone_1
rclone_1930×452 75.3 KB

"Failed to get token" error

13

I tried several times, always with the same token error. In the rclone document it states:

Be aware that, due to the "enhanced security" recently introduced by Google, you are theoretically expected to "submit your app for verification" and then wait a few weeks(!) for their response; in practice, you can go right ahead and use the client ID and client secret with rclone, the only issue will be a very scary confirmation screen shown when you connect via your browser for rclone to be able to get its token-id (but as this only happens during the remote configuration, it's not such a big deal). Keeping the application in "Testing" will work as well, but the limitation is that any grants will expire after a week, which can be annoying to refresh constantly. If, for whatever reason, a short grant time is not a problem, then keeping the application in testing mode would also be sufficient.

Is this the problem I’m encountering?

14

Does your config work for one week and then stops?:slight_smile:

It looks like you are doing something wrong indeed. Delete everything and try again... You make some mistake but it is hard to tell when and where.

Maybe this micro guide will help to take fresh look at client_id creation:

15

It didn’t work at all, from the first moment. That’s why I’m so upset. I just can’t understand shy Google reports success after my configuration.

16

It works for myself and many others. So most likely problem is between keyboard and chair in your case. Not rclone, nor Google.

It can be a bit hard to configure it right the first time. You are not the only one. Delete everything. Start again - carefully do everything step by step. It will work.

17

{A9387B41-C456-4C4F-857B-38B6CA614281}

could be a network issue on your end. internet, proxy server, etc...