
Transmission
Lightweight BitTorrent client that “just works”
Transmission is a fast, easy-to-use BitTorrent client designed with sensible defaults that work out of the box. Ubuntu chose Transmission as its default BitTorrent client largely due to its easy learning curve. QuickBox Pro offers Transmission in both legacy (2.x/3.x) and modern (4.x+, Qt6-based) builds from the compiled-packages manifest, with per-user systemd services, nginx reverse proxy, and pre-configured RPC access.
Just Works
Sensible defaults with minimal configuration needed out of the box
Web Interface
Clean, responsive web UI via nginx reverse proxy with RPC authentication
Watch Directories
Auto-add torrents from watch folder for automated workflows
Dynamic Versions
Available versions resolved from the compiled-packages manifest with dual packaging support
RPC Whitelist
Secure RPC access with authentication and IP whitelist (127.0.0.1)
Peer Blocklists
Support for bad peer blocklists to enhance privacy and security
Installation
Install from the Dashboard
Open App Dashboard → Package Management (/dashboard?mode=packages), find Transmission in the catalog (browse Download Clients or search), and click Install. The available builds are resolved from the compiled-packages catalog for your distro — both the legacy 3.x series and the modern 4.x+ (Qt6) series appear there. The dashboard streams the install log live and Transmission appears in your Application Control panel when it finishes. Reinstall, Update, and Remove are available from the same panel.
What you see and can manage is gated by your account: admins manage any user’s apps; regular users manage their own. For the full package flow see App Management.
Transmission installs as a system-wide binary, so switching between the legacy 3.x and modern 4.x+ series replaces the installation for all users on the server. User configurations and torrent data are preserved, but plan the switch with all users in mind.
Install from the CLI (automation)
The CLI runs the same install and is suited to automation and scripting. By default it installs the legacy 3.00 build; add --v4 to install or switch to the modern 4.x+ (Qt6) series:
qb install transmission -u username # legacy 3.00
qb install transmission -u username --v4 # modern 4.x+CLI Commands
| Command | Description |
|---|---|
qb install transmission -u username | Install Transmission 3.00 (legacy) |
qb install transmission -u username --v4 | Install Transmission 4.x+ (modern, Qt6, latest from manifest) |
qb reinstall transmission -u username | Reinstall while preserving QuickBox integration |
qb update transmission -u username | Update Transmission to latest stable version |
qb update transmission -u username --v4 | Update or switch to Transmission 4.x+ |
qb remove transmission -u username | Remove Transmission and clean up files |
qb help transmission | Display comprehensive help information |
Dual Packaging Model
Transmission uses different packaging depending on the version series:
- Legacy 2.x/3.x — installed as separate subpackages:
transmission-daemon,transmission-cli,transmission-common,transmission-gtk, andtransmission-qt. All are held at the installed version to prevent accidental upgrades. - Modern 4.x+ — installed as a single
+allmods.deb that bundles all components. Qt6 dependencies are resolved and installed from the compiled-packages manifest alongside the main package.
This means --v4 does not just change the version number; it changes the entire packaging structure.
CLI Options
-u, --usernameRequiredTarget QuickBox username for install/reinstall/remove operations. Supply Admin username for version updates affecting all users.
--v4Install or update to the latest Transmission 4.x+ build (Qt6-based, single +allmods package). Affects all users on the server.
QuickBox automatically assigns ports:
- RPC port: Starting at
15105(auto-incremented per user) - Peer port: Random from
49152-65535
Find your assigned RPC port in the QuickBox dashboard or in ~/.config/Transmission/settings.json.
Accessing Transmission
After installation, access Transmission at:
https://your-server-ip/transmission/Transmission is automatically integrated into your QuickBox dashboard. Find it in the Service Control panel with port and status information. Click the LAUNCH icon to open the web interface.
Login credentials:
- Username: Your QuickBox username
- Password: Your QuickBox password (RPC authentication)
Browser Download Index
In addition to the Transmission Web UI, QuickBox installs a per-user browser file index that lists the contents of your Transmission download directory in a dark-themed fancyindex view. Useful for quickly grabbing a single finished file without loading the torrent client.
https://your-server-ip/username.transmission.downloadsThe nginx template at /etc/nginx/software/username.dlindex.conf exposes /home/username/torrents/transmission through the shared fancyindex snippet. Access is protected by auth_basic against /etc/htpasswd.d/htpasswd.username, which is the same credential file used for other QuickBox user endpoints.
- The listing path matches the Transmission download root, including the
downloads/andwatch/subfolders. - The index is stitched together per user: if you also have qBittorrent, rTorrent, Deluge, NZBGet, or SABnzbd installed, their completed-download locations are appended into the same
username.dlindex.confso each client gets its own URL. It is one shared browse-index config covering all of that user’s download clients. - The feature has no service of its own — it is pure nginx. If the page fails to load — returns a 502 or 404, shows blank, or errors — while the rest of the dashboard works normally, the per-user config is broken or missing. Rebuild it with
qb fix dlindex -u username(one user) orqb fix dlindex(all users). See the Download Clients overview and theqb fixreference.
Initial Configuration
1. Web Interface Setup
On first access, the web interface is pre-configured:
- RPC authentication: Enabled with your QuickBox credentials
- RPC whitelist: Restricted to
127.0.0.1for security - Download directory:
/home/username/torrents/transmission/downloads - Watch directory:
/home/username/torrents/transmission/watch
No additional setup required—Transmission is ready to use immediately.
2. Configure Watch Directory (Optional)
Enable automated torrent loading:
- Navigate to Preferences (gear icon) → Network
- Verify watch directory is enabled:
/home/username/torrents/transmission/watch - Drop
.torrentfiles into the watch folder—they’ll be added automatically
3. Connect to *arr Applications (Optional)
If using Sonarr, Radarr, or other *arr applications:
- In your
*arrapp, go to Settings → Download Clients → Add (+) - Select Transmission from the list
- Enter connection details:
- Host:
127.0.0.1 - Port: Your RPC port (check
~/.config/Transmission/settings.json→rpc-port) - URL Path:
/transmission/ - Username: Your QuickBox username
- Password: Your QuickBox password
- Host:
- Test and save
Service Management
Transmission runs as a systemd service for reliability and automatic startup.
systemctl status transmission@username # Check status
systemctl restart transmission@username # Restart service
journalctl -u transmission@username -f # View live logs
systemctl enable transmission@username # Start on boot
systemctl disable transmission@username # Prevent auto-startTroubleshooting
Transmission Won’t Start
journalctl -u transmission@username -fCheck for port conflicts:
grep -i 'rpc-port' ~/.config/Transmission/settings.json
# Default: 15105Web Interface Not Accessible
Symptoms
- Cannot access Transmission web interface
- 403 Forbidden or authentication errors
- RPC connection refused from
`*arr`apps - nginx proxy not working
Resolution
- Verify service is running: systemctl status transmission@username
- Check RPC whitelist in settings.json includes 127.0.0.1
- Ensure nginx configuration exists: /etc/nginx/conf.d/username.transmission.conf
- Reload nginx: systemctl reload nginx
Configuration File Corruption
# Stop service
systemctl stop transmission@username
# Backup current configuration
cp ~/.config/Transmission/settings.json ~/.config/Transmission/settings.json.backup
# Edit or regenerate configuration
nano ~/.config/Transmission/settings.json
# Restart service
systemctl start transmission@usernamePermission Issues
qb fix permissions -u username
systemctl restart transmission@usernameVersion Switch Issues
# If switching from v3 to v4 fails, clean reinstall
qb remove transmission -u username
qb install transmission -u username --v4Best Practices
Do
- Use qb update transmission to keep Transmission updated safely
- Monitor service health with systemctl status transmission@username
- Use the watch folder for automated torrent loading
- Configure speed limits during peak hours if needed
- Set appropriate peer limits based on your connection
- Enable blocklists for enhanced privacy and security
- Create categories for different
`*arr`applications - Regularly check disk space—torrents can grow quickly
Don't
- Don't install Transmission from system package managers—use QuickBox only
- Don't manually edit systemd or nginx configs without backing up first
- Don't expose the RPC port directly to the internet without nginx in front
- Don't edit settings.json while service is running—stop it first
- Don't mix v3 and v4 installations—choose one for all users
- Don't delete .config/Transmission directory manually—use qb remove
- Don't ignore RPC whitelist—keep it restricted to 127.0.0.1
- Don't use Transmission for high-performance seeding—consider rTorrent instead
FAQ
--v4, Transmission 3.00 is installed. With --v4, the CLI resolves the latest available 4.x+ version from the packages.lst manifest in the QuickBox/compiled-packages repository, filtered by your distro codename.transmission-daemon, transmission-cli, transmission-common, transmission-gtk, transmission-qt). Modern 4.x+ installs as a single +allmods .deb that bundles all components.--v4 flag to choose between legacy and modern builds. The exact modern version is the latest available in the manifest for your distro; there is no -o version flag for Transmission.Related Applications
Indexers
Other Download Clients
Web Interfaces
Additional Resources
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.