Other instances

Configure Rclone UI to use a different rclone backend than your local one.

In essence, this allows you to control other rclone instances running on other devices like servers or homelabs.

Just start the daemon on the other machine and add it as a host in Rclone UI. You can now control the rclone running on that machine: operations, transfers and remotes are those of the host, while the interface stays on your local machine.

Prerequisites

The device has to have rclone installed, you can see the install options in the CLI docs.

All that's needed is to run rclone in rcd mode and allow access to it:

rclone rcd --rc-addr=0.0.0.0:5572 --rc-no-auth

# or set a user and password instead of open access
rclone rcd --rc-addr=0.0.0.0:5572 --rc-user=admin --rc-pass=yourpassword

--rc-addr makes the daemon reachable from other machines (rclone binds to localhost without it), and the user and password go into the "Auth" fields when you add the host. Use --rc-no-auth only on a network you trust (ideally never).

It can run in a container, as a service or in a terminal. The Docker / Homelab / Server page has the commands for each way of starting it.

Adding a host

Open the toolbar, type settings and open the Hosts section.

Here you can see each each host as a card with info about the operating system, version, and an ONLINE status if the daemon is running on that machine.

To add one tap the plus button and fill in the URL of the daemon on the remote server. You can also give it a name for your own reference.

Switch between hosts

Hover over a host card to reveal the checkbox, tap the checkbox to make it the active host.

While another host is active, a strip in the corner of the settings reads "Connected to" followed by its name. A few things stay bound to the local machine and are disabled: the Config and Binary sections, because they manage files on this computer.