Fix External Rclone Connection Refused — Troubleshoot rcd Access with RcloneView

October 16, 2026 · 3 min read

Product Manager

When RcloneView cannot reach your external rclone server, the cause is almost always one of five things you can check in minutes.

RcloneView ships with an embedded rclone, but many users point it at an external rclone running on a NAS, VPS, or AWS EC2 instance through the Connect Manager. When that link fails with "connection refused", a timeout, or an authentication error, a short checklist finds the cause.

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.

Confirm rclone rcd Is Actually Running

RcloneView talks to an external rclone through its Remote Control API, started with rclone rcd. On the server, launch it with explicit credentials and address, for example rclone rcd --rc-user=<user> --rc-pass=<pass> --rc-addr=127.0.0.1:5572. The default external port is 5572, while the embedded instance uses 5582 on localhost.

A frequent mistake is binding to 127.0.0.1 and then connecting from another machine. Loopback only accepts local traffic. For a remote server, bind to 0.0.0.0:5572 and restrict access by IP in your firewall. Note that RcloneView is a GUI tool and is not installed on the server; the server only runs rclone.

Connecting RcloneView to an external rclone host

Check Network Path and Credentials

If rcd is running but the connection is still refused, test the path. From the machine running RcloneView, a health check against /rc/noop with your username and password should return a response. If it hangs, a firewall or cloud security group is blocking port 5572. On AWS EC2, the security group needs a Custom TCP rule for 5572 in addition to restricted SSH.

Authentication failures are separate: the username and password entered in RcloneView must match --rc-user and --rc-pass exactly, including case.

Entering external connection details in RcloneView

Verify Settings in Connect Manager

Open Settings > Connect Manager > New Connection and fill in the Display Name, the address in http://<host>:5572 form, and your credentials. If your server uses a self-signed certificate, the option to disable SSL certificate verification lets the connection proceed. Press Test Connection before saving so you see the result immediately.

If it still fails, enable rclone logging under Settings > Embedded Rclone, set the level to DEBUG, restart, and reproduce the problem to capture a log.