
Managing files across multiple cloud storage providers from a single Ubuntu server is frustrating without the right tool. If you have ever tried to juggle Google Drive, Amazon S3, Dropbox, and Backblaze B2 using separate apps or fragile custom scripts, you already know the pain. This guide shows you exactly how to install Rclone on Ubuntu 24.04 LTS using four different methods, configure your first cloud remote, and automate your backup workflow — from a clean system to a working sync job. Whether you are a beginner learning Linux server management or a seasoned sysadmin, every step here is production-tested and ready to run.
What Is Rclone and Why Use It on Ubuntu 24.04?
Rclone is a free, open-source command-line tool written in Go, often described as “rsync for cloud storage.” It supports over 70 cloud storage providers and lets you copy, sync, move, mount, and encrypt files across platforms from a single terminal command.
First released in 2012 and actively maintained by a large open-source community, Rclone has become the go-to CLI tool for Linux sysadmins who need reliable, scriptable cloud storage management. It ships as a single static binary, which means zero dependencies and zero drama when deploying to minimal Ubuntu server images.
Supported providers include:
- Google Drive
- Amazon S3 (and S3-compatible: Wasabi, DigitalOcean Spaces, Backblaze B2)
- Microsoft OneDrive
- Dropbox
- SFTP, FTP, WebDAV
- Mega
- Google Cloud Storage
- And 60+ more via the official provider list at rclone.org
Common use cases:
- Automated nightly cloud backups from a Linux server
- Cross-provider storage migrations without downloading locally
- Mounting remote cloud buckets as local FUSE directories
- Encrypted offsite archiving with built-in
cryptbackend - Sync jobs triggered by cron or systemd on headless servers
Prerequisites
Before you run a single command, confirm the following. Missing any one of these will cause the installation to fail or behave unexpectedly.
- OS: Ubuntu 24.04 LTS (Noble Numbat) — desktop or server edition
- User privileges: A non-root user with
sudoaccess - Internet connection: Required for all download-based install methods
curlorwget: Used to fetch the install script or binary archive; install withsudo apt install -y curl wgetif missing- System architecture check: Run
uname -mto confirm your CPU type — most Ubuntu servers returnx86_64(AMD64), but ARM64 users must download the matching archive for the manual method - Optional: An active account on your target cloud provider (Google Drive, Dropbox, Amazon S3, etc.) ready for the configuration step
Step 1: Update Your Ubuntu 24.04 System
Always refresh your package index and apply pending updates before installing new software. Stale package metadata is one of the most common causes of broken installs on Ubuntu servers.
sudo apt update && sudo apt upgrade -y
What this does: apt update fetches fresh metadata from all configured repositories. apt upgrade -y applies all pending package updates and auto-confirms the prompt with -y.
Expected output (abbreviated):
Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
If you see pending upgrades, let them complete before moving on. Rebooting after a kernel update is good practice on production servers.
Step 2: Choose Your Rclone Installation Method
Ubuntu 24.04 LTS supports four distinct methods to install Rclone on Ubuntu 24.04. Each one has a different trade-off between version freshness, update handling, and feature availability.
| Method | Version on Ubuntu 24.04 | Auto-Updates | rclone mount |
Best For |
|---|---|---|---|---|
| APT | 1.60.x | Yes (apt upgrade) |
Yes | Stable, managed systems |
| Official Script | 1.73.x (latest) | Manual (selfupdate) |
Yes | Most users — recommended |
| Snap | 1.73.x (latest) | Yes (snap refresh) |
No | Quick installs, no mount needed |
| Manual Binary | Any version | Manual | Yes | Air-gapped or offline servers |
The version gap between APT (1.60.x) and upstream (1.73.x) matters. Newer cloud backends, bug fixes, and S3-compatible provider improvements only exist in the upstream release.
Recommendation: Use the Official Script method unless you have a specific reason to stick with Ubuntu’s packaged version. It gives you the latest stable release and a clean upgrade path via
rclone selfupdate.
Step 3: Install Rclone on Ubuntu 24.04 — All Four Methods
Method 1: Install Rclone via APT (Ubuntu Repository)
This is the simplest path. One command, handled entirely by Ubuntu’s package manager, with automatic updates during routine apt upgrade runs.
sudo apt install -y rclone
What this does: Pulls the rclone package from Ubuntu’s Universe repository and installs it system-wide. No extra configuration needed.
Verify the install:
rclone version
Expected output:
rclone v1.60.1-DEV
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.8.0-51-generic (x86_64)
- os/type: linux
- os/arch: amd64
Limitation: Ubuntu 24.04 ships Rclone 1.60.x, which is significantly behind upstream 1.73.x. You will miss newer cloud backends and recent bug fixes.
If you plan to switch methods later, remove the APT package first to avoid PATH conflicts:
sudo apt remove --autoremove -y rclone
Method 2: Install Rclone via Official Script (Recommended)
This method pulls the current stable release directly from rclone.org. It auto-detects your CPU architecture, installs the binary to /usr/bin/rclone, adds man pages, and skips the download entirely if the same version is already installed.
Step 2a: Remove any existing APT Rclone install (skip if not installed):
sudo apt remove --autoremove -y rclone
Step 2b: Ensure curl is available:
sudo apt install -y curl
Step 2c: Run the official install script:
curl -fsSL https://rclone.org/install.sh | sudo bash
What each flag does:
-f— Fail silently on HTTP errors instead of serving an error page to bash-s— Silent mode; suppresses progress output-S— Show errors even in silent mode-L— Follow HTTP redirects automatically
Expected output:
rclone v1.73.2 has been downloaded and installed.
Verify the install:
rclone version
Expected output:
rclone v1.73.2
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.8.0-51-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.24.1
- go/linking: static
- go/tags: none
Security note: Always confirm the URL is https://rclone.org/install.sh before piping to bash on production systems. The official rclone.org domain is the only trusted source for this script.
Future updates:
# Check if a newer version exists
sudo rclone selfupdate --check
# Apply the update
sudo rclone selfupdate
Method 3: Install Rclone via Snap
Snap delivers the latest Rclone stable release with automatic updates via snap refresh. This is a solid option for desktop users or developers who do not need rclone mount.
Install snapd if missing (common on Ubuntu server or minimal images):
sudo apt install -y snapd
Install Rclone:
sudo snap install rclone
Verify:
snap list rclone
Expected output:
Name Version Rev Tracking Publisher Notes
rclone 1.73.2 576 latest/stable aoilinux -
Critical limitation you must know: The Snap build runs in a strictly confined sandbox. This means rclone mount is completely blocked and will not work. If you need FUSE-based mounting, switch to Method 2.
Snap config path difference: The Snap version stores configuration at:
~/snap/rclone/current/.config/rclone/rclone.conf
Not the standard path used by APT and the official script:
~/.config/rclone/rclone.conf
This matters if you copy configs between installs.
Method 4: Manual Binary Installation
Use this for air-gapped servers, offline environments, or when you need a specific Rclone version pinned for reproducibility.
Step 4a: Download the binary archive:
wget https://downloads.rclone.org/rclone-current-linux-amd64.zip
For ARM64 servers, visit rclone.org/downloads/ and replace amd64 with arm64 in the URL.
Step 4b: Extract and install:
unzip rclone-current-linux-amd64.zip
cd rclone-*-linux-amd64
sudo cp rclone /usr/local/bin/
sudo chown root:root /usr/local/bin/rclone
sudo chmod 755 /usr/local/bin/rclone
Step 4c: Install the man page (optional but useful):
sudo mkdir -p /usr/local/share/man/man1
sudo cp rclone.1 /usr/local/share/man/man1/
sudo mandb
Step 4d: Clean up downloaded files:
cd ~
rm -rf rclone-*-linux-amd64*
Step 4e: Verify:
rclone version
Step 4: Configure Rclone on Ubuntu 24.04 — Add Your First Remote
With Rclone installed, the next step is to connect it to your cloud storage. The Rclone config wizard handles this interactively and stores credentials in a local config file. This is the configure Rclone on Ubuntu 24.04 step that unlocks every useful feature.
Launch the configuration wizard:
rclone config
You will see an interactive menu:
No remotes found, make a new one?
n) New remote
s) Set configuration password
q) Quit config
n/s/q>
Type n and press Enter to create a new remote.
Follow these sub-steps:
- Enter a name for your remote (e.g.,
gdrive,s3backup,my-dropbox) — this name is used in all future commands - Select the storage type from the numbered list (e.g.,
17for Google Drive,5for Amazon S3,9for Dropbox) - Complete provider-specific authentication (OAuth2 for Google/Dropbox/OneDrive, access key/secret for S3)
For headless Ubuntu servers without a browser (OAuth2 flow):
Run this command on a local machine that has a browser:
rclone authorize "drive"
Copy the token it outputs, then paste it back into your server’s rclone config session when prompted.
Verify the remote is working:
# List all configured remotes
rclone listremotes
# Test connectivity — list root directories on the remote
rclone lsd gdrive:
Config file location by install method:
| Install Method | Config Path |
|---|---|
| APT / Official Script | ~/.config/rclone/rclone.conf |
| Snap | ~/snap/rclone/current/.config/rclone/rclone.conf |
Step 5: Use Essential Rclone Commands on Your Linux Server
Once your remote is configured, these are the commands you will use most on a daily Linux server workflow.
List files and directories:
# Recursive file list with sizes
rclone ls remote:path
# Directories only
rclone lsd remote:path
Copy files without deleting anything at the destination:
rclone copy /local/path remote:bucket/path --progress
This is safe — it only adds or updates files. It never deletes anything at the destination.
Sync directories (mirror mode — use with caution):
# Always dry-run first
rclone sync /local/path remote:bucket/path --dry-run
# Apply the sync when you are confident
rclone sync /local/path remote:bucket/path --progress
Warning:
rclone syncdeletes files at the destination that do not exist at the source. Always run--dry-runfirst on any data you care about.
Key flags to include in production commands:
| Flag | Purpose |
|---|---|
--dry-run |
Simulate without making changes |
--progress |
Show real-time transfer stats |
--transfers 8 |
Run 8 parallel file transfers (default: 4) |
--bwlimit 10M |
Cap bandwidth at 10 MB/s |
--log-file /var/log/rclone.log |
Write output to a log file |
Step 6: Mount Cloud Storage as a Local Directory (FUSE)
Rclone mount lets you browse and interact with cloud storage as if it were a local folder on your Ubuntu 24.04 system. This requires a FUSE install and only works with APT or official script installs — not Snap.
Install FUSE:
sudo apt install -y fuse
Create a mount point and mount your remote:
mkdir ~/cloud-mount
rclone mount gdrive: ~/cloud-mount --daemon --vfs-cache-mode full
What --vfs-cache-mode full does: Enables full read and write caching for the best interactive experience. Without it, random-access reads from cloud storage will be very slow.
Unmount when done:
fusermount -uz ~/cloud-mount
VFS cache mode options:
| Mode | Behavior | Use Case |
|---|---|---|
off |
No caching | Low resource, read-once transfers |
minimal |
Cache writes only | Light workloads |
full |
Full read/write caching | Interactive or GUI access |
Note: The --daemon flag runs the mount in the background. Remove it for foreground or debugging use.
Step 7: Automate Rclone with Cron and Systemd
Manual syncs are fine for testing, but production Rclone on Ubuntu 24.04 setup always means automation.
Automated daily backup with cron (runs at 2 AM):
crontab -e
Add this line:
0 2 * * * rclone sync /home/user/docs gdrive:backup >> /var/log/rclone-backup.log 2>&1
The 2>&1 redirect captures both stdout and stderr into the log file so you can diagnose failures without a terminal session.
Auto-mount at boot with systemd:
Create the service file:
sudo nano /etc/systemd/system/rclone-mount.service
Paste this content:
[Unit]
Description=Rclone Mount - Google Drive
Requires=network-online.target
After=network-online.target
[Service]
Type=notify
Environment=RCLONE_CONFIG=/home/youruser/.config/rclone/rclone.conf
ExecStart=/usr/bin/rclone mount gdrive: /home/youruser/cloud-mount \
--vfs-cache-mode full \
--log-file /var/log/rclone-mount.log
ExecStop=/bin/fusermount -uz /home/youruser/cloud-mount
Restart=on-failure
[Install]
WantedBy=multi-user.target
Enable and start:
sudo systemctl daemon-reload
sudo systemctl enable rclone-mount.service
sudo systemctl start rclone-mount.service
sudo systemctl status rclone-mount.service
Replace youruser and gdrive: with your actual username and configured remote name.
Troubleshooting Common Rclone Errors on Ubuntu 24.04
Even clean installs hit issues. Here are the five most common problems and their fixes.
1. rclone: command not found
Cause: The binary directory is not in your shell’s $PATH.
Fix:
which rclone # Find where the binary actually is
export PATH=$PATH:/usr/local/bin # Add it if needed
echo 'export PATH=$PATH:/usr/local/bin' >> ~/.bashrc # Make it permanent
2. FUSE Mount Error: fuse: device not found
Full error: fuse: device not found, try 'modprobe fuse' first
Fix:
sudo modprobe fuse
sudo apt install -y fuse
3. OAuth2 Token Expired or Invalid
Error: invalid_grant or Token has been expired or revoked
Fix:
rclone config reconnect remote:
This refreshes the OAuth token without requiring you to delete and recreate the entire remote.
4. Snap Build: rclone mount Not Working
Cause: The Snap sandbox blocks FUSE access by design. This is not a bug you can fix — it is a hard restriction.
Fix — switch to the official script:
sudo snap remove rclone
curl -fsSL https://rclone.org/install.sh | sudo bash
rclone version
5. Slow Transfer Speeds
Cause: Default settings use only 4 parallel transfers and 8 checkers, which is too conservative for high-bandwidth connections or large buckets.
Fix — increase parallelism:
rclone copy /local/path remote:bucket --transfers 16 --checkers 32 --multi-thread-streams 4 --progress
Use --progress during tuning so you can see where the bottleneck is in real time. For bandwidth-limited environments, set --bwlimit 50M to cap at 50 MB/s instead of blasting the full connection.
Update and Remove Rclone on Ubuntu 24.04
Back up your config before any update:
cp ~/.config/rclone/rclone.conf ~/rclone.conf.bak
Updating Rclone:
| Install Method | Update Command |
|---|---|
| APT | sudo apt install --only-upgrade -y rclone |
| Official Script | sudo rclone selfupdate |
| Snap | sudo snap refresh rclone |
Removing Rclone:
| Install Method | Remove Command |
|---|---|
| APT | sudo apt remove --autoremove -y rclone |
| Official Script | sudo rm -f /usr/bin/rclone /usr/local/share/man/man1/rclone.1 |
| Snap | sudo snap remove rclone |
To also remove saved credentials and remote configurations:
rm -rf ~/.config/rclone/ # APT and official script
rm -rf ~/snap/rclone/ # Snap only
Only run the rm command above if you intend to permanently delete all saved tokens and remote settings.
Congratulations! You have successfully installed Rclone. Thanks for using this tutorial for installing Rclone on your Ubuntu 24.04 LTS system. For additional help or useful information, we recommend you check the official Rclone website.