Reinstall - New gdrive - gcd token just won't work

[datao]

I get this message when I try to add ‘My Drive’ google drive. This is a google workspace account.

Failed to retrieve the id of the root: googleapi: Error 404: File not found:

I am only using the Directory tab, not Shared Drive.

I tried re-generating the gcd token many times, it just doesn’t work.

I tried generating a token from another Google Workspace org and I get the same message.

Just for more info, this is the message I receive if I just want the Shared Drives listed:

Failed to list the shared drives: googleapi: Error 403: Request had insufficient authentication scopes. Details: [ { "@type": "type.googleapis.com/google.rpc.ErrorInfo", "domain": "googleapis.com", "metadata": { "method": "google.apps.drive.v3.DriveDrives.List", "service": "drive.googleapis.com" }, "reason": "ACCESS_TOKEN_SCOPE_INSUFFICIENT" } ] More details: Reason: insufficientPermissions, Message: Insufficient Permission

I am on the latest version, I am trying to setup the gdrive storage through the web gui.

[sarcasm.tarot91]

I’m running into the same issue.

I have a personal google account.
the token suddenly stopped working, and delete duplicacy and reauth instead resulted in the insufficient scope issue.

Wonder if something introduced a breaking change.

[saspus]

This could be related

This app is blocked

It appears that Google Drive stopped giving out the full access scope https://www.googleapis.com/auth/drive. I modified Google Drive for Duplicacy to use the more restricted https://www.googleapis.com/auth/drive.file scope instead, which means Duplicacy can only access files and directories that it creates. As a result, you can no longer click the browse button to list directories in your Google Drive account. You’ll have to manually enter the directory name.

[gchen]

Right. It looks like Google Drive just revoked all tokens previously issued with the full access scope.

You can work around the issue with the following steps:

1. Obtain a new, app-scoped token from Google Drive for Duplicacy. This new token can only be used to access files created by Duplicacy
2. Create a new temporary Google Drive storage in Duplicacy. When selecting the storage directory, don’t click the directory browsing button. Instead, just enter the old storage directory name in the input box. Google Drive will create a new directory with the same name, but this one can be accessed by the new app-scoped token
3. The storage should be created with the same password if the previous storage was encrypted
4. In Google Drive, remove the config file under the storage directory, and then copy over chunks, snapshots, and config from the old storage directory
5. Remove the old Google Drive storage in Duplicacy and create a new one with the same storage name using the new app-scoped token
6. All backup and schedule jobs should now work as before

[sarcasm.tarot91]

I’ve deleted my previous gDrive “Storage”

But I don’t remember if I have changed the following fields:

Is there any place I can look it up?

Thanks

[sarcasm.tarot91]

2. I used the same storage directory (My Drive/Backup/Duplicacy)

No new “Duplicacy” folder was created. The app instead “found” the existing folder. Performing a check shows 0 backup and 0 versions.

2. If I instead use a new directory: (My Drive/Backup/Duplicacy_v2)

The storage will be created successfully in duplicacy webapp, but no Duplicacy_v2 is created at the place.

[gchen]

Can you try using My Drive/Duplicacy as the new directory? I did not test the case where the storage directory is under another directory.

[datao]

Hello gchen,

This worked for me. I just started a fresh backup anyways, so step 1-2 was enough for me.

[sarcasm.tarot91]

yes this worked.

backup recovered, thanks!

[danieldpt]

Meny thanks for this!

I think (Hope) i did it the right way.

My “prune” job is taking very long. Is that normal? I have about 1,3 TB on my google drive.

Okay it did finish but i still get

Running check command from /cache/localhost/all
Options: [-log check -storage dbhansdude -a -tabular]
2024-10-13 12:01:02.427 INFO STORAGE_SET Storage set to gcd://Duplicacy
2024-10-13 12:01:05.939 INFO SNAPSHOT_CHECK Listing all chunks
2024-10-13 12:02:37.955 ERROR LIST_FILES Failed to list the directory chunks/: googleapi: Error 400: Invalid Value, invalid
Failed to list the directory chunks/: googleapi: Error 400: Invalid Value, invalid

EDIT. Just tryed to delete the old “Duplicacy” trust in my google drive and make a new token.
But im still getting error with the “Check”

@gchen any good ideas?

Regards Daniel

[kelvin]

Just sharing my thanks. My weekly backups only failed this week and I was completely unaware of the token changes by google. The solution/fix in this thread worked first time, thank you

[Qinnit]

Thank you from me as well. For some reason it didn’t work the first time, but the second time I followed these instructions my Google Drive storage got up and running again.
Glad to be ditching Google Drive soon, when my current plan ends. Too much nonsense like this.