Rclone proton openpgp erro

Help and Support
1

What is the problem you are having with rclone?

Error in sycing Proton Drive with SMB

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

rclone v1.66.0

  • os/version: debian 12.5 (64 bit)
  • os/kernel: 6.1.0-18-amd64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.22.1
  • go/linking: static
  • go/tags: none

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

Proton Drive

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

    rclone sync mfc_proton: mfc_smb_orion:PROTON-MFC --tpslimit 6 --transfers=3 --checkers=6 --max-duration=48h --cutoff-mode=hard --retries 3 --retries-sleep=10 --timeout=1m --log-level=NOTICE

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

``2024/04/23 11:20:24.407627 WARN RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401), Attempt 1
2024/04/23 11:20:24.408899 ERROR RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401)
2024/04/23 11:20:24.445596 WARN RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422), Attempt 1
2024/04/23 11:20:24.446674 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422)
2024/04/23 11:20:27.673719 WARN RESTY gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type, Attempt 1
2024/04/23 11:20:27.675112 ERROR RESTY gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type
2024/04/23 11:20:27 Failed to create file system for "mfc_proton:": couldn't initialize a new proton drive instance: gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type

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

------------------------------------------------------------------------------------------------
2024/04/23 11:27:04 INFO  : Starting transaction limiter: max 6 transactions/s with burst 1
2024/04/23 11:27:04 DEBUG : rclone: Version "v1.66.0" starting with parameters ["rclone" "sync" "mfc_proton:" "mfc_smb_orion:PROTON-MFC" "--tpslimit" "6" "--transfers=3" "--checkers=6" "--max-duration=48h" "--cutoff-mode=hard" "--retries" "3" "--retries-sleep=10" "--timeout=1m" "-vv"]
2024/04/23 11:27:04 DEBUG : Creating backend with remote "mfc_proton:"
2024/04/23 11:27:04 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2024/04/23 11:27:04 DEBUG : proton drive root link ID '': Has cached credentials
2024/04/23 11:27:04.826967 WARN RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401), Attempt 1
2024/04/23 11:27:04.828488 ERROR RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401)
2024/04/23 11:27:04.867412 WARN RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422), Attempt 1
2024/04/23 11:27:04.868455 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422)
2024/04/23 11:27:04 DEBUG : Saving config "client_uid" in section "mfc_proton" of the config file
2024/04/23 11:27:05 DEBUG : Saving config "client_access_token" in section "mfc_proton" of the config file
2024/04/23 11:27:05 DEBUG : Saving config "client_refresh_token" in section "mfc_proton" of the config file
2024/04/23 11:27:05 DEBUG : Saving config "client_salted_key_pass" in section "mfc_proton" of the config file
2024/04/23 11:27:05 DEBUG : proton drive root link ID '': Cached credential doesn't work, clearing and using the fallback login method
2024/04/23 11:27:05 DEBUG : Saving config "client_uid" in section "mfc_proton" of the config file
2024/04/23 11:27:05 DEBUG : Saving config "client_access_token" in section "mfc_proton" of the config file
2024/04/23 11:27:06 DEBUG : Saving config "client_refresh_token" in section "mfc_proton" of the config file
2024/04/23 11:27:06 DEBUG : Saving config "client_salted_key_pass" in section "mfc_proton" of the config file
2024/04/23 11:27:06 DEBUG : proton drive root link ID '': couldn't initialize a new proton drive instance using cached credentials: failed to refresh auth: failed to refresh auth, de-auth: 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422)
2024/04/23 11:27:06 DEBUG : proton drive root link ID '': Using username and password to log in
2024/04/23 11:27:08.384481 WARN RESTY gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type, Attempt 1
2024/04/23 11:27:08.385926 ERROR RESTY gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type
2024/04/23 11:27:08 Failed to create file system for "mfc_proton:": couldn't initialize a new proton drive instance: gopenpgp: error in reading key ring: openpgp: invalid data: user ID signature with wrong type
2

at this point, many issues with proton support that are not getting fixed.

fwiw, might just start over, re-create mfc_proton from scracth.

can you post that?

3 

[mfc_proton]
type = protondrive
username = mXXXX
password = XXX
client_uid =
client_access_token =
client_refresh_token =
client_salted_key_pass =

[mfc_smb_orion]
type = smb
host = XXX
user = XXX
pass = XXX

[rfc_proton]
type = protondrive
username = riXXXX
password = XXX
client_uid = XXX
client_access_token = XXX
client_refresh_token = XXX
client_salted_key_pass = XXX

[rfc_smb_orion]
type = smb
host = XXX
user = XXX
pass = XXX
### Double check the config for sensitive info before posting publicly

I recreated the end point a few times even other machines, no luck though...