Fix Rclone Config Password Errors — Resolve Encrypted Config Issues with RcloneView

September 23, 2026 · 4 min read

Developer Advocate

When the Config Password protecting your rclone.conf file gets out of sync, every remote in RcloneView stops loading at once — here's how to diagnose it and get back in.

RcloneView's Settings tab includes a Config Password option under Embedded Rclone, which encrypts your entire rclone.conf file — the file holding every remote you've configured, not just one provider. That's different from encrypting individual files with a Crypt remote; a Config Password protects the credentials and tokens for all your remotes at once. When that password is wrong, missing, or out of sync with what actually encrypted the file, RcloneView can't decrypt any remote, and the whole explorer appears empty or throws connection errors on startup.

Manage & Sync All Clouds in One Place

RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.

One-click jobs: Copy · Sync · Compare
Schedulers & history for reliable automation
Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more

WindowsmacOSLinux

Get Started Free →

Free core features. Plus automations available.

Recognizing a Config Password Problem

The symptom is usually total, not partial: instead of one remote failing to connect, every remote — Google Drive, S3, Dropbox, all of them — fails at once, often right after RcloneView starts or after the embedded rclone process restarts. Check the Log tab in the bottom Info View, or enable file-based logging in Settings > Embedded Rclone with log level set to DEBUG, then restart the embedded rclone process. A config decryption failure shows up clearly in the log rather than as a provider-specific auth error, which is a clear way to tell this apart from an expired OAuth token or a revoked API key.

Reviewing job history and logs after a config password error in RcloneView

Common Causes and Fixes

Most Config Password issues trace back to one of a few situations:

Password entered incorrectly after an update or reinstall. If you moved RcloneView to a new machine or reinstalled it, re-enter the exact Config Password in Settings > Embedded Rclone > Config Password. There's no partial match — a single wrong character prevents decryption of the entire file.

A stale rclone.conf path. RcloneView's Local Rclone config location setting points to a specific file. If a previous install left behind an unencrypted or differently-encrypted config at that path, RcloneView may be reading the wrong file entirely. Verify the config location in Settings matches where your actual encrypted rclone.conf lives.

Forgotten password with no recovery option. Rclone's config encryption has no backdoor — if the password is truly lost, the existing rclone.conf cannot be decrypted. Your only path forward is removing the encrypted file and re-adding each remote from scratch through Remote > New Remote, which is why keeping a password manager entry for this value matters as much as any cloud provider credential.

Re-adding a remote in RcloneView after a config password reset

Preventing Lockouts Going Forward

Before changing a Config Password, export your current job definitions with Job Manager's Export option — it saves job settings as a portable JSON file, documenting which remotes and jobs existed even though it won't restore credentials on its own. RcloneView also mounts and syncs 90+ providers from one window on Windows, macOS, and Linux, so rebuilding remotes from scratch through New Remote takes minutes rather than hours.

Reviewing job settings before changing the config password in RcloneView

When escalating to support, follow the same log collection steps used for other rclone issues: enable DEBUG logging, restart the embedded rclone process, reproduce the failure, and send the log file — decrypt errors are far easier to diagnose from raw log output than a screenshot.

Getting Started

Download RcloneView from rcloneview.com.
Check Settings > Embedded Rclone > Config Password and confirm it matches what originally encrypted your rclone.conf.
Enable DEBUG logging and restart the embedded rclone process to confirm the failure is a decrypt error, not a provider auth issue.
If the password truly can't be recovered, remove the encrypted config and re-add remotes through New Remote.

A Config Password protects every credential in your rclone.conf at once, so treat it with the same care as a master password — losing it means starting your remote list over.

Related Guides: