Failed to cryptdecode: The remote needs to be of type "crypt"

Hi, an odd problem ...

I am running two instances of rclone: local/Windows and remote/Ubuntu. Identical keys, passwords, etc. Even tried simple passwords like 12345 to be 100% certain that the two installs match.

crypt as follows:

H:\rclone>rclone lsd share:/encrypt
-1 2019-07-08 21:02:47 -1 am1iv0eehtrf2gatvootu4hics
-1 2019-07-08 21:05:04 -1 ruhjqefvp2jep89eti73sge9us

But for some reason, when I try and access the files uploaded from the Ubuntu server, I am unable to decrypt them. This is the error:

rclone cryptdecode share:/encrypt am1iv0eehtrf2gatvootu4hics
2019/07/08 21:09:35 Failed to cryptdecode: The remote needs to be of type "crypt"

Any idea what I might be doing wrong?

I'd guess the rclone.conf is wrorng on the remote that is having the issue.

If you can share it with the keys/passwords removed, we can check it out.

Thank you. I copied and pasted from the original rclone.conf and also created the drives manually - same problem. Setup as follows:

[share]
type = drive
client_id = X
client_secret = X
scope = drive
token = X
team_drive = X

[scrypt]
type = crypt
remote = share:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = X
password2 = X

[scache]
type = cache
remote = share:
chunk_size = 512M
info_age = 1d
chunk_total_size = 50G

share: isn't a crypt remote so that's what it is telling you.

rclone lsd scrypt:

Aaaah, of course! That works, but also reveals another problem:

H:\rclone>rclone lsd scrypt:
-1 2019-07-08 21:02:47 -1 1
-1 2019-07-08 21:05:04 -1 2
-1 2019-07-08 21:20:56 -1 3
-1 2019-07-08 21:21:27 -1 4

But the actual content of the drive is as follows:
Annotation%202019-07-08%20123858

In other words, files I create locally are visible - the four directories named 1,2,3,4 above (shown as encrypted).

But the file created remotely is not - 'fg8pv28qgcqgrdlcbl107opho0':

Annotation%202019-07-08%20213906

It all depends on if you copied to the encrypted remote or not. You can put non encrypted files in there, which is what I guess you may have done. If you see those, they are encrypted files.

Absolutely, but if the two rclone.conf files (local, remote) are identical, how could the files uploaded locally be visible, but those uploaded remotely appear non-existent?

The rclone.conf posted above is from the local machine.

This is the remote rclone.conf, from /root/.config/rclone/rclone.conf:

type = drive
client_id = X
client_secret = X
scope = drive
token = X

[scrypt]
type = crypt
remote = share:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = X
password2 = X

[scache]
type = cache
remote = share:
chunk_size = 512M
info_age = 1d
chunk_total_size = 50G

Because you uploaded something to a wrong remote.

I uploaded to 'scrypt' - locally and remotely. You can see the four folders (locally uploaded) and the single file (remotely uploaded), so they are going to the same remote ....

Both rclone clients are also using the same Client ID and Secret from the same account - with 'Password1' set as 12345 and 'Password2' set as 54321.

That being the case, this makes no sense ... :slight_smile:

Any other ideas?

I mean, your config if off somewhere as if they were the same it works. Without seeing the passwords and such, it's hard to tell.

run a rclone ls on a file with -vv and share the output if it's not working.

I agree with you 100% - just to be sure here are both:

Annotation%202019-07-08%20215436

Fine on Windows, so I guess Ubuntu is using a rogue rclone.conf ... would that explain it?

EDIT: just noticed that Ubuntu can't see the remotely-uploaded file 'fg8pv28qgcqgrdlcbl107opho0': either ...

Annotation%202019-07-08%20215820

Is there a way to search the entire remote for any other rclone.conf files?

Run it with -vv

Windows one reports back fine, but this is the Ubuntu one:

That would be the one with the bad password/salt.

Weird. I have pasted from the local rclone.conf and manually typed the passwords .... neither works.

The passwords and the salt have to all be the same.

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