Skip to Content
DocsApplicationsDownload ClientsTransmission
Transmission

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

Version Selection

By default, Transmission 3.00 (legacy) is installed. Use the --v4 flag to install a modern 4.x+ version with Qt6 support and the latest features resolved dynamically from the compiled-packages manifest. Note: Switching between legacy and modern will replace the Transmission installation for all users.

Installation

Symptoms

  • QuickBox Pro v3 installed and configured
  • User account created on the server
  • Sufficient disk space for torrent data

Resolution

  • Use QuickBox's qb command for installation
  • Automatic configuration with reverse proxy
  • Per-user installation with isolated settings

Basic Installation (Legacy)

Install Transmission for a specific user. Without --v4, version 3.00 is installed:

qb install transmission -u username

Modern Installation (4.x+)

Install the latest Transmission 4.x+ build with Qt6 support. The exact version is resolved dynamically from the compiled-packages manifest for your distro:

qb install transmission -u username --v4

CLI Commands

CommandDescription
qb install transmission -u usernameInstall Transmission 3.00 (legacy)
qb install transmission -u username --v4Install Transmission 4.x+ (modern, Qt6, latest from manifest)
qb reinstall transmission -u usernameReinstall while preserving QuickBox integration
qb update transmission -u usernameUpdate Transmission to latest stable version
qb update transmission -u username --v4Update or switch to Transmission 4.x+
qb remove transmission -u usernameRemove Transmission and clean up files
qb help transmissionDisplay 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, and transmission-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.

Version Switching

Switching between legacy and modern (via update or reinstall with --v4) will replace the Transmission installation for all users on the server. Plan accordingly if you have multiple users.

Branch Channels

QuickBox Pro uses two package channels: main (stable, default) and develop (beta, opt-in). The channel is detected automatically. When using --v4, the resolved version comes from the active channel’s packages.lst manifest.

CLI Options

-u, --usernameRequired

Target QuickBox username for install/reinstall/remove operations. Supply Admin username for version updates affecting all users.

--v4

Install or update to the latest Transmission 4.x+ build (Qt6-based, single +allmods package). Affects all users on the server.

Automatic Port Assignment

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/

QuickBox Dashboard Integration

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)

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.1 for 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:

  1. Navigate to Preferences (gear icon) → Network
  2. Verify watch directory is enabled: /home/username/torrents/transmission/watch
  3. Drop .torrent files into the watch folder—they’ll be added automatically

3. Connect to *arr Applications (Optional)

If using Sonarr, Radarr, or other *arr applications:

  1. In your *arr app, go to Settings → Download Clients → Add (+)
  2. Select Transmission from the list
  3. 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
  4. 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-start

Troubleshooting

Transmission Won’t Start

journalctl -u transmission@username -f

Check for port conflicts:

grep -i 'rpc-port' ~/.config/Transmission/settings.json
# Default: 15105

Web 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@username

Permission Issues

qb fix permissions -u username
systemctl restart transmission@username

Version Switch Issues

# If switching from v3 to v4 fails, clean reinstall
qb remove transmission -u username
qb install transmission -u username --v4

Best 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

Use Cases

Simple BitTorrent Downloads

  • Minimalist approach with sensible defaults that “just work”
  • No complex configuration needed—start downloading immediately
  • Perfect for users who want simplicity over advanced features

Automated Media Downloads

  • Connect to Sonarr, Radarr, Lidarr for automated TV, movie, and music downloads
  • Watch directory support for RSS-based automation
  • Lightweight resource usage compared to other clients

Beginner-Friendly Client

  • Ubuntu’s default BitTorrent client for a reason—easy learning curve
  • Clean web interface with intuitive controls
  • Ideal for users new to BitTorrent or seedbox management

FAQ

Without --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.
Legacy 2.x/3.x installs as separate subpackages (transmission-daemon, transmission-cli, transmission-common, transmission-gtk, transmission-qt). Modern 4.x+ installs as a single +allmods .deb that bundles all components.
Transmission uses the --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.
The main channel (default) contains stable, tested builds. The develop channel (beta) may include newer Transmission builds not yet promoted to stable. Your server's channel is detected automatically.
Yes. Transmission is a system-level binary — switching between legacy and modern (or vice versa) 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.
🎬

Media Management

Sonarr ⭐Radarr ⭐LidarrReadarr
🔍

Indexers

Prowlarr ⭐Jackett
⬇️

Other Download Clients

qBittorrentDelugerTorrent
🎨

Web Interfaces

Flood

Additional Resources

Transmission Official Website

Official documentation and downloads

Transmission GitHub Repository

Source code and issue tracking

Transmission RPC Specification

RPC API documentation for automation

Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support
Feature Previews
Community Configs
Active Discussions
Join Discord Server
SABnzbdFile Management