What is the problem you are having with rclone?
The proton drive remote is not functioning for me. I've tried the stable version of rclone 1.74.0 and the beta version rclone v1.75.0-beta.9822.59c86b01b. In both instances, I have simply created the remote via rclone config, filled in the username, password, 2 factor auth code and the OTP key, and then ran rclone lsd proton: all while the 2fa code that I inputted earlier into the config was still valid.
Run the command 'rclone version' and share the full output of the command.
$ rclone version
rclone v1.75.0-beta.9822.59c86b01b
- os/version: fedora 43 (64 bit)
- os/kernel: 7.0.12-101.fc43.x86_64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.26.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 lsd proton: -vv
$ rclone moveto proton:folder1/folder2 proton:folder1/folder2renamed -vv
Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
$ rclone config redacted
[proton]
type = protondrive
username = XXX
password = XXX
2fa = 266418
otp_secret_key = XXX
client_uid =
client_access_token =
client_refresh_token =
client_salted_key_pass =
### Double check the config for sensitive info before posting publicly
A log from the command that you were trying to run with the -vv flag
$ rclone lsd proton: -vv
2026/06/20 17:29:55 DEBUG : rclone: Version "v1.75.0-beta.9822.59c86b01b" starting with parameters ["rclone" "lsd" "proton:" "-vv"]
2026/06/20 17:29:55 DEBUG : Creating backend with remote "proton:"
2026/06/20 17:29:55 DEBUG : Using config file from "/home/XXX/.config/rclone/rclone.conf"
2026/06/20 17:29:55 DEBUG : proton drive root link ID '': Using username and password to log in
2026/06/20 17:29:58 NOTICE: proton drive root link ID '': 422 POST https://drive-api.proton.me/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422), Attempt 1
2026/06/20 17:29:58 ERROR : proton drive root link ID '': 422 POST https://drive-api.proton.me/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422)
2026/06/20 17:29:58 CRITICAL: Failed to create file system for "proton:": couldn't initialize a new proton drive instance: 422 POST https://drive-api.proton.me/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422)
$ rclone moveto proton:folder1/folder2 proton:folder1/folder2renamed -vv
2026/06/20 17:32:08 DEBUG : rclone: Version "v1.75.0-beta.9822.59c86b01b" starting with parameters ["rclone" "moveto" "proton:folder1/folder2" "proton:folder1/folder2renamed" "-vv"]
2026/06/20 17:32:08 DEBUG : Creating backend with remote "proton:folder1/folder2"
2026/06/20 17:32:08 DEBUG : Using config file from "/home/XXX/.config/rclone/rclone.conf"
2026/06/20 17:32:08 DEBUG : proton drive root link ID 'folder1/folder2': Using username and password to log in
2026/06/20 17:32:10 NOTICE: proton drive root link ID 'folder1/folder2': 401 GET https://drive-api.proton.me/core/v4/users: Invalid access token (Code=401, Status=401), Attempt 1
2026/06/20 17:32:10 ERROR : proton drive root link ID 'folder1/folder2': 401 GET https://drive-api.proton.me/core/v4/users: Invalid access token (Code=401, Status=401)
2026/06/20 17:32:10 DEBUG : Saving config "client_uid" in section "proton" of the config file
2026/06/20 17:32:10 DEBUG : Saving config "client_access_token" in section "proton" of the config file
2026/06/20 17:32:10 DEBUG : Saving config "client_refresh_token" in section "proton" of the config file
2026/06/20 17:32:10 DEBUG : Saving config "client_salted_key_pass" in section "proton" of the config file
2026/06/20 17:32:11 DEBUG : proton drive root link ID 'folder1/folder2': Used username and password to initialize the ProtonDrive API
2026/06/20 17:32:11 DEBUG : Saving config "client_uid" in section "proton" of the config file
2026/06/20 17:32:11 DEBUG : Saving config "client_access_token" in section "proton" of the config file
2026/06/20 17:32:11 DEBUG : Saving config "client_refresh_token" in section "proton" of the config file
2026/06/20 17:32:11 DEBUG : Saving config "client_salted_key_pass" in section "proton" of the config file
2026/06/20 17:32:12 DEBUG : Creating backend with remote "proton:folder1/folder2renamed"
2026/06/20 17:32:12 DEBUG : proton drive root link ID 'folder1/folder2renamed': Has cached credentials
2026/06/20 17:32:12 NOTICE: proton drive root link ID 'folder1/folder2renamed': 401 GET https://drive-api.proton.me/core/v4/users: Invalid access token (Code=401, Status=401), Attempt 1
2026/06/20 17:32:12 ERROR : proton drive root link ID 'folder1/folder2renamed': 401 GET https://drive-api.proton.me/core/v4/users: Invalid access token (Code=401, Status=401)
2026/06/20 17:32:13 NOTICE: proton drive root link ID 'folder1/folder2renamed': 400 POST https://drive-api.proton.me/auth/v4/refresh: Invalid refresh token (Code=10013, Status=400), Attempt 1
2026/06/20 17:32:13 ERROR : proton drive root link ID 'folder1/folder2renamed': 400 POST https://drive-api.proton.me/auth/v4/refresh: Invalid refresh token (Code=10013, Status=400)
2026/06/20 17:32:13 DEBUG : Saving config "client_uid" in section "proton" of the config file
2026/06/20 17:32:13 DEBUG : Saving config "client_access_token" in section "proton" of the config file
2026/06/20 17:32:13 DEBUG : Saving config "client_refresh_token" in section "proton" of the config file
2026/06/20 17:32:13 DEBUG : Saving config "client_salted_key_pass" in section "proton" of the config file
2026/06/20 17:32:13 DEBUG : proton drive root link ID 'folder1/folder2renamed': Cached credential doesn't work, clearing and using the fallback login method
2026/06/20 17:32:13 DEBUG : Saving config "client_uid" in section "proton" of the config file
2026/06/20 17:32:13 DEBUG : Saving config "client_access_token" in section "proton" of the config file
2026/06/20 17:32:13 DEBUG : Saving config "client_refresh_token" in section "proton" of the config file
2026/06/20 17:32:13 DEBUG : Saving config "client_salted_key_pass" in section "proton" of the config file
2026/06/20 17:32:13 DEBUG : proton drive root link ID 'folder1/folder2renamed': couldn't initialize a new proton drive instance using cached credentials: failed to refresh auth: failed to refresh auth, de-auth: 400 POST https://drive-api.proton.me/auth/v4/refresh: Invalid refresh token (Code=10013, Status=400)
2026/06/20 17:32:13 DEBUG : proton drive root link ID 'folder1/folder2renamed': Using username and password to log in
2026/06/20 17:32:14 NOTICE: proton drive root link ID 'folder1/folder2renamed': 422 POST https://drive-api.proton.me/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422), Attempt 1
2026/06/20 17:32:14 ERROR : proton drive root link ID 'folder1/folder2renamed': 422 POST https://drive-api.proton.me/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422)
2026/06/20 17:32:14 CRITICAL: Failed to create file system for destination "proton:folder1/folder2renamed": couldn't initialize a new proton drive instance: 422 POST https://drive-api.proton.me/auth/v4/2fa: Incorrect login credentials. Please try again. (Code=8002, Status=422)