Ran out of space, config file disappeared, now I cant access my enc stuff

I had my gdrive mounted using encryption. I ran out of local diskspace and one of my applications crashed so I freed up some space and rebooted. After a reboot my mounted encrypted gdrive was gone. I ran config and it said there were no remotes. It was a pita but I ran rclone config and recreated the encrypted mount. I said yes x 2 to entering my own password the first time so I did the same this time and used the exact same password but my mount is empty, as if I had created a new one. If I mount the unencrypted remote I can see the encrypted data on my gdrive but cannot access it.

Please tell me how I can get at the data again.

If you lost your config file, i’m not sure it would be possible to get the data back decrypted

Really? I only started using rclone a few days ago, Before that I used encfs and was able to remount anywhere as long as I had the password. I tried encfs with rclone mount but I kept getting input/output errors so I switched to crpyt but if I cant recover then I dont think its reliable enough for me.

Let a bit more time to other people to answer you may be i did something wrong on my side but i tried to mount the same folder on different server and even if i used the same password it didn’t work because the passkey generated with the same password change everytime i made a news config file …

If you have the right credentials, then you can absolutely get your data. If you don’t see your data after verifying your ~/.rclone.conf file is correct then you have the wrong passwords/keys.

The thing is he lost the ~/.rclone.conf file so when he ran rclone config it says there’s nothing configured.
If he create a new one even if he use the same password the program create another passkey so his old files won’t be decrypted

Yes. he needs the password hashes.

So just to clarify, if I lose my conf file but I know my passwords (alphanumeric) I should be able to access the rclone crypt mount? I am asking because I definitely had the correct password but it was empty

In my opinion : you can’t because when you will recreate the new conf file even if you use the same password the password hash will be different…

He can. The secrets in the conf are just obscured passwords. If he knows the password and salts he can recreate the config and access his data. I just did that exact test case. Yes the values in the conf are different but that doesn’t matter.

1 Like

It didn’t work for me :confused:

@brimur : Try and tell us .I hope @calisro is right

He is right.

I configured same mount on different servers with just entering the password (without copying config).

If you type your password right, it should be working fine.

1 Like

Just to clarify for you. You can’t type the hashes stored in the config as those are obscured passwords into the ‘rclone config’ wizard. If you already have the obscured passwords from the config file, you can just paste them BACK to the config file. If you know the original passwords you originally entered when creating the config via the rclone config wizard, then run through the config again and retype those. It works…

Yes i clearly understand that. I configured and upload all my library encrypted from server1. I wanted to browse my library from server 2 so i did rclone config . create the remote then the encrypted one, using the same password and Salt things and everything came up empty :confused: if you said it should works i may be done something wrong

Here is a usecase. I used hello and hello1 as my password/salt for both crypts.

$rclone config
2017/04/05 11:03:06 NOTICE: Config file “/var/lib/deluge/.config/rclone/rclone.conf” not found - using defaults
No remotes found - make a new one
n) New remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config

n/r/c/s/q> n
name> local
Type of storage to configure.
Choose a number from below, or type in your own value
1 / Amazon Drive
\ “amazon cloud drive”
2 / Amazon S3 (also Dreamhost, Ceph, Minio)
\ “s3”
3 / Backblaze B2
\ “b2”
4 / Dropbox
\ “dropbox”
5 / Encrypt/Decrypt a remote
\ “crypt”
6 / Google Cloud Storage (this is not Google Drive)
\ “google cloud storage”
7 / Google Drive
\ “drive”
8 / Hubic
\ “hubic”
9 / Local Disk
\ “local”
10 / Microsoft OneDrive
\ “onedrive”
11 / Openstack Swift (Rackspace Cloud Files, Memset Memstore, OVH)
\ “swift”
12 / SSH/SFTP Connection
\ “sftp”
13 / Yandex Disk
\ “yandex”
Storage> 9
Disable UNC (long path names) conversion on Windows
Choose a number from below, or type in your own value
1 / Disables long file names
\ “true”
nounc>
Remote config

[local]
nounc =

y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d> y
Current remotes:
Name Type
==== ====
local local

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q> n

name> crypt1
Type of storage to configure.
Choose a number from below, or type in your own value
1 / Amazon Drive
\ “amazon cloud drive”
2 / Amazon S3 (also Dreamhost, Ceph, Minio)
\ “s3”
3 / Backblaze B2
\ “b2”
4 / Dropbox
\ “dropbox”
5 / Encrypt/Decrypt a remote
\ “crypt”
6 / Google Cloud Storage (this is not Google Drive)
\ “google cloud storage”
7 / Google Drive
\ “drive”
8 / Hubic
\ “hubic”
9 / Local Disk
\ “local”
10 / Microsoft OneDrive
\ “onedrive”
11 / Openstack Swift (Rackspace Cloud Files, Memset Memstore, OVH)
\ “swift”
12 / SSH/SFTP Connection
\ “sftp”
13 / Yandex Disk
\ “yandex”
Storage> 5
Remote to encrypt/decrypt.
Normally should contain a ‘:’ and a path, eg “myremote:path/to/dir”,
“myremote:bucket” or maybe “myremote:” (not recommended).
remote> local:/var/lib/deluge/l
How to encrypt the filenames.
Choose a number from below, or type in your own value
1 / Don’t encrypt the file names. Adds a “.bin” extension only.
\ “off”
2 / Encrypt the filenames see the docs for the details.
\ “standard”
filename_encryption> 2
Password or pass phrase for encryption.
y) Yes type in my own password
g) Generate random password
y/g> y
Enter the password:
password:
Confirm the password:
password:
Password or pass phrase for salt. Optional but recommended.
Should be different to the previous password.
y) Yes type in my own password
g) Generate random password
n) No leave this optional password blank
y/g/n> y
Enter the password:
password:
Confirm the password:
password:
Remote config

[crypt1]
remote = crypt local:/var/lib/deluge/l
filename_encryption = standard
password = *** ENCRYPTED ***
password2 = *** ENCRYPTED ***

y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d> y
Current remotes:

Name Type
==== ====
crypt1 crypt
local local

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q> n
name> crypt2
Type of storage to configure.
Choose a number from below, or type in your own value
1 / Amazon Drive
\ “amazon cloud drive”
2 / Amazon S3 (also Dreamhost, Ceph, Minio)
\ “s3”
3 / Backblaze B2
\ “b2”
4 / Dropbox
\ “dropbox”
5 / Encrypt/Decrypt a remote
\ “crypt”
6 / Google Cloud Storage (this is not Google Drive)
\ “google cloud storage”
7 / Google Drive
\ “drive”
8 / Hubic
\ “hubic”
9 / Local Disk
\ “local”
10 / Microsoft OneDrive
\ “onedrive”
11 / Openstack Swift (Rackspace Cloud Files, Memset Memstore, OVH)
\ “swift”
12 / SSH/SFTP Connection
\ “sftp”
13 / Yandex Disk
\ “yandex”
Storage> 5
Remote to encrypt/decrypt.
Normally should contain a ‘:’ and a path, eg “myremote:path/to/dir”,
“myremote:bucket” or maybe “myremote:” (not recommended).
remote> local:/var/lib/deluge/l
How to encrypt the filenames.
Choose a number from below, or type in your own value
1 / Don’t encrypt the file names. Adds a “.bin” extension only.
\ “off”
2 / Encrypt the filenames see the docs for the details.
\ “standard”
filename_encryption> 2
Password or pass phrase for encryption.
y) Yes type in my own password
g) Generate random password
y/g> y
Enter the password:
password:
Confirm the password:
password:
Password or pass phrase for salt. Optional but recommended.
Should be different to the previous password.
y) Yes type in my own password
g) Generate random password
n) No leave this optional password blank
y/g/n> y
Enter the password:
password:
Confirm the password:
password:
Remote config

[crypt2]
remote = local:/var/lib/deluge/l
filename_encryption = standard
password = *** ENCRYPTED ***
password2 = *** ENCRYPTED ***

y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d> y
Current remotes:

Name Type
==== ====
crypt1 crypt
crypt2 crypt
local local

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q> q
$echo hi > somefile
$rclone cp somefile crypt1:
$rclone copy somefile crypt1:
$rclone cat crypt1:somefile
hi
$rclone cat crypt2:somefile
hi
$cat .config/rclone/rclone.conf
[local]
type = local
nounc =

[crypt1]
type = crypt
remote = local:/var/lib/deluge/l
filename_encryption = standard
password = pMhVY8yslTbG21WDD4uK37igwAlR
password2 = SmMSJAqOhM0D_5ivFXRZi4sQuoy26A

[crypt2]
type = crypt
remote = local:/var/lib/deluge/l
filename_encryption = standard
password = ooqn02DUt10LpKGPYrHbDqTa5HJM
password2 = VN_D8wFuixhMi–N5NZsnT6Cky-gcA

$ls -l /var/lib/deluge/l
total 8
-rw-rw-r-- 1 deluge mediashare 51 Apr 5 11:07 076tp4ct1ll3jd04ngm35j2fmg
drwxrwxr-x 3 deluge mediashare 4096 Apr 5 07:08 hp7ltam9g1g64idlpd0bjoo8es

You said ‘password’ but there is a password and a salt. In essence two passwords.

I have issues too.

I made a HUBIC crypt and used the same pw+salt on two devices and it works.
Tried to do the same with ACD and it doesn’t work.
rclone ls enrcyptedACD: gives me the encrypted filenames.
rclone ls encryptedHubic: gives the decrypted filenames on both devices.
I checked and rechecked and the configuration is the same and typed the passwords one letter at a time, just to be sure that I didn’t mistype.
I even tried to delete the crypt on the PC it worked the first time, used the same pw+salt and it worked.

pw lenght is 10 chars; salt lenght is 14chars for acd.

l.e. problem was between the keyboard and seat.
I did rclone ls acd_path_to_enc_folder and not rclone ls enrcyptedACD…

I will suggest Long Path Tool program. Try using it. It really works.