Impossible to access my Proton Drive remote: object not found

Suspected Bug
1

What is the problem you are having with rclone?

Although it looks like I can connect to my ProtonDrive remote and the credentials are accepted, I cannot access its content.

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

$ rclone version     
rclone v1.64.2
- os/version: debian kali-rolling (64 bit)
- os/kernel: 6.5.0-kali3-amd64 (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)

ProtonDrive

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

rclone ls proton:

The rclone config contents with secrets removed.

[proton]
type = protondrive
username = fred.gib
password = XXX
2fa = 954370
client_uid = XXX
client_access_token = XXX
client_refresh_token = XXX
client_salted_key_pass = XXX

A log from the command with the -vv flag

$ rclone ls proton: -vv                                     
<7>DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "ls" "proton:" "-vv"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "proton:"
<7>DEBUG : Using config file from "/home/fred/.config/rclone/rclone.conf"
<7>DEBUG : proton drive root link ID '': Has cached credentials
<7>DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
<3>ERROR : : error listing: object not found
<7>DEBUG : 5 go routines active
Failed to ls with 2 errors: last error was: object not found
2 
rclone ls proton01: -vv
2023/11/07 09:22:30 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "ls" "proton01:" "-vv"]
2023/11/07 09:22:30 DEBUG : Creating backend with remote "proton01:"
2023/11/07 09:22:30 DEBUG : Using config file from "c:\\data\\rclone\\rclone.conf"
2023/11/07 09:22:30 DEBUG : proton drive root link ID '': Has cached credentials
2023/11/07 09:22:33 DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
       17 file.ext

did proton: work in the past and just now failed, or is this the first time using it?
i would create a new remote from scratch.

3

Thanks for the quick advice. It's the first time and I never got it to work yet; and I already deleted and recreated it.

4 
rclone config redacted proton01:
[proton01]
type = protondrive
username = XXX
password = XXX
2fa = XXX
client_uid = XXX
client_access_token = XXX
client_refresh_token = XXX
client_salted_key_pass = XXX

perhaps try a few test.

try to copy a file to root and list it.

rclone copy ~/file.ext proton: -vv
rclone ls proton: -vv

create a subdir and copy a file to it

rclone mkdir proton:folder -vv
rclone ls proton:folder -vv
5

Thanks again!

Uploading a file works (and I could check online that the file was there)

$ rclone copy ~/temp/file.ext Proton: -vv
<7>DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "copy" "/home/fred/temp/file.ext" "Proton:" "-vv"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "/home/fred/temp/file.ext"
<7>DEBUG : Using config file from "/home/fred/.config/rclone/rclone.conf"
<7>DEBUG : fs cache: adding new entry for parent of "/home/fred/temp/file.ext", "/home/fred/temp"
<7>DEBUG : Creating backend with remote "Proton:"
<7>DEBUG : proton drive root link ID '': Has cached credentials
<7>DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
<7>DEBUG : file.ext: Need to transfer - File not found at Destination
<7>DEBUG : file.ext: sha1 = 4eb5f318a048763f4e2c625ccc5111947584e2b1 OK
<6>INFO  : file.ext: Copied (new)
<6>INFO  : 
Transferred:              5 B / 5 B, 100%, 2 B/s, ETA 0s
Transferred:            1 / 1, 100%
Elapsed time:         5.6s

<7>DEBUG : 8 go routines active

However, right after that:

$ rclone ls Proton: -vv                  
<7>DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "ls" "Proton:" "-vv"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "Proton:"
<7>DEBUG : Using config file from "/home/fred/.config/rclone/rclone.conf"
<7>DEBUG : proton drive root link ID '': Has cached credentials
<7>DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
<3>ERROR : : error listing: object not found
<7>DEBUG : 5 go routines active
Failed to ls with 2 errors: last error was: object not found

Same with folder creation, which I can create but not list, whether I then use ls or lsd

Note: the remote is now Proton, as I tried to delete and create the remote yet a second time, with a different name.

6

if you do not post the debug out, we cannot be sure what you are doing?

rclone mkdir proton01:zork -vv
2023/11/07 09:42:06 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "mkdir" "proton01:zork" "-vv"]
2023/11/07 09:42:06 DEBUG : Creating backend with remote "proton01:zork"
2023/11/07 09:42:06 DEBUG : Using config file from "c:\\data\\rclone\\rclone.conf"
2023/11/07 09:42:06 DEBUG : proton drive root link ID 'zork': Has cached credentials
2023/11/07 09:42:07 DEBUG : proton drive root link ID 'zork': Used cached credential to initialize the ProtonDrive API
2023/11/07 09:42:08 DEBUG : proton drive root link ID 'zork': Making directory
2023/11/07 09:42:09 DEBUG : 3 go routines active

c:\data\rclone>rclone ls proton01:zork -vv
2023/11/07 09:42:14 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "ls" "proton01:zork" "-vv"]
2023/11/07 09:42:14 DEBUG : Creating backend with remote "proton01:zork"
2023/11/07 09:42:14 DEBUG : Using config file from "c:\\data\\rclone\\rclone.conf"
2023/11/07 09:42:14 DEBUG : proton drive root link ID 'zork': Has cached credentials
2023/11/07 09:42:15 DEBUG : proton drive root link ID 'zork': Used cached credential to initialize the ProtonDrive API
2023/11/07 09:42:17 DEBUG : 3 go routines active

c:\data\rclone>rclone lsd proton01:zork -vv
2023/11/07 09:42:19 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "lsd" "proton01:zork" "-vv"]
2023/11/07 09:42:19 DEBUG : Creating backend with remote "proton01:zork"
2023/11/07 09:42:19 DEBUG : Using config file from "c:\\data\\rclone\\rclone.conf"
2023/11/07 09:42:19 DEBUG : proton drive root link ID 'zork': Has cached credentials
2023/11/07 09:42:21 DEBUG : proton drive root link ID 'zork': Used cached credential to initialize the ProtonDrive API
2023/11/07 09:42:24 DEBUG : 3 go routines active
7

Here it is for the folder creation...

$ rclone mkdir Proton:test-folder -vv
<7>DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "mkdir" "Proton:test-folder" "-vv"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "Proton:test-folder"
<7>DEBUG : Using config file from "/home/fred/.config/rclone/rclone.conf"
<7>DEBUG : proton drive root link ID 'test-folder': Has cached credentials
<7>DEBUG : proton drive root link ID 'test-folder': Used cached credential to initialize the ProtonDrive API
<7>DEBUG : proton drive root link ID 'test-folder': Making directory
<7>DEBUG : 5 go routines active

Folder is visible online. But...

$ rclone ls Proton: -vv              
<7>DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "ls" "Proton:" "-vv"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "Proton:"
<7>DEBUG : Using config file from "/home/fred/.config/rclone/rclone.conf"
<7>DEBUG : proton drive root link ID '': Has cached credentials
<7>DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
<3>ERROR : : error listing: object not found
<7>DEBUG : 5 go routines active
Failed to ls with 2 errors: last error was: object not found

$ rclone lsd Proton: -vv
<7>DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "lsd" "Proton:" "-vv"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "Proton:"
<7>DEBUG : Using config file from "/home/fred/.config/rclone/rclone.conf"
<7>DEBUG : proton drive root link ID '': Has cached credentials
<7>DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
<3>ERROR : : error listing: object not found
<7>DEBUG : 5 go routines active
Failed to lsd with 2 errors: last error was: object not found
8

Could it be because I have a visionary account, with several users, a custom domain name and a so-called "organisation encryption key"?

9

please try to mimic the same exact tests as i did, using subdir only, not root.

10

no idea, research the upstream third-party library, see if it supports those features.

maybe another forum member as a visionary account and can comment.

11

Indeed, I can list files that I updated in the folder i have earlier created. But I cannot list the content of the root. Wonder whether it's a limitation on Proton's side, a bug on either side or a security measure on Proton's side

12

imho, neither, as i already posted an example of listing root and it work...

rclone ls proton01: -vv
2023/11/07 09:22:30 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "ls" "proton01:" "-vv"]
2023/11/07 09:22:30 DEBUG : Creating backend with remote "proton01:"
2023/11/07 09:22:30 DEBUG : Using config file from "c:\\data\\rclone\\rclone.conf"
2023/11/07 09:22:30 DEBUG : proton drive root link ID '': Has cached credentials
2023/11/07 09:22:33 DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
       17 file.ext
13

It is still beta.

As per docs:

NB This backend is currently in Beta. It is believed to be correct and all the integration tests pass. However the Proton Drive protocol has evolved over time there may be accounts it is not compatible with. Please post on the rclone forum if you find an incompatibility.

I think the proton remote maintainer might be the best person to answer this one.

@henrybear327 - would you mind to have a look?

1 Like
14

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