[BUG] Proton Drive backups can indefinitely stall, rclone upgrade needed

[EthanC]

Prerequisites

• I have read the troubleshooting guide

Rclone Pre-flight Checklist (if applicable)

• This issue is NOT related to rclone (skip if not using rclone)
• I have tested rclone listremotes and rclone lsd remote: on the host and they work
• I have verified the rclone config is mounted into the container
• I have restarted the container after config changes

Bug Description

Zerobyte v0.42.0 bundles rclone 1.75.0. When Proton Drive returns HTTP 502 during upload, rclone retries using an already-consumed stream, which then causes Proton to return HTTP 422. This can cause Zerobyte's backup upload to stall or silently create a truncated restic pack.

rclone 1.75.1 (https://github.com/rclone/rclone/releases/tag/v1.75.1) fixes this issue, thus Zerobyte needs to bump its dependency please.

Fix corrupted uploads after a retried upload error (Nick Craig-Wood)

Steps to Reproduce

1. Proton returns 502 Bad Gateway during an upload.
2. rclone 1.75.0 incorrectly retries using an already-consumed stream.
3. Proton returns 422 file already exists.
4. The upload can stall or silently create a truncated restic pack.

Expected Behavior

Upload gracefully fails.

Zerobyte version / commit

v0.42.0

Deployment Method

Docker Compose

Backup/Repository Context

No response

Logs / Error Messages

N/A

[nicotsx]

Should be resolved in the last v0.43.1 version