Proton drive rclone need help

Help and Support
1

What is the problem you are having with rclone?

I am using rclone via a restic container for my personal backups.

I reproduce the problem I am having, just by using rclone command (so I don’t think the trouble come from restic). I can’t upload file anymore on my proton drive (encrypted) remote.

It was working perfectly until this morning.

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

rclone v1.71.1

  • os/version: darwin 26.1 (64 bit)
  • os/kernel: 25.1.0 (arm64)
  • os/type: darwin
  • os/arch: arm64 (ARMv8 compatible)
  • go/version: go1.25.1
  • go/linking: dynamic
  • go/tags: cmount

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 copy --protondrive-replace-existing-draft=true docker-compose.yaml protonDriveSecured:```

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 = XXX@proton.me
password = XXX
mailbox_password = XXX
client_uid = XXX
client_access_token = XXX
client_refresh_token = XXX
client_salted_key_pass = XXX

[protonDriveSecured]
type = crypt
remote = protonDrive:Secured
filename_encryption = obfuscate
password = XXX
password2 = XXX

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

rclone copy --protondrive-replace-existing-draft=true docker-compose.yaml protonDriveSecured: -vv 
2025/10/02 22:18:00 DEBUG : rclone: Version "v1.71.1" starting with parameters ["rclone" "copy" "--protondrive-replace-existing-draft=true" "docker-compose.yaml" "protonDriveSecured:" "-vv"]
2025/10/02 22:18:00 DEBUG : Creating backend with remote "docker-compose.yaml"
2025/10/02 22:18:00 DEBUG : Using RCLONE_CONFIG_PASS password.
2025/10/02 22:18:00 DEBUG : Using config file from "/Users/laptop/.config/rclone/rclone.conf"
2025/10/02 22:18:00 DEBUG : fs cache: renaming child cache item "docker-compose.yaml" to be canonical for parent "/Users/laptop/Documents/docker"
2025/10/02 22:18:00 DEBUG : Creating backend with remote "protonDriveSecured:"
2025/10/02 22:18:00 DEBUG : Creating backend with remote "protonDrive:Secured"
2025/10/02 22:18:00 DEBUG : protonDrive: detected overridden config - adding "{kpshc}" suffix to name
2025/10/02 22:18:00 DEBUG : proton drive root link ID 'Secured': Has cached credentials
2025/10/02 22:18:01 DEBUG : proton drive root link ID 'Secured': Used cached credential to initialize the ProtonDrive API
2025/10/02 22:18:01 DEBUG : fs cache: renaming cache item "protonDrive:Secured" to be canonical "protonDrive{kpshc}:Secured"
2025/10/02 22:18:02 DEBUG : docker-compose.yaml: Need to transfer - File not found at Destination
2025/10/02 22:18:02.639373 WARN RESTY 422 POST https://mail.proton.me/api/drive/shares/BVtPSg36X7z4GUsrEW9gvNa-JZnkGIHeZy23C37yZf3zzlBvfgw633LwLEAfENOaTXAkWspz67KlOADnyD-I4g==/files: A file or folder with that name already exists (Code=2500, Status=422), Attempt 1
2025/10/02 22:18:02.639446 ERROR RESTY 422 POST https://mail.proton.me/api/drive/shares/BVtPSg36X7z4GUsrEW9gvNa-JZnkGIHeZy23C37yZf3zzlBvfgw633LwLEAfENOaTXAkWspz67KlOADnyD-I4g==/files: A file or folder with that name already exists (Code=2500, Status=422)
2025/10/02 22:18:04.073964 WARN RESTY 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422), Attempt 1
2025/10/02 22:18:04.074049 ERROR RESTY 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:04 ERROR : docker-compose.yaml: Failed to copy: 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:04 ERROR : Attempt 1/3 failed with 1 errors and: 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:04 DEBUG : docker-compose.yaml: Need to transfer - File not found at Destination
2025/10/02 22:18:04.829473 WARN RESTY 422 POST https://mail.proton.me/api/drive/shares/BVtPSg36X7z4GUsrEW9gvNa-JZnkGIHeZy23C37yZf3zzlBvfgw633LwLEAfENOaTXAkWspz67KlOADnyD-I4g==/files: A file or folder with that name already exists (Code=2500, Status=422), Attempt 1
2025/10/02 22:18:04.829552 ERROR RESTY 422 POST https://mail.proton.me/api/drive/shares/BVtPSg36X7z4GUsrEW9gvNa-JZnkGIHeZy23C37yZf3zzlBvfgw633LwLEAfENOaTXAkWspz67KlOADnyD-I4g==/files: A file or folder with that name already exists (Code=2500, Status=422)
2025/10/02 22:18:06.197003 WARN RESTY 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422), Attempt 1
2025/10/02 22:18:06.197087 ERROR RESTY 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:06 ERROR : docker-compose.yaml: Failed to copy: 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:06 ERROR : Attempt 2/3 failed with 1 errors and: 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:06 DEBUG : docker-compose.yaml: Need to transfer - File not found at Destination
2025/10/02 22:18:07.755024 WARN RESTY 422 POST https://mail.proton.me/api/drive/shares/BVtPSg36X7z4GUsrEW9gvNa-JZnkGIHeZy23C37yZf3zzlBvfgw633LwLEAfENOaTXAkWspz67KlOADnyD-I4g==/files: A file or folder with that name already exists (Code=2500, Status=422), Attempt 1
2025/10/02 22:18:07.755114 ERROR RESTY 422 POST https://mail.proton.me/api/drive/shares/BVtPSg36X7z4GUsrEW9gvNa-JZnkGIHeZy23C37yZf3zzlBvfgw633LwLEAfENOaTXAkWspz67KlOADnyD-I4g==/files: A file or folder with that name already exists (Code=2500, Status=422)
2025/10/02 22:18:09.167909 WARN RESTY 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422), Attempt 1
2025/10/02 22:18:09.167980 ERROR RESTY 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:09 ERROR : docker-compose.yaml: Failed to copy: 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:09 ERROR : Attempt 3/3 failed with 1 errors and: 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)
2025/10/02 22:18:09 INFO  : 
Transferred:   	    3.105 KiB / 3.105 KiB, 100%, 529 B/s, ETA 0s
Errors:                 1 (retrying may help)
Elapsed time:         6.9s

2025/10/02 22:18:09 DEBUG : 7 go routines active
2025/10/02 22:18:09 NOTICE: Failed to copy: 422 POST https://fra-storage.proton.me/storage/blocks: Operation failed: Please retry (Code=200501, Status=422)

Please I need help, I don’t understand, the ls command is working perfectly.

If you need additional information don’t hesitate (sorry for my english mistakes I am not an english native speaker).

2

welcome to the forum,

there is no expectation for proton remotes to work at all.
proton drive tech support absolutely refuses to support rclone.
the forum is full of posts about all that.

in addition, the author of the rclone proton remote has not logged into the forum for 18+ months.

the proton remote is beta, but really, imho, is should be labeled experimental and needs to be deprecated.

3

:smiling_face_with_tear: really sad about what I just read, it was working so perfectly for the last 10 months and it suddenly stop working.

4

that has been discussed many times in the forum.

1 Like
5

any good cloud storage not too expensive to suggest then ?

6

about proton, check out
https://forum.rclone.org/t/does-proton-silently-rate-limit-accounts-that-use-rclone-api-with-proton-drive/52548

sure, but that is a fuzzy question, hard to provide a good answer??

7

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