Docker / Homelab / Server

Control your server, homelab, or mom's PC with the easiest solution to manage remote rclone instances.

The brain of Rclone UI is rclone, but it doesn't have to be only the local rclone. You can run in Docker or a remote VM and connect to it through Rclone UI.

To connect to it simply start rclone rcd and set a port, see below for more info.

Docker Compose

services:
  rclone:
    image: rclone/rclone
    container_name: rclone
    command: rcd --rc-addr=0.0.0.0:5572 --rc-no-auth
    ports:
      - 5572:5572
      - 53682:53682 # needed for rclone OAuth connections
    volumes:
      - ./config:/config/rclone
      - /path/to/data:/data

Docker CLI

docker run -d \
  --name rclone \
  -p 5572:5572 \
  -p 53682:53682 \ # needed for rclone OAuth connections
  -v ./config:/config/rclone \
  -v /path/to/data:/data \
  rclone/rclone rcd --rc-addr=0.0.0.0:5572 --rc-no-auth

Without Docker

Just start the rcd daemon directly:

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

Notes

• After starting up rclone using your preferred method, open Rclone UI and navigate to Settings > Hosts, see Other instances.
• Make sure to allow traffic to port 5572 in your firewall and/or reverse proxy (nginx/caddy/traefik).
• Rclone UI can connect to any RCD port, so you can customize the default 5572 port.
• Use --rc-user and --rc-pass instead of --rc-no-auth in production.