NO access to Gdrive

Help and Support
1

What is the problem you are having with rclone?

Hello

for some background. I have a google workspace account that I had connected to rclone: it is also encrypted.

so it looks like this:

Gdrive - drive

gdrivecrypt - crypt

But for some reason I can't get access.

I don't know if its the tokens or somethng else.

I have tried many attempts following the guides:

rclone gdrive setup workspace

If I erase the config file in my pc and start new and connect to my Gdrive account will it delete both remotes (Gdrive and crypt)

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

rclone v1.68.1

  • os/version: Microsoft Windows 10 Pro 22H2 (64 bit)
  • os/kernel: 10.0.19045.4894 (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 (workspace account)

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

rclone config reconnect nameofyourremote: -vv

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

[Gdrive]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
token = XXX
team_drive =
service_account_file = C:\Users\XYZ\Downloads\xxxxxxxxxxxxx.json

[gdrivecrypt]
type = crypt
remote = Gdrive:
filename_encryption = standard
directory_name_encryption = true
password = XXX
password2 = XXX
### Double check the config for sensitive info before posting publicly

A log from the command that you were trying to run with the -vv flag

2024/10/01 20:45:50 DEBUG : rclone: Version "v1.68.1" starting with parameters ["rclone" "config" "reconnect" "Gdrive:" "-vv"]
2024/10/01 20:45:50 DEBUG : Using config file from "C:\\Users\\XYZ\\AppData\\Roaming\\rclone\\rclone.conf"
2024/10/01 20:45:50 DEBUG : Gdrive: config in: state="", result=""
2024/10/01 20:45:50 DEBUG : Gdrive: config out: out=&{State:teamdrive Option:<nil> OAuth:<nil> Error: Result:}, err=<nil>
2024/10/01 20:45:50 DEBUG : Gdrive: config in: state="teamdrive", result=""
2024/10/01 20:45:50 DEBUG : Gdrive: config out: out=&{State:teamdrive_ok Option:false OAuth:<nil> Error: Result:}, err=<nil>
2024/10/01 20:45:50 DEBUG : Gdrive: config: reading config parameter "config_change_team_drive"
Configure this as a Shared Drive (Team Drive)?

y) Yes
n) No (default)
y/n> n

2024/10/01 20:46:01 DEBUG : Gdrive: config in: state="teamdrive_ok", result="false"
2024/10/01 20:46:01 DEBUG : Saving config "team_drive" in section "Gdrive" of the config file
2024/10/01 20:46:01 DEBUG : Keeping previous permissions for config file: -rw-rw-rw-
2024/10/01 20:46:01 DEBUG : Gdrive: config out: out=<nil>, err=<nil>
2024/10/01 20:46:01 DEBUG : rclone: Version "v1.68.1" finishing with parameters ["rclone" "config" "reconnect" "Gdrive:" "-vv"]
2

welcome to the forum,

check the rclone docs at https://rclone.org/drive/#3-configure-rclone-assuming-a-new-install

that when using a service account file, the rclone remote should not have the following.

client_id = XXX
client_secret = XXX
token = XXX

this is what my remote looks like

[gdrivesa]
type = drive
scope = drive
service_account_file = c:\data\rclone\other\gdrive.sa\testunv-d0540da87aac.json
3

In my description I have those present. It says those things. The link that you provided is the one in my description.

4

afiak, those should not be present.
tho, i could be wrong

client_id>       # Can be left blank
client_secret>   # Can be left blank

afiak, service accounts do not use tokens.
the example remote in the link does not have a token.

5

I'm sorry but I'm confused. When I checked my info I had a token that expired. So I don't know how to work these things. It was fine before. Would it be better if I reset this.

7

Here is mine:
rclone lsd Gdrive: -vv
2024/10/01 21:30:42 DEBUG : rclone: Version "v1.68.1" starting with parameters ["rclone" "lsd" "Gdrive:" "-vv"]
2024/10/01 21:30:42 DEBUG : Creating backend with remote "Gdrive:"
2024/10/01 21:30:42 DEBUG : Using config file from "C:\Users\XYZ\AppData\Roaming\rclone\rclone.conf"
2024/10/01 21:30:42 DEBUG : Google drive root '': 'root_folder_id = 123456ABC' - save this in the config to speed up startup
2024/10/01 21:30:42 DEBUG : 6 go routines active

8

ok, that looks good, so what do you need help with?

9

I can't get into my remote. LOL

10

you just posted the output of a working command, so you can access the remote...

sorry, no idea what that means, what do you need help with?

11

I can't see any of the files. they are still encrypted in gdrive though.

12

that is because you are using the wrong command.

to list files, use rclone ls

13

rclone ls Gdrive:

{blank}

rclone ls gdrivecrypt:

{blank}

nothing shows up

14

post the full output of rclone ls Gdrive: -vv

15

C:\Program Files\rclone-v1.60.1-windows-amd64>rclone ls Gdrive: -vv
2024/10/01 21:53:52 DEBUG : rclone: Version "v1.68.1" starting with parameters ["rclone" "ls" "Gdrive:" "-vv"]
2024/10/01 21:53:52 DEBUG : Creating backend with remote "Gdrive:"
2024/10/01 21:53:52 DEBUG : Using config file from "C:\Users\XYZ\AppData\Roaming\rclone\rclone.conf"
2024/10/01 21:53:52 DEBUG : Google drive root '': 'root_folder_id = xxxxxxxxxxxxx' - save this in the config to speed up startup
2024/10/01 21:53:52 DEBUG : 6 go routines active

C:\Program Files\rclone-v1.60.1-windows-amd64>rclone ls gdrivecrypt: -vv
2024/10/01 21:54:07 DEBUG : rclone: Version "v1.68.1" starting with parameters ["rclone" "ls" "gdrivecrypt:" "-vv"]
2024/10/01 21:54:07 DEBUG : Creating backend with remote "gdrivecrypt:"
2024/10/01 21:54:07 DEBUG : Using config file from "C:\Users\XYZ\AppData\Roaming\rclone\rclone.conf"
2024/10/01 21:54:07 DEBUG : Creating backend with remote "Gdrive:"
2024/10/01 21:54:07 DEBUG : Google drive root '': 'root_folder_id = xxxxxxxxxxxxxxx' - save this in the config to speed up startup
2024/10/01 21:54:07 DEBUG : 6 go routines active

16

i think you need to start over, re-read my comments, create new remotes.

17

afaik (per what I have read on this forum) service accounts are like other google accounts and have different drive than your main drive, but I could be wrong. I have never used that kind of stuff

18

correct.
but i mentioned more than once, your remote has both service account file and client id+secret;
should not do that; use service account file or use client id+secret, not both.

imho, best to start over from scratch, create new remotes.

19

Thank you to the both of you.

I will do as you all have advised and create a new remote.

My questions are:

does doing that delete the contents of the remote (files).

I have two remotes (unencrypted and encrypted) would that be a problem when setting things up.

20

Doing what?

This is how crypt works. There are always two remotes. Let's see what you configure and if there are any issues we will look into it.

21

[quote="kapitainsky, post:20, topic:48036, full:true"]

"Doing what?"

Erasing the remotes. does it erase the contents of the remotes, the files