2021/08/20 19:39:36 DEBUG : rclone: Version "v1.56.0" starting with parameters ["rclone" "-vv" "ls" "secret:archive"]
2021/08/20 19:39:36 DEBUG : Creating backend with remote "secret:archive"
2021/08/20 19:39:36 DEBUG : Using config file from "/Users/user/.rclone.conf"
2021/08/20 19:39:36 DEBUG : Creating backend with remote "remote:serverbackup/[redacted]"
2021/08/20 19:39:36 DEBUG : remote: Loaded invalid token from config file - ignoring
2021/08/20 19:39:37 DEBUG : remote: Token refresh failed try 1/5: oauth2: cannot fetch token: 400 Bad Request
Response: {
"error": "invalid_grant",
"error_description": "Token has been expired or revoked."
Is it possible that this is a temporary user ban?
I have no idea how to troubleshoot this. I can see in the GDrive web interface that the data is still there but I can't interact with it: can't "ls" and can't mount.
I've been using this gdrive and mounting rclone for 6 years and this is the first time this has happened.
When I do that and enter the URL in the browser, I get this:
Authorization Error
Error 400: admin_policy_enforced
Access to your account data is restricted by policies within your organization. Please contact the administrator for [redacted] for more information.
I fear the worst here. I can't imagine how I'd be able to justify to my organization's administrator the need to have a server accessing my Google Drive storing my Plex content.
Is there any way to access any of this encrypted data to move it somewhere else, perhaps in its encrypted state in order to decrypt it from a new location?
If, for example, I opened a new (paid) GD account...
I can still access it through the browser. All the content for the relevant folder, including the filenames, is encrypted, so it'd be quite laborious even figuring out which folders are the essential ones.
I wonder if I'd dare try to cajole an administrator (it's an educational account) that I need rclone to be able to access my GD. I think that that would be mission impossible. There'd be questions about the 39TB of files.
I suspect that it wasn't that anyone personally revoked API access for me. Rather, I would imagine they introduced a new policy regarding "scopes" (I have no idea what these are, but could guess) and it blocked anything that ran afoul of that policy.
Is it sure that changing the "Publishing Status" from "In Production" to "Testing" wouldn't do anything?
There is in the Google Account management page a big old button for transferring content to another Google Account. I think that might be my best bet: set up an unlimited enterprise account ($$$) and transfer the data there.
@Animosity022,
since the OP can access the folder using the browser.
is there a way to get the folder id, use it as root_folder_id and use rclone's client_id to create a remote?
Thanks. Is it also possible to point rclone to local files (if, say, I were to download them to a server) and decrypt them. I realise this may be a stupid question but I've only ever used rclone to transfer and decrypt files hosted remotely.
I don't suppose there's some other GDrive client or any other utility for a Linux server that would allow me to transfer the encrypted files to my server? I gather (in my limited knowledge of such things) that some third-party apps can access my files. These continue to work. Only my rclone "app" has been removed from API access.
What would be involved (obviously at developer level) in giving rclone the kind of access to GDrive that other apps have? For example, Arq Backup can write and read from my Google Drive and continues to be able to do so.
Is there any other workaround that might give me back access to my GDrive share? Would the "verification" process work?
Forgive me if this is a naive or confused question. Although I've been running a server for quite a while, I'm really just a hobbyist.
Also: is there any way to determine the size of GDrive folders? DaisyDisk (mac app) will do this in theory, but seems to choke every time (times out), no doubt because of the number of files or size of the storage in GDrive.
I've now been able to install gdrive on my headless server (the one on which I used to mount my GD share using rclone).
Here's what I don't understand (and this isn't a complaint; I'm just hoping to learn): the unofficial gdrive app for linux has this in its README.md:
gdrive is finally verified for using sensitive scopes which should fix the This app is blocked error. Note that the project name will show up as project-367116221053 when granting access to you account. (I don't dare to change any more settings in the google console.)
rclone no longer works with my GD share precisely because of those 'sensitive scopes' which has led my gdrive administrators to require 'verification' of the app.
Question: can rclone not be 'verified' in this way in the way that, say, the ftp clients on my mac are verified to interact with Gdrive?
gdrive can apparently access my entire Google Drive from my linux server. I haven't tested it, but I assume it will be able to transfer (or mount?) the encrypted folder I used for my rclone share. Why is rclone blocked but not gdrive?