[BUG] Decyphar-managed Rclone failing to mount on DUMB v2.4.0 and Decypharr v2.0 and v3.0.0-beta

[djkraft16]

Duplicate check

• I searched existing issues and did not find a matching report.

Before submitting, I have

• Reviewed the relevant DUMB docs and checked my configuration.
• Confirmed this is a DUMB backend issue and not only an upstream service issue.
• Re-tested on the latest applicable DUMB release, image tag, or branch head.
• Collected logs or enough detail to help reproduce the issue.

Which backend area is affected?

Other / unsure

What happened?

After updating to decypharr v2.0 and v3.0.0-beta, managed rclone consistently fails to mount. This is preventing downstream services from starting (plex and seerr). I have scoured the docs for DUMB and deycpharr and this doesnt seem to be addressed anywhere yet. There is another issue #131 on here which threw one of the same error messages, but my API keys are present in that location so it is something else causing it. I have attached relevant log info. I made an issue on the decypharr github last night as well, so check that out in case I missed anything on this one: sirrobot01/decypharr#241

Some swift assistance would be greatly appreciated as my setup is unusable in this state! 🤕

Steps to reproduce

1. Configure decypharr on v2.0 stable and/or v3.0.0-beta in DUMB v2.4.0
2. Configure managed rclone instance within the decypharr UI
3. Start/Restart Decypharr. Watch logs for generic "mount failed" messages

How are you running DUMB?

Docker container

DUMB version / image tag / branch marker

v2.4.0

Host OS / platform

Ubuntu 24.04

Affected services

decypharr, rclone

Relevant config or request payload

DUMB config:
  "config_dir": "/decypharr",
  "config_file": "/decypharr/config.json",
  "log_file": "/decypharr/logs/decypharr.log",
  "env": {},
  "mount_type": "rclone",
  "mount_path": "/mnt/debrid/decypharr",
  "api_keys": {
    "realdebrid": "rd_apikey"
  }

Service config:
 "mount": {
    "type": "rclone",
    "mount_path": "/mnt/debrid/decypharr/realdebrid",
    "rclone": {
      "port": "5572",
      "vfs_cache_mode": "off",
      "vfs_cache_max_age": "1h",
      "vfs_cache_poll_interval": "1m",
      "vfs_read_chunk_size": "128M",
      "vfs_read_chunk_size_limit": "off",
      "vfs_read_ahead": "128k",
      "async_read": true,
      "transfers": 4,
      "uid": 1000,
      "gid": 1000,
      "attr_timeout": "1s",
      "dir_cache_time": "5m",
      "log_level": "INFO"
    },
    "dfs": {},
    "external_rclone": {}
  },

Relevant log output

04/13/2026 11:48:51 PM    INFO     manager    Starting manager mount_path=/mnt/debrid/decypharr/realdebrid mount_type=rclone notifications=false version=2.0-stable`
04/13/2026 11:49:22 PM    ERROR    rclone    Mount operation failed
04/13/2026 11:49:22 PM    ERROR    rclone    Failed to mount rclone filesystem error="mount failed for"

Possibly related:
WARNING    DUMB    Decypharr backend not reachable on 127.0.0.1:8282; skipping download client setup

Additional context

No response

[djkraft16]

Update:
Changed version to the new Decypharr v2.1 today and saw more information given in the rclone error:
Failed to mount rclone filesystem error="failed to create rclone config: failed to create rclone config: failed to create config: POST http://localhost:5572/config/create giving up after 4 attempt(s)"

Still is not mounting successfully

[I-am-PUID-0]

Have you confirmed that the permissions are properly set for the user (PUID/PGID) on the host-side bind-mounted directories?

Can you set DEBUG logging for both DUMB and Decypharr to see if any additional details are revealed?

[djkraft16]

PUID and GUID are both 1000, same as before any of the updates. I attempted to set up external rclone instead of managed, and it mounts successfully most of the time but decypharr doesn't seem to connect to it at all. On the times it doesn't mount it logs this:

04/16/2026 09:20:22 AM DEBUG Rclone w/ Decypharr Serving remote control on http://[::]:5572/

04/16/2026 09:20:22 AM DEBUG Rclone w/ Decypharr Creating backend with remote "realdebrid:"

04/16/2026 09:20:22 AM CRITICAL Rclone w/ Decypharr Failed to load config file "/decypharr/rclone/rclone.conf": open /decypharr/rclone/rclone.conf: permission denied

[I-am-PUID-0]

PUID and GUID are both 1000, same as before any of the updates. I attempted to set up external rclone instead of managed, and it mounts successfully most of the time but decypharr doesn't seem to connect to it at all. On the times it doesn't mount it logs this:

04/16/2026 09:20:22 AM DEBUG Rclone w/ Decypharr Serving remote control on http://[::]:5572/

04/16/2026 09:20:22 AM DEBUG Rclone w/ Decypharr Creating backend with remote "realdebrid:"

04/16/2026 09:20:22 AM CRITICAL Rclone w/ Decypharr Failed to load config file "/decypharr/rclone/rclone.conf": open /decypharr/rclone/rclone.conf: permission denied

Try docker exec -it DUMB ls -al /decypharr/ and look at the rclone directory; it should be owned by your user.
If not, try docker exec -it DUMB chown -R 1000:1000 /decypharr/rclone/

[djkraft16]

Says it's owned by Ubuntu, which is 1000/1000

[I-am-PUID-0]

Says it's owned by Ubuntu, which is 1000/1000

Is the rclone.conf also owned by Ubuntu?

[djkraft16]

Also Ubuntu. However, I noticed the permissions are super restricted. -rw------- 1 ubuntu ubuntu 203 Apr 16 09:33 rclone.conf

Could this be the cause?

[djkraft16]

Update:
Confirmed this was the issue by doing chmod 777 on the rclone.conf file and then restarting decypharr with the managed rclone. It then successfully mounted, however I would like to note that the configs seem to be very janky right now in terms of the mount path. It currently mounts my realdebrid downloads into decypharr/__all__ AND decypharr/realdebrid for some reason despite my mount path in the UI settings being mnt/debrid/decypharr/realdebrid only. Not sure if this can be fixed in the config, but it was not like this before the decypharr v2.0 update.

[djkraft16]

Also @I-am-PUID-0 since you were looking at this, I just wanted to take the opportunity thank you for making and maintaining this DUMB project, it's really impressive! I've greatly enjoyed using it and have had little to no issues (except this decypharr update) and all the different features from available services being in one place is fantastic 👏

[I-am-PUID-0]

Update: Confirmed this was the issue by doing chmod 777 on the rclone.conf file and then restarting decypharr with the managed rclone. It then successfully mounted, however I would like to note that the configs seem to be very janky right now in terms of the mount path. It currently mounts my realdebrid downloads into decypharr/all AND decypharr/realdebrid for some reason despite my mount path in the UI settings being mnt/debrid/decypharr/realdebrid only. Not sure if this can be fixed in the config, but it was not like this before the decypharr v2.0 update.

That's odd; I'm not sure why Decypharr wouldn't have set the permissions properly on rclone.conf.

There were some significant changes - even breaking changes - introduced in v2.0.0 of Decypharr. Namely, the mount locations being used became consolidated in the new release.

As for the config issue, try going to Decypharr's Web UI and saving the settings, even without changes, from there; that should update the Decypharr config.json

[djkraft16]

Update: Confirmed this was the issue by doing chmod 777 on the rclone.conf file and then restarting decypharr with the managed rclone. It then successfully mounted, however I would like to note that the configs seem to be very janky right now in terms of the mount path. It currently mounts my realdebrid downloads into decypharr/all AND decypharr/realdebrid for some reason despite my mount path in the UI settings being mnt/debrid/decypharr/realdebrid only. Not sure if this can be fixed in the config, but it was not like this before the decypharr v2.0 update.

That's odd; I'm not sure why Decypharr wouldn't have set the permissions properly on rclone.conf.

There were some significant changes - even breaking changes - introduced in v2.0.0 of Decypharr. Namely, the mount locations being used became consolidated in the new release.

As for the config issue, try going to Decypharr's Web UI and saving the settings, even without changes, from there; that should update the Decypharr config.json

I'll give that a try, thanks. If that doesn't solve things, is it possible to revert back to the previous decypharr version?

[I-am-PUID-0]

Yes. You can pin Decypharr to a specific release, though I would recommend using the latest release, as it offers improvements and fixes.