Moving from Dropbox to Proton hangs

What is the problem you are having with rclone?

Moving hangs a long time with an error 400 and not continueing.

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

root@gemini:~# rclone version
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)

Dropbox and Proton

rclone move mfc_db: mfc_proton: --progress --delete-empty-src-dirs --tpslimit 4 --transfers=2 --checkers=4 --protondrive-replace-existing-draft=true --max-duration=6h --cutoff-mode=hard --retries 3 --retries-sleep=10 -vvv --timeout=2m

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

[mfc_db]
type = dropbox
token = XXX

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

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

[rfc_proton]
type = protondrive
username = XXX
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

Log (still running)

2024/04/07 09:00:10 INFO  : Starting transaction limiter: max 4 transactions/s with burst 1
2024/04/07 09:00:10 DEBUG : rclone: Version "v1.66.0" starting with parameters ["rclone" "move" "mfc_db:" "mfc_proton:" "--progress" "--delete-empty-src-dirs" "--tpslimit" "4" "--transfers=2" "--checkers=4" "--protondrive-replace-existing-draft=true" "--max-duration=6h" "--cutoff-mode=hard" "--retries" "3" "--retries-sleep=10" "-vvv" "--timeout=2m"]
2024/04/07 09:00:10 DEBUG : Creating backend with remote "mfc_db:"
2024/04/07 09:00:10 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2024/04/07 09:00:10 DEBUG : Creating backend with remote "mfc_proton:"
2024/04/07 09:00:10 DEBUG : mfc_proton: detected overridden config - adding "{kpshc}" suffix to name
2024/04/07 09:00:10 DEBUG : proton drive root link ID '': Has cached credentials
2024/04/07 09:00:12 DEBUG : proton drive root link ID '': Used cached credential to initialize the ProtonDrive API
2024/04/07 09:00:12 DEBUG : fs cache: renaming cache item "mfc_proton:" to be canonical "mfc_proton{kpshc}:"
2024/04/07 09:00:12 INFO  : proton drive root link ID '': Transfer session HARD deadline: 2024/04/07 15:00:12
2024/04/07 09:00:12 DEBUG : mfc_db: Loaded invalid token from config file - ignoring
2024/04/07 09:00:12 DEBUG : Saving config "token" in section "mfc_db" of the config file
2024/04/07 09:00:12 DEBUG : mfc_db: Saved new token in config file
2024/04/07 09:02:16 DEBUG : Afbeeldingen/Amsterdam 12-4-2009/DVD/Adam_12-4-2009.iso: Need to transfer - File not found at Destination
Transferred:          512 MiB / 649.969 MiB, 79%, 7.255 MiB/s, ETA 19s
Transferred:            0 / 1, 0%
Elapsed time:      3m19.8s
Transferring:
2024/04/07 09:03:31 ERROR : Afbeeldingen/Amsterdam 12-4-2009/DVD/Adam_12-4-2009.iso: Failed to copy: 400 POST https://zrh-storage.proton.me/storage/blocks: Invalid content length (Code=2022, Status=400)
2024/04/07 09:03:31 ERROR : Afbeeldingen/Amsterdam 12-4-2009/DVD/Adam_12-4-2009.iso: Not deleting source as copy failed: 400 POST https://zrh-storage.proton.me/storage/blocks: Invalid content length (Code=2022, Status=400)
2024/04/07 10:05:04 INFO  : Signal received: interrupt
2024/04/07 10:05:04 INFO  : Dropbox root '': Committing uploads - please wait...
2024/04/07 10:05:04 INFO  : Exiting...
Transferred:          512 MiB / 512 MiB, 100%, 154.607 KiB/s, ETA 0s
Errors:                 1 (retrying may help)
Elapsed time:    1h4m53.8s

As you can see, it hangs on a faulty file.

  • How can I fix this faulty file? (there are more of these)
  • Why won't it proceed to the next file?

welcome to the forum,

not sure proton is designed to handle large .iso, not designed to be use for backups.
i ran into that problem.

the numerous problems with proton drive are well documented in the forum and rclone docs.
i was a paid subscriber to proton, i really wanted to use it with rclone.
i have since given up on that and moved on.
now, i use mullvad for vpn

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