Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rclone - crypt support? #10

Open
DarkVader-cell opened this issue Feb 4, 2022 · 7 comments
Open

rclone - crypt support? #10

DarkVader-cell opened this issue Feb 4, 2022 · 7 comments

Comments

@DarkVader-cell
Copy link

Hey, I have deployed this and torrents download fine, but I would like the download location to be an encrypted drive (crypt) from my config and I have set it as my first drive there to reflect the same.

But, none of the downloads are being reflecting in my team drive, am I doing something wrong or are crypt remotes not supported yet?

@developeranaz
Copy link
Owner

oh thats a problem.
i'll fix it as soon as possible.

@developeranaz
Copy link
Owner

I assume rclone crypt is similar to rclone union, for now rename your cloud/remote name in a manner below.

[1] 
type = union
remotes = 2: 3: 4:

[2] 
type = drive
root_folder_id = xxcc
scope = drive
token = xxcc

[3] 
type = pcloud
hostname = api.pcloud.com
token = 

[4]
type = mega
user = [email protected]
pass = xxxxxxxx

Use your main/ desired remote name for upload to [1] (to list it first)

@developeranaz
Copy link
Owner

I assume rclone crypt is similar to rclone union, for now rename your cloud/remote name in a manner below.
[1]
type = union
remotes = 2: 3: 4:
[2]
type = drive
root_folder_id = xxcc
scope = drive
token = xxcc
[3]
type = pcloud
hostname = api.pcloud.com
token =
[4]
type = mega
user = [email protected]
pass = xxxxxxxx
Use your main/ desired remote name for upload to [1] (to list it first)

so are you saying that keep my [1] remote one as crypt drive and keep [2] remote 2 as the normal gdirve that might fix the error ??? I tried this configuration keeping encrypted drive 1st still it uploads the the the unencrypted 2nd remote that is drive 1 doesn't work but their is a fix i got it working [driveencrypt] type = crypt remote = drive1: password = ILUFIKVikfvsajufvbskli-dsgdsgsdgds-gdsg-sdgg-dsg-sdg-dsgds password2 = ILUFIKVikfvsajufvbskli-dsgdsgsdgds-gdsg-sdgg-dsg-sdg-dsgds

[drive1] type = drive client_id = client_secret = scope = drive token = {"access_token":"lol"} root_folder_id =

the solution is tools>options scroll allthe way down and you will see this line rclone copy /qBittorrent/downloads/"%N" drive1:qbit/"%N" just edit this to rclone copy /qBittorrent/downloads/"%N" driveencrypt:qbit/"%N" image i did this and it worked

you can do that but you need to change it every 23 hours or next heroku restart

@developeranaz
Copy link
Owner

Use below similar rclone config to change it permanently

[000000001a]
type = crypt
remote = drive1:
password = ILUFIKVikfvsajufvbskli-dsgdsgsdgds-gdsg-sdgg-dsg-sdg-dsgds
password2 = ILUFIKVikfvsajufvbskli-dsgdsgsdgds-gdsg-sdgg-dsg-sdg-dsgds

[drive1]
type = drive
client_id =
client_secret =
scope = drive
token = {"access_token":"lol"}
root_folder_id =

according to rclone remote listing , remotes starting with 0 will list first and files will be uploaded to it

@bolavefasfas
Copy link

bolavefasfas commented Mar 22, 2022

Use below similar rclone config to change it permanently

[000000001a]
type = crypt
remote = drive1:
password = ILUFIKVikfvsajufvbskli-dsgdsgsdgds-gdsg-sdgg-dsg-sdg-dsgds
password2 = ILUFIKVikfvsajufvbskli-dsgdsgsdgds-gdsg-sdgg-dsg-sdg-dsgds

[drive1]
type = drive
client_id =
client_secret =
scope = drive
token = {"access_token":"lol"}
root_folder_id =

according to rclone remote listing , remotes starting with 0 will list first and files will be uploaded to it

ohh thats great so any remote starting with a 0 will be considered as default remote 👍 was this pushed in update ??

@developeranaz
Copy link
Owner

No, the webapp was already designed in that manner, but i didn't provided it in readme.

@bolavefasfas
Copy link

No, the webapp was already designed in that manner, but i didn't provided it in readme.

All right

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants