Download Clients
Download client settings are configured in the [torrents] section of your config.toml file. MediaManager supports both qBittorrent and SABnzbd as download clients.
qBittorrent Settings ([torrents.qbittorrent])
[torrents.qbittorrent])qBittorrent is a popular BitTorrent client that MediaManager can integrate with for downloading torrents.
enabledSet totrueto enable qBittorrent integration. Default isfalse.hostHostname or IP of the qBittorrent server. Include the protocol (http/https).portPort of the qBittorrent Web UI/API. Default is8080.usernameUsername for qBittorrent Web UI authentication. Default isadmin.passwordPassword for qBittorrent Web UI authentication. Default isadmin.
Transmission Settings ([torrents.transmission])
[torrents.transmission])!!! info The downloads path in Transmission and MediaManager must be the same, i.e. the path /data/torrents must link to the same volume for both containers.
Transmission is a BitTorrent client that MediaManager can integrate with for downloading torrents.
enabledSet totrueto enable Transmission integration. Default isfalse.usernameUsername for Transmission RPC authentication.passwordPassword for Transmission RPC authentication.https_enabledSet totrueif your Transmission RPC endpoint uses HTTPS. Default istrue.hostHostname or IP of the Transmission server (without protocol).portPort of the Transmission RPC endpoint. Default is9091.pathRPC request path target. Usually/transmission/rpc.
SABnzbd Settings ([torrents.sabnzbd])
[torrents.sabnzbd])SABnzbd is a Usenet newsreader that MediaManager can integrate with for downloading NZB files.
enabledSet totrueto enable SABnzbd integration. Default isfalse.hostHostname or IP of the SABnzbd server, it needs to includehttp(s)://.portPort of the SABnzbd API. Default is8080.api_keyAPI key for SABnzbd. You can find this in SABnzbd's configuration under "General" → "API Key".base_pathAPI base path for SABnzbd. It usually ends with/api, the default is/api.
Example Configuration
Here's a complete example of the download clients section in your config.toml:
Docker Compose Integration
When using Docker Compose, make sure your download clients are accessible from the MediaManager backend:
!!! warning You should enable only one BitTorrent and only one Usenet Download Client at any time.
!!! info Make sure the download directories in your download clients are accessible to MediaManager for proper file management and organization.
Last updated