2fa for proton drive keeps failing

Help and Support
1

What is the problem you are having with rclone?

I am trying to create and use a remote on proton drive with an account that uses 2FA. I have been successful in configuring a proton drive remote without 2FA, but the higher security version quits with a missing signature error. I have tried entering a 6-digit code from an authenticator and a recovery code from Proton for the particular account. Neither works.

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

rclone v1.71.0
- os/version: fedora 41 (64 bit)
- os/kernel: 6.16.11-100.fc41.x86_64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.24.6
- go/linking: dynamic
- 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 -vv lsd proton_drive:

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

[proton_drive]
type = protondrive
username = XXXXXXXX@proton.me
password = XXX
2fa = XXXXXX [recovery code]
client_uid = XXX
client_access_token = XXX
client_refresh_token = XXX
client_salted_key_pass = XXX

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

2025/10/24 11:47:53 DEBUG : rclone: Version "v1.71.0" starting with parameters ["rclone" "-vv" "lsd" "proton_drive:"]
2025/10/24 11:47:53 DEBUG : Creating backend with remote "proton_drive:"
Enter configuration password:
password:
2025/10/24 11:48:04 DEBUG : Using config file from "/home/xxxxx/.config/rclone/rclone.conf"
2025/10/24 11:48:04 DEBUG : proton drive root link ID '': Has cached credentials
2025/10/24 11:48:08 DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
2025/10/24 11:48:14 ERROR : error listing: Signature Verification Error: Missing signature
2025/10/24 11:48:14 DEBUG : 5 go routines active
2025/10/24 11:48:14 NOTICE: Failed to lsd with 2 errors: last error was: Signature Verification Error: Missing signature
2

Search the forum, the proton remotes are not working. And most likely, will be labeled as depractad or abandoned.

Proton absolutely refuses to support rclone.

Your question has been asked many times, can search the forum...

3

Yes, I saw some posts about similar but not identical errors and was wondering whether I was doing something different. I know about proton’s intransigence.

Still, the non-2FA drives seem to work fine.

4

the proton remotes are not working.

From my own experience and what I read elsewhere, Proton remotes are working generally fine, including those with 2FA. People may tend to come here primarily in case they need help rather than to say everything is working fine :slight_smile:

@roamingbhole Have you gone into rclone config to edit your remote and enter a new 2FA code (actual one, not a backup)? You may need to run a command quite quickly after to make sure Proton picks up the 2FA code on time. 2FA tends to “expire” once every blue moon, and entering a new one quickly followed by rclone lsd fixes it until the next time it “expires”.

Also, have you tried running the command without an rclone config password?