VPS Hosting

How to Set Up a Seedbox on a VPS, Step by Step

qBittorrent in Docker on Ubuntu 24.04, its web UI reachable only through an SSH tunnel, files pulled home over SFTP or rclone — and when a VPS is the wrong tool.

8 min read
How to Set Up a Seedbox on a VPS, Step by Step

A seedbox is not a special kind of server. It is a torrent client that runs all day on a machine with a fast uplink, a web page to drive it, and a way to get the finished files home. Any Linux VPS can be that machine in about twenty minutes. Whether it should be is a separate question, and we answer it at the end — the short version is that a VPS wins on control and loses on disk.

This guide builds the setup we would actually run: qBittorrent in Docker, its web interface reachable only through an SSH tunnel, and files pulled home over SFTP or rclone. Nothing is exposed to the internet except the torrent port itself.

What you need before you start

  • A VPS running Ubuntu 24.04 LTS (Debian 12 works the same way). One vCPU and 1 GB of RAM are enough for qBittorrent alone; 2 GB leaves room for a media server or Sonarr later.
  • Disk sized for the library, not for the OS. This is where VPS plans hurt: a typical $5–20 instance ships with 25 to 100 GB of NVMe. Add a block-storage volume if you need more, and price it before you commit — we did that arithmetic in the best VPS for a seedbox.
  • A traffic allowance you will not blow through. Seeding is upload. Vultr's regular Cloud Compute plans include 1 to 3 TB a month depending on size; Hetzner's EU cloud plans include 20 TB. Read the overage rate on your host's pricing page before the first big torrent.
  • An SSH key on your own computer. If ls ~/.ssh/id_ed25519.pub returns nothing, create one with ssh-keygen -t ed25519.
  • Your provider's rules on torrent traffic. Some hosts forbid public BitTorrent outright in their acceptable-use policy; many forward copyright notices to you. Use the box for content you have the right to share — Linux images, public-domain archives, your own files.

Which VPS? If you do not have one yet, an hourly-billed instance is the low-risk way to try this guide: Vultr's Cloud Compute starts at $5 a month for 1 vCPU / 1 GB / 25 GB, and destroying the server stops billing the same hour.

Step 1 — Secure the server before installing anything

Log in as root once, create a normal user, and give it your key:

ssh root@YOUR_SERVER_IP
adduser seed
usermod -aG sudo seed
rsync --archive --chown=seed:seed ~/.ssh /home/seed

Then, from a second terminal, check that ssh seed@YOUR_SERVER_IP works before you lock root out. Once it does, put the hardening in its own file rather than editing sshd_config:

printf 'PermitRootLogin no\nPasswordAuthentication no\n' | sudo tee /etc/ssh/sshd_config.d/00-hardening.conf
sudo systemctl reload ssh
sudo sshd -T | grep -Ei 'permitrootlogin|passwordauthentication'

Why a separate file: on Ubuntu, sshd_config includes sshd_config.d/*.conf at the top, and for each setting the first value read wins. Many cloud images ship a 50-cloud-init.conf there with PasswordAuthentication yes, which silently overrides an edit further down sshd_config. A file named 00-… is read first. The last command prints the values the server actually uses — both should say no. Brute-force bots find a new VPS within minutes; key-only login makes them irrelevant.

Now the firewall. Allow SSH and the torrent port, nothing else:

sudo ufw allow OpenSSH
sudo ufw allow 6881/tcp
sudo ufw allow 6881/udp
sudo ufw enable

Note what is not in that list: the web interface port. It stays closed on purpose.

Step 2 — Install Docker

Docker keeps the torrent client, its settings and its updates in one place you can delete cleanly. Install it from Docker's own repository with the convenience script, then let your user run it:

curl -fsSL https://get.docker.com | sudo sh
sudo usermod -aG docker seed

Log out and back in so the group change applies, then check with docker run --rm hello-world.

One trap worth knowing: Docker writes its own firewall rules and bypasses ufw for published ports. A port you publish as -p 8080:8080 is reachable from the internet even though ufw says it is closed. That is why the next step binds the web interface to 127.0.0.1 only.

Step 3 — Run qBittorrent

Create the folders and a compose file:

mkdir -p ~/seedbox/{config,downloads} && cd ~/seedbox
nano compose.yaml
services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - WEBUI_PORT=8080
      - TORRENTING_PORT=6881
    volumes:
      - ./config:/config
      - ./downloads:/downloads
    ports:
      - 127.0.0.1:8080:8080   # web UI: local only, reached through SSH
      - 6881:6881             # torrent traffic
      - 6881:6881/udp
    restart: unless-stopped

PUID and PGID must match your user — check with id seed; the first user created on Ubuntu is usually 1000. Start it:

docker compose up -d
docker logs qbittorrent 2>&1 | grep -i password

Recent qBittorrent versions no longer ship a fixed default password: the log prints a temporary password for the admin user at first start. Copy it — you will change it in a minute.

Step 4 — Open the web interface through an SSH tunnel

On your own computer:

ssh -N -L 8080:127.0.0.1:8080 seed@YOUR_SERVER_IP

Leave that running and open http://localhost:8080. You are now talking to qBittorrent over the encrypted SSH connection; nobody else can even see the login page.

In Tools → Options:

  • Web UI → Authentication: set a real password for admin.
  • Connection → Listening port: confirm 6881, and untick Use UPnP / NAT-PMP (there is no router to configure on a VPS).
  • Downloads → Default save path: /downloads.
  • BitTorrent → Seeding limits: set a ratio or time at which torrents pause. On a metered plan this is your bandwidth budget; without it, one popular torrent will seed until the month's allowance is gone.
  • Speed: a global upload limit is the bluntest and most reliable cap if your plan bills overage.

Step 5 — Get the files home

A seedbox is only useful if the files leave it. Three ways, from simplest to most automated:

  1. SFTP. Any SFTP client (FileZilla, Cyberduck, WinSCP) connects with the same seed user and key. Browse to ~/seedbox/downloads. Nothing to install on the server.
  2. rsync over SSH for repeatable, resumable copies:
    rsync -avP seed@YOUR_SERVER_IP:seedbox/downloads/ ~/Downloads/seedbox/
    
    Run it again and it copies only what changed.
  3. rclone to push finished files to cloud storage on its own, so the VPS disk never fills. This is the piece that turns a box into a pipeline — we wire it up with Sonarr and Radarr in seedbox automation.

Step 6 — Keep it running

  • Updates: docker compose pull && docker compose up -d from ~/seedbox updates qBittorrent without touching your settings in ./config. Run sudo apt update && sudo apt upgrade for the OS.
  • Disk: df -h before you add anything large. A full disk stops downloads and can corrupt the client's state.
  • Traffic: your host's dashboard shows the month's transfer. Check it after the first week to see whether your seeding limits are right.
  • Backups: the only thing worth backing up is ./config — a few megabytes that hold your settings and torrent list.

When a VPS is the wrong tool

Everything above works. The question is what it costs per terabyte, and that is where a VPS loses. Cloud instances charge NVMe prices for disk and meter upload; a dedicated seedbox charges hard-drive prices and often includes unmetered 10 Gbps traffic. Our seedbox price breakdown puts a 2 TB seedbox around $15 a month — on most cloud providers that is the price of the CPU and RAM alone, before a single terabyte of storage.

So the honest rule:

  • Build it on a VPS if the library is small, you want root for something a seedbox will not run, or you already pay for the server.
  • Rent a seedbox if the library is measured in terabytes or you want ratio on private trackers. The providers we track are compared in our seedbox vs VPS breakdown and on the provider pages.

Frequently asked questions

Is running a seedbox on a VPS legal? Running a torrent client is legal. What you download and share is what matters, along with your host's acceptable-use policy — some providers ban public BitTorrent traffic regardless of content. Read it before you install.

Why not expose the web UI with HTTPS instead of an SSH tunnel? You can, behind a reverse proxy with TLS and a strong password. The tunnel is simpler and leaves nothing to misconfigure: the login page simply does not exist from the outside.

How much RAM does qBittorrent need? Around a few hundred megabytes for a modest number of torrents. Thousands of active torrents push it higher; 1 GB is a comfortable floor for the client alone.

Can I add Plex or Jellyfin to the same server? Yes, as another container pointing at the same downloads folder. Streaming adds CPU load if it has to transcode, and every stream counts against your traffic allowance.


Vultr plan figures read from vultr.com/pricing on 12 November 2026; Hetzner's 20 TB EU allowance from its cloud pricing pages on the same date. Commands written for Ubuntu 24.04 LTS and the linuxserver.io qBittorrent image.

Some links on this page are affiliate links. If you sign up through them we may earn a commission, at no extra cost to you. It never changes which providers we recommend or how we rank them.

Related tutorials