Crypt remotes - why is `myremote:` not recommended?

What is the problem you are having with rclone?

Confused with crypts

The config wizard says:

Remote to encrypt/decrypt.
Normally should contain a ':' and a path, eg "myremote:path/to/dir",
"myremote:bucket" or maybe "myremote:" (not recommended).
Enter a string value. Press Enter for the default ("").

Why is myremote: not recommended?

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

rclone v1.64.2
- os/version: slackware 14.2+ (64 bit)
- os/kernel: 5.10.28-Unraid (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.21.3
- go/linking: static
- go/tags: none

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


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

rclone config

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

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

root filesystem be it local or remote often contains objects (files/folders/links) specific to given OS or cloud provider. For example Thrash Folder, "virtual" folders pointing to other filesystems or shared folders etc.

It means that potentially you mix encrypted content created by rclone with not encrypted content created by OS/cloud provider. Results can be unpredictable.

This is why it is logical and good practice to store all rclone encrypted content in dedicated place, e.g.: "myremote:path/to/my_encrypted_data".

1 Like

But surely the root of the remote doesn't necessarily point to the root of a filesystem? Especially when it's a crypt.

Depends how you configure it. "myremote:" - not recommended is general advice.

If let's say it is linux mounted drive and your crypt points to /mnt/ext_drive then it is fine - still depends on your external disk file system and OS, some like to store some hidden data.

But would be potential problem on Windows when you point it to D: drive.

Give me an example you want to use to comment further:)

I've mounted a remote server under /mnt/remotes/offsite/

And then I've made aliases such as video: to /mnt/remotes/offsite/video

I then backup to a crypt remote which is addressed to video:

OK - clear. I would do the same without worry as you do not point crypt to top folder of your disk but to its subfolder - /video

1 Like

Might be worth to make it more clear in the documentation. As at the end it is not about remote: but about underlying filesystem. It is not recommended to point crypt to disk root folder or root cloud storage...


I agree -- I remember this confused me when I was new to rclone. What it says is not exactly what it means.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.