Encryption Remote Gone, What To Do Now?

What is the problem you are having with rclone?

I had made a remote with Rclone for my Google Disk account and all files on it, i then made a Encrypt Remote to encrypt all files in my Google Disk (with folders).

However the Virtual Machine with the Rclone where the Google (Disk) remote was and the Encrypted (Crypt) remote was, got corrupted and I had to delete it.

As expected the files on my Google Disk didn't get decrypted just because the original Rclone was gone, but how can I decrypt the files and download them? or decrypt them locally with a new Rclone installation?

I tried to download Rclone and make the same Remotes again (Google and Crypt), but even thought the Google remote could find the files (encrypted) the Crypt remote didn't find any files when I did the "rclone ls Crypt:" command and couldn't decrypt them to my device like the original Rclone could.

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

- os/version: Microsoft Windows 10 Pro 20H2 (64 bit)
- os/kernel: 10.0.19042.1706 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.17.9
- go/linking: dynamic
- go/tags: cmount

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

Google Disk

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

rclone ls Crypt:

The rclone config contents with secrets removed.

[Google]
type = drive
scope = drive
token = {"access_token":"REDACTED"}
team_drive = 

[Crypt]
type = crypt
remote = Google:
password = REDACTED

A log from the command with the -vv flag

Sorry, could not figure out how to find a log from the cmd or know what a "-vv flag" is

Run the command above with -vv on the end so

rclone ls Crypt: -vv

You'd have to use the same config you used previously so the same encryption and same passwords on the crypt remote.

Alright, thankfully the Google Drive and VM was newly made for me to test Rclone. However if I decide to use Rclone to sync and encrypt my files and folders I should copy the original Config file with passwords and ID Tokens from the then remotes somewhere safely incase I ever need to make a new Rclone on a new Device?

Btw. Root Folder ID is not sensitive information is it? Because I just did the CMD with the "-vv" and it includes the Root Folder ID.

Up to you. I don't think it is, but perhaps others might think it is.

That's the easiest or you can document it somewhere as well.

1 Like

So what should be backed up is the Account ID and Auto-Generated Password?

I'm not sure what you mean by that. I'm saying backup the rclone.conf in whole and/or copy all the contents somewhere else.

1 Like

Saving the config elsewhere is good. If you know the passwords and how it was set up, you can recreate a crypt.

The rclone config is just text so it is easily backed up in a password manager for example

I fully agree with you Nick.
For an example: a self hosted bitwarden server. Requiring a root password upon boot of the service, along with a master password upon trying to view / copy the 'key' for the specific remote flag field.

Also if I sync one folder, but the only change in the folder is 1 new file. Rclone will not try to upload the entire folder again? It will then notice the only difference is the new file and only upload that and leave the rest untouched?

Because I am now syncing a folder of 1TB data, but I'm seeing some files getting Errors while trying to Upload it to my chosen Cloud Service.

If I Sync the folder again when its done with the original Syncing, will Rclone try to upload the files to replace the already existing files again? Or will Rclone be smart enough to see that the files are the same and only upload the files that aren't already uploaded?

hi,

yes, rclone is smart enough.
as per the docs

and as per the docs
"Since this can cause data loss, test first with the --dry-run"

Yep, found out as tested it on my VM. However, i'll try the Dry-Run to see what that does.

Ah, nice. It shows what will be transfered and deleted if I sync the folder from Local -> Cloud.

Nice way to test, thanks for the tip.

I have another question, but I should probably close this Topic and make a new one for that.

what is the question?

My question is, with Jottacloud do I always need the Login Token (which gets refreshed each hour) every time when I want to sync/copy to my Jottacloud account?

you are right, start a new topic.

and no need to close this topic, as it will close on its own after one month.