Protondrive 503 then 400

What is the problem you are having with rclone?

Greetings!
First of all thanks for everyone who is working on this amazing project!

I am running into 503 Service Unavailable then 400 afterwards with a protondrive remote after about 30GBs of Upload.

I tried it around 10 times with and without vfs-cache and different parameters, always the same issue after 10 to 80Gbs.

I use a docker compose with duplicacy wich first creates a local backup on a ZFS hdd array then copies it to the locally FUSE mounted protondrive.

For mounting the protondrive I use the docker-rclone container:

I am not sure if this has to do with Rate-Limits of Protondrive. Maybe I could fix this by moving larger files?

Thank you! to anyone who takes the time to look at this

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

# In the docker container https://github.com/wiserain/docker-rclone
root@f2bf9c4298aa:/# rclone --version
rclone v1.69.1
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.8.12-8-pve (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.24.0
- go/linking: static
- go/tags: none

# On the host (used only for creating the config)
rclone --version
rclone v1.70.0-beta.8606.e0d477804
- os/version: debian 12.9 (64 bit)
- os/kernel: 6.8.12-8-pve (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.24.0
- go/linking: static
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

protondrive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

This is an assumption as I use the the wiserain "docker-rclone" container

rclone mount protondrive:/backups /data --vfs-cache-mode full --allow-non-empty --vfs-cache-max-size 64 --transfers 2 --protondrive-replace-existing-draft=true --buffer-size 64M --vfs-read-chunk-size 32M --vfs-read-chunk-size-limit 256M

This is my full docker compose, in case my assumption is wrong:

  rclone-mount:
    container_name: rclone
    image: wiserain/rclone                      # or ghcr.io/wiserain/rclone
    restart: unless-stopped
    cap_add:
      - SYS_ADMIN
    devices:
      - /dev/fuse
    security_opt:
      - apparmor:unconfined
    environment:
      - TZ=Europe/Berlin
      - RCLONE_REMOTE_PATH=protondrive:/backups
      - RCLONE_LOG_FILE=/log/rclone-mnt.log
      - RCLONE_LOG_LEVEL=DEBUG
      # I also tried it with just --vfs-cache-mode full --allow-non-empty
      - RCLONE_MOUNT_USER_OPTS=--vfs-cache-mode full --allow-non-empty --vfs-cache-max-size 64 --transfers 2 --protondrive-replace-existing-draft=true --buffer-size 64M --vfs-read-chunk-size 32M --vfs-read-chunk-size-limit 256M
      - RCLONE_REFRESH_ON_MOUNT=.
    volumes:
      - /root/.config/rclone/:/config
      - ${APP_DIR:?err}/rclone/log:/log
      - /mnt/vfs-cache/rclone/cache:/cache
      - /mnt/protondrive/backups:/data:shared

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 = lorenz@XXXXXXX
password = XXX
client_uid = XXX
client_access_token = XXX
client_refresh_token = XXX
client_salted_key_pass = XXX

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

Search forum for similar topics. It is quite common issue. Proton drive implementation is not maintained at the moment so unfortunately not much anybody can do about it.

Hi kapitainsky
Thanks for your response.
What specifically is a very common issue?
I have not found any post regarding specifically responses with a 503 status code. Rate limits are very common I understand, but thought this would be a 429 or not?

What I am saying is that Proton rclone implementation experience software rot for some time now. More and more issues nobody is looking to investigate and fix.

Until somebody will feel like spend some time on it things will only get worse.

Sorry for bad news.

No worries, thanks anyway.

I am paying for the duo plan for mail, vpn etc. and have 1TB of "free" storage anyway. I just hoped I could put this to use somehow

drop an email to proton guys:) and ask them to open their API to 3rd party tools. Existing rclone implementation relies on somebody reverse engineering things - and as such is real hard to carry on maintaining when original developer lost interest.

Proper documented API would make it so much easier. But seems Proton is not really interested so far.