Deploy and Host self hosted Debian rclone (Cloud Storage Sync From a Debian Box) on Railway

This template deploys a persistent Debian 12 box for running rclone against S3, Google Drive or Backblaze B2. Long transfers can run in a shared tmux session.

About Hosting Debian rclone open-source software on Railway (self hosted rclone sync and copy on a persistent Debian 12 box template)

rclone is open-source software, so the code is yours to inspect and run, and this template gives you a Debian 12 (bookworm) box where it lives.

Why Deploy Debian rclone, the Syncthing alternative on Railway (Railway Free Trial)

Syncthing syncs folders between your own devices but does not push copies to S3, Google Drive or B2 on a schedule, so you need a server running rclone.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Debian rclone on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

Railway vs Other Hosting Providers and VPS for Debian rclone self hosting

Railway gives you a working Debian rclone box with a persistent /home, while a VPS means you run the OS yourself. Compare the options below.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	Debian 12 with /home on a volume and SSH via TCP proxy, deployed from one template.	A Droplet with root access, but you manage SSH keys, firewalls, and updates.
AWS	One service with a generated password and shared tmux session, no VPC setup needed.	EC2 with close S3 proximity, but you handle instance setup, security groups, and volumes.
Hetzner	A persistent home so your rclone config under /home survives redeploys.	Low-cost servers with generous bandwidth, but you install and maintain Debian, rclone, and tmux.

Pick Railway for a quick Debian rclone setup, or a VPS when you need full root control.

Common Use Cases for hosted Debian rclone

Scheduled S3 mirror: Keep a project folder under /home/debian and run rclone sync against an S3 remote on a schedule, so the bucket matches the last good state.
Archive copy to B2: Use rclone copy from Google Drive to Backblaze B2, since copy never deletes files from the destination.
Safe sync preview: Run rclone sync --interactive --dry-run first, read what it would delete or overwrite, then repeat the command without the flag.
Long bucket-to-bucket copy: Start the transfer in the shared main tmux session, detach with Ctrl-b d, and reattach later to check progress after your laptop disconnects.
Transfer audit log: Add --log-file under /home so the full record survives redeploys and you can grep it later for skipped or failed files.

Dependencies for Debian rclone Docker hosted on Railway

Debian rclone runs as one Railway service built from the Debian 12 Web Terminal image, so you need one service and one volume. Only /home survives a redeploy, so rclone and its config must live there.

Deployment Dependencies for Managed Debian rclone Service (ttyd + OpenSSH + tmux)

The template runs ttyd on port 7681 behind HTTP basic auth and sshd on port 2222, with both sessions attaching to one tmux session named main.

Implementation Details for Debian rclone (Using Debian 12 Web Terminal official docker image)

The image uses debian:bookworm-20261027 and ships tmux 3.3a, git, curl, zip/unzip, rsync, and jq, but not rclone.

How does Debian rclone compare against other ways to sync files to S3, Google Drive or B2 from a server

Debian rclone vs rsync.net (Hosted Storage With SSH Access)

Where it fits: Debian rclone talks to S3, Google Drive and Backblaze B2 directly, so the bucket you already pay for becomes the destination.
Control: You own the box and the config under /home/debian/.config/rclone.
Where rsync.net wins: It is managed storage with rsync and SSH built in, so there is no VM to patch.

Debian rclone vs Syncthing (Peer-to-Peer Continuous Sync)

Where it fits: Syncthing keeps folders in step between your devices, while rclone runs deliberate jobs against a cloud remote.
Safety: A copy with --dry-run shows exactly what would change before any file moves.
Where Syncthing wins: For live two-way sync across laptops and phones, it is the better tool.

Debian rclone vs Duplicati (Encrypted Backup Client)

Where it fits: Duplicati is built around encrypted, versioned backups, while rclone moves files as they are.
Transparency: Objects land in your bucket as plain files you can inspect with standard tools.
Where Duplicati wins: It handles encryption and retention for you, which rclone does not do on its own.

Debian rclone vs a Laptop Cron Job (Scheduled Script on Your Machine)

Where it fits: A long copy on the Railway Debian box keeps running in tmux after your laptop sleeps or disconnects.
Reachability: The box stays online, so transfers do not depend on a personal machine being awake.
Where a laptop cron job wins: It costs nothing extra and keeps credentials on hardware you already control.

How to use Debian rclone (the OSS Cloud Storage Sync From a Debian Box)?

Work through these steps on your first day after the Debian service is online. The binary and config stay under /home so a redeploy does not break your backup job.

SSH in with ssh -p PORT debian@HOST, using the TCP proxy from Settings to Networking.
Fetch and unpack the zip:

mkdir -p ~/.local/bin && cd ~
curl -O https://downloads.rclone.org/rclone-current-linux-amd64.zip
unzip rclone-current-linux-amd64.zip
cp rclone-*-linux-amd64/rclone ~/.local/bin/rclone

Copy the binary to ~/.local/bin/rclone, not /usr/bin, which does not persist.
Run rclone config and add a remote for S3, Google Drive or B2.
Confirm the config location with rclone config file, which should show /home/debian/.config/rclone/rclone.conf.
Preview before syncing: rclone sync --interactive --dry-run SOURCE remote:DESTINATION.
Run long jobs in the shared session with tmux new-session -A -s main, then rclone copy --log-file /home/debian/copy.log SOURCE remote:DESTINATION, and detach with Ctrl-b d.

How to self host Debian rclone on other VPS Services (Debian 12 Web Terminal self hosting guide)

Clone the Repository

Clone the template repository and check out the pinned commit so the build matches the published image.

git clone https://github.com/onepush-dev/debian-web-terminal.git
cd debian-web-terminal
git checkout 3c32c09

Install Dependencies

Install Docker with the buildx plugin on the host. The image pulls ttyd 1.7.7 from GitHub during the build, so the host needs outbound HTTPS.

docker --version
docker buildx version

Configure Environment Variables

Set your own password and the ports, then add keys with SSH_AUTHORIZED_KEYS (separate multiple keys with a semicolon). Switch SSH_PASSWORD_AUTH to false once keys work.

export TERMINAL_USER=debian
export TERMINAL_PASSWORD="$(openssl rand -base64 18)"
export SSH_PORT=2222
export PORT=7681
export TZ=UTC

Start the Debian rclone Application

Build the image, then run it with a volume mounted at /home so rclone configs and binaries in ~/.local/bin survive restarts. Browse to http://your-domain:7681 or run ssh -p 2222 debian@your-domain.

Official Pricing of Debian rclone (Debian 12 Web Terminal pricing)

Debian rclone is free and open source, so there is no license fee to pay for the software itself. The template ships under the MIT license, and rclone is open source too.

Debian rclone cloud vs self hosted comparison (Pricing, features, costs, and more)

Running rclone on a persistent Debian 12 box keeps the binary, config and logs under /home, so a redeploy will not break your sync schedule.

Monthly cost of self hosting Debian rclone on Railway

Railway bills this single Debian service by resource use, with one volume mounted at /home. Check the Railway pricing page for current rates.

System Requirements for Hosting Debian rclone on a VPS

On a VPS, give the box enough disk for the rclone config and temporary transfer space, plus a stable outbound connection to your storage provider.

Frequently Asked Questions (FAQs)

Why does rclone installed with apt disappear after a redeploy?

Packages installed with apt live in the container layer, and only /home is on the persistent volume on this template. Put the rclone binary in ~/.local/bin instead, as described in the how-to steps, so it survives redeploys.

Where is rclone.conf stored?

By default it lives at /home/debian/.config/rclone/rclone.conf, which is on the persistent volume. Run rclone config file to confirm the exact path on your box.

What is the difference between sync and copy?

rclone sync makes the destination match the source, which can delete files on the destination. rclone copy only adds and updates files and never deletes anything, so use copy when you want a safe one-way transfer.

How do I preview a sync safely?

Run rclone sync --interactive --dry-run SOURCE remote:DESTINATION first.

How do I keep a long copy running after I disconnect?

Start a session with tmux new-session -A -s main, run your rclone copy with --log-file, then detach with Ctrl-b d. The job keeps running in tmux, and you can reattach later to check on it.

Which remotes can I configure on this box?

Run rclone config to add remotes for Amazon S3, Backblaze B2, Google Drive, and any other backend rclone supports. Each remote is stored as a named section in rclone.conf.