🔴 Setup Transmission — Lightweight Torrent Client
Deploy Transmission on Ubuntu — a fast, minimal BitTorrent client with a clean web UI, watch folders, and one of the smallest memory footprints of any torrent daemon.
📦 Resources & Setup Scripts
Grab the automated bash script from GitHub to follow along with the video.
Quick Install:
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/downloads/transmission/transmission-ubuntu.sh
chmod +x transmission-ubuntu.sh
sudo bash transmission-ubuntu.shTutorial Steps
1 Download the Script
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/downloads/transmission/transmission-ubuntu.sh2 Make it Executable
chmod +x transmission-ubuntu.sh3 Run the Installer
The script installs Docker if needed, generates a random 20-character password for the admin user, and starts Transmission with config, downloads, and watch volumes under /root/docker/transmission.
sudo bash transmission-ubuntu.sh4 Access the Web UI
Open your browser and log in with username admin and the password printed at the end of the install output:
http://<your-server-ip>:9092Ports Used
| Port | Purpose |
|---|---|
| 9092 | Web UI + RPC API (container port 9091) |
| 51413 TCP/UDP | BitTorrent peer connections |
Overview
Transmission is the torrent client that ships by default on many Linux distributions and NAS systems, known for doing one thing well with very little RAM or CPU. This setup runs the lscr.io/linuxserver/transmission image with the web UI published on port 9092 (container port 9091) and peer traffic on 51413 TCP/UDP. The daemon exposes a JSON-RPC API that countless tools integrate with, three bind mounts persist your data: /config for settings and torrent state, /downloads for completed files, and /watch — a folder where any .torrent file you drop in is added automatically. Authentication is preconfigured by the script with the admin user and a randomly generated password.
Why Use It
Transmission's appeal is its footprint: the daemon idles at a fraction of the memory qBittorrent needs, which matters on a Raspberry Pi, an old NAS, or a VPS with 512 MB of RAM. Its settings.json is simple to manage with configuration tools, its RPC API is stable and universally supported (Sonarr, Radarr, and most mobile remotes speak it), and the watch-folder workflow means automation can be as simple as copying a file. If you want torrents handled reliably without tuning dozens of options, Transmission is the pragmatic choice.
When You Need It
Who Should Use It
Real Use Cases
Main Features
How to Use After Installation
Security Best Practices
Ports and Firewall Notes
The web UI and RPC API are published on host port 9092 (mapping to container port 9091) — restrict this to your LAN or VPN, and add a reverse proxy with HTTPS if remote access is needed. Port 51413 TCP/UDP carries BitTorrent peer traffic; forwarding it on your router makes the client connectable and improves speeds, though it works without forwarding at reduced performance. Verify UFW rules with ufw status after the script runs.
Backup and Maintenance
Common Mistakes
Troubleshooting
Alternatives
qBittorrent (covered in this Academy) adds a built-in search engine, RSS download rules, and finer-grained controls at the cost of more memory. Deluge offers a plugin system and daemon/thin-client split. rTorrent with Flood is a favorite on high-end seedboxes. For direct HTTP/FTP downloads rather than torrents, see our Aria2 + AriaNg tutorial, and for Usenet, SABnzbd.
When Not to Use It
If you rely on RSS-based tracker automation or a built-in torrent search, Transmission does not have them — use qBittorrent. Private tracker power users who need detailed per-tracker tuning and client whitelisting sometimes find Transmission's options too sparse. And if your workflow is Usenet-based, you need SABnzbd instead of any torrent client.
PrismaTechWork Professional Help
PrismaTechWork provides end-to-end infrastructure services — from initial deployment and security hardening to ongoing monitoring, automated backups, and dedicated support.
Frequently Asked Questions
What are the default Transmission login credentials?
The install script sets the username to admin and generates a random 20-character password, printed at the end of the setup output. If you lose it, stop the container, edit rpc-password in /config/settings.json to a new plain-text value, and start the container — Transmission hashes it automatically.
Why is the web UI on port 9092 instead of 9091?
Transmission listens on 9091 inside the container, but the script publishes it as 9092 on the host to avoid clashing with other services. Browsers and integrations should always use http://your-server:9092.
How does the watch folder work?
Any .torrent file copied into /root/docker/transmission/watch (mounted as /watch in the container) is detected and added automatically, then renamed with a .added suffix. It is the simplest way for scripts or other apps to hand torrents to Transmission without touching the API.
Transmission vs qBittorrent — which should I pick?
Pick Transmission for low-resource hardware, scriptable configuration, and simplicity. Pick qBittorrent for RSS automation rules, a built-in search engine, and finer per-torrent control. Both integrate equally well with Sonarr and Radarr, so the media-stack use case works with either.
Can I manage Transmission from my phone?
Yes. Apps such as Transmission Remote (Android) or Transmission RPC clients (iOS) connect to the RPC API on port 9092 with your admin credentials. Only do this over your LAN, a VPN like WireGuard, or an HTTPS reverse proxy — never by exposing the port directly.