What a seedbox actually is
A seedbox is a server whose whole job is BitTorrent. It downloads to fast local disk over a symmetric datacenter link, then keeps seeding around the clock — long after your laptop is closed. You connect only to manage it and to pull the finished files down over an encrypted channel. Because the transfer happens on the server, torrent traffic and swarm metadata never touch your home IP, and your seed ratio no longer depends on a slow residential upload or a monthly data cap.
There is a privacy angle beyond raw speed. The peers in a swarm see the IP that is seeding; on a seedbox that is the server, not your home line. And because the host is no-KYC and paid in crypto, renting the machine doesn’t create another identity record tied to your name.
Legitimate use — and what our AUP forbids
BitTorrent is a neutral protocol. It distributes Ubuntu and Debian images, game patches, the Internet Archive’s public-domain collections, large Creative-Commons datasets, and plenty of people’s own encrypted backups. All of that is exactly what this plan is for.
What it is not for: sharing copyrighted films, music, software or books without permission. That is unlawful and it breaks our Acceptable Use Policy. We are a privacy host with a published AUP and a working abuse desk — not a “bulletproof” host — and we act on valid abuse reports. Run a seedbox for content you have the right to distribute, and none of that is your problem.
Install qBittorrent-nox
qbittorrent-nox is a headless build with a clean Web UI — a good default.
rTorrent paired with ruTorrent is the classic alternative if you prefer its
plugin ecosystem. The commands below stand up qBittorrent on a fresh Ubuntu
server. They’re illustrative; read the project’s own docs before relying on
them.
# on a fresh VPS (Ubuntu 24.04)
sudo apt update && sudo apt install -y qbittorrent-nox
# run the daemon as its own unprivileged user, never as root
sudo useradd -r -m -s /usr/sbin/nologin qbtGive it a systemd unit so it survives reboots:
sudo tee /etc/systemd/system/qbittorrent-nox.service >/dev/null <<'EOF'
[Unit]
Description=qBittorrent-nox
After=network-online.target
Wants=network-online.target
[Service]
User=qbt
# bind the Web UI to localhost only — see the next section
ExecStart=/usr/bin/qbittorrent-nox --webui-port=8080
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
sudo systemctl enable --now qbittorrent-noxRecent builds print a temporary Web UI password to the journal on first start:
sudo journalctl -u qbittorrent-nox | grep -i "temporary password"Lock down the Web UI
This is the step people skip, and it’s the one that matters. A torrent Web UI
open on a public port with the default admin login is an invitation.
First, log in and change the admin password immediately. Then don’t serve the UI
to the open internet at all. Bind it to 127.0.0.1 and reach it through an
encrypted front door — a reverse proxy that terminates HTTPS and adds its own
auth, or a private VPN tunnel to the server so the panel is never publicly
reachable. Two patterns work well: a reverse proxy such as Caddy or nginx with
basic-auth over TLS, or WireGuard-only access so the panel is reachable only
from inside your tunnel. Pick whichever fits your setup.
In qBittorrent’s own settings, also enable “IP whitelisting” for the Web UI and turn off the UPnP/NAT-PMP port forwarding option unless you know you need it. If you use a VPN for the torrent traffic itself, bind the client to that interface so a VPN drop pauses transfers instead of leaking.
Mount and size your storage
If your plan gives you a separate data volume, format it and mount it where the client writes downloads, so a full disk never takes out the root filesystem:
# format and mount a dedicated data volume (adjust the device name)
sudo mkfs.ext4 /dev/vdb
sudo mkdir -p /srv/torrents
echo '/dev/vdb /srv/torrents ext4 defaults,noatime 0 2' | sudo tee -a /etc/fstab
sudo mount -a
sudo chown -R qbt:qbt /srv/torrentsPoint qBittorrent’s default save path at /srv/torrents and pull finished files
with sftp qbt@your-server:/srv/torrents/... or your reverse proxy’s HTTPS
download route.
Sizing bandwidth and ratio
Disk decides how much you can seed at once; bandwidth decides your ratio and speed. Long-term seeding of large archives is the workload the Max plan is built for — the biggest disk and the highest transfer allowance in the lineup (the pricing page shows the current pre-launch numbers). Lighter, occasional torrenting fits a smaller plan; scale down if you don’t need the headroom.
Because the link is symmetric and always on, keeping a healthy ratio is effortless — the server seeds at full upload speed while you sleep. Set a global ratio or seeding-time goal in the client if you want it to stop automatically, and you’re done.
What this page is and isn’t
This is a guide to hosting a seedbox for content you have the right to share. It is not a piracy tool and not a workaround for our AUP. We rent you a fast, private server; what you seed on it is your responsibility.