Protond Drive 2fa code doesn't work

Help and Support
1

What is the problem you are having with rclone?

I am trying to set up a Proton Drive remote that can be automatically backed up to with cron. RClone asks for 2fa codes when interacting with proton drive, which would be fine if my 2fa codes didn't reset every minute or so. I don't understand how this works, could someone please explain how I can set and forget this remote?

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

rclone v1.67.0
- os/version: fedora 40 (64 bit)
- os/kernel: 6.10.3-200.fc40.x86_64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.4
- 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 --exclude '/vesktop/sessionData' /home/Charlie/.config protondrive:/Configs

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

[protondrive]
type = protondrive
username = charlie.france
password = XXX
2fa = 597967
client_uid = 
client_access_token = 
client_refresh_token = 
client_salted_key_pass =

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

2024/08/15 00:02:37 DEBUG : rclone: Version "v1.67.0" starting with parameters ["rclone" "sync" "--exclude" "/vesktop/sessionData" "/home/Charlie/.config" "protondrive:/Configs" "-vv"]
2024/08/15 00:02:37 DEBUG : Creating backend with remote "/home/Charlie/.config"
2024/08/15 00:02:37 DEBUG : Using config file from "/home/Charlie/.config/rclone/rclone.conf"
2024/08/15 00:02:37 DEBUG : Creating backend with remote "protondrive:/Configs"
2024/08/15 00:02:37 DEBUG : proton drive root link ID 'Configs': Using username and password to log in
2024/08/15 00:02:40.828874 WARN RESTY 422 POST https://mail.proton.me/api/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422), Attempt 1
2024/08/15 00:02:40.828888 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422)
2024/08/15 00:02:40 Failed to create file system for "protondrive:/Configs": couldn't initialize a new proton drive instance: 422 POST https://mail.proton.me/api/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422)
2

welcome to the forum,

use rclone config to delete the remote

sorry, not understanding?

@henrybear327, you are the author of the proton backend, what do you think?

3

What I mean is this - I use 2fa TOTPs from an authenticator app to sign in to my proton account. The codes regenerate every minute or so, so I don't understand how to permanently authenticate rsync. Thanks

4

afaik, need to do that one time.

[protondrive]
type = protondrive
username = redacted@protonmail.com
2fa = 059869
password = XXX
client_uid = XXX
client_access_token = XXX
client_refresh_token = XXX
client_salted_key_pass = XXX

rclone lsd protondrive: -vv
2024/08/14 20:45:47 DEBUG : rclone: Version "v1.67.0" starting with parameters ["rclone" "lsd" "protondrive:" "-vv"]
2024/08/14 20:45:47 DEBUG : Creating backend with remote "protondrive:"
2024/08/14 20:45:47 DEBUG : Using config file from "C:\\data\\rclone\\rclone.conf"
2024/08/14 20:45:47 DEBUG : proton drive root link ID '': Has cached credentials
2024/08/14 20:45:49 DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
          -1 2023-11-07 09:42:09        -1 zork
5

What are these, and why don't I have them filled? I will try and add the OTP one more time in the mean time.

6

those appear after the remote is created by rclone.

7

But mine are empty?

8

fwiw, i create that remote just a few minutes ago, so i know that rclone is working fine.

ignore that, not relevant to your issue, ok?
those get created only after rclone has contact proton, assuming you supply the correct credentials.

need to use the correct credentials. not sure your username is valid?
take a look at the working remote i posted.

9

I know that it's the 2fa for 2 reasons-

  1. It worked the first time (and now it's working with the code I just gave it) with the same login and 2fa code, but now the 2fa code is outdated
  2. In proton's account manager I can see that rsync gets past the username/password, but fails at 2fa
10

if that were the case, protondrive would fail for every single rclone user after creating it.
forum would be full of topics about that.
imho, so either something just changed on proton side or that is not the actual issue.

post the details

it has been almost 45 minutes since i created that remote and it is still working fine.
and i have another proton remote with 2fa, i created a long time ago. it is also working fine.

on the other hand, whenever i log into https://proton.me, the 2fa code is different each time.
same as with any other website using 2fa

11

https://forum.rclone.org/t/some-characters-seem-not-to-be-handled-in-passwords/42760
https://github.com/rclone/rclone/issues/7864
https://github.com/rclone/rclone/issues/7407

12

Yeah you are right. Very sorry for wasting your time, no idea why it didn't work the other times. It seems to be working now, thanks!

13

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