Skip to main content


Please make yourself aware of the Fair Usage Policy. Directly pointing any cloud storage directory using Rclone will create extreme strain on your slot's disk and WILL cause a 24-hour ban on accessing your cloud storage repeatedly. It is YOUR responsibility to ensure usage is within acceptable limits. Ignorance is not an excuse.

If you are on an HDD plan, you should be mindful not to have multiple simultaneous downloads active as it will cause high disk IO utilization, and negatively affect your disk neighbors. There is no set limit on how many active downloads you can have, though depending on the download speeds, we recommend 1-3 at the most. To monitor the disk IO utilization, see this link:

Transmission is a BitTorrent client which features a variety of user interfaces written in C/Objective-C. It is:

Open Source and volunteer-based

Easy to use Lean and low on resources

Written in Objective C

  • Powerful client with several features:
    • Encryption
    • Web interface
    • Peer exchange
    • Magnet link support
    • DHT, µTP, UPnP, and NAT-PMP port forwarding
    • Webseed support
    • Watch directories
    • Tracker editing
    • Global and per-torrent speed limits

For more information, you can view the complete list of features here.

Initial Setup

Transmission is already configured and tuned out of the box. Just install the client, enter your desired password, and press Connect to log in to your Transmission Web Interface.

Default File Paths

  • Default Downloads Folder: ~/files
  • Transmissions's config folder: ~/.config/transmission-daemon

Using Transmission Remote GUI

Transmission Remote GUI is a feature-rich cross-platform front-end to control the Transmission daemon via its RPC protocol remotely. It is faster and has more functionality than the built-in Transmission web interface.


  • Native application for Windows, Linux, and macOS
  • uTorrent-like interface
  • Select files to download
  • Choose files priority
  • View details about connected peers
  • Full information about each torrent
  • Per torrent options

You can visit the repository here:


Install the program using the links below. Listed are the direct links to the latest version of the program.


Windows 64-bit:
Windows 32-bit:
macOS (x86):

For Windows, you may have to install an additional program; otherwise, upon connection, you will be greeted with the following error message.

Unable to load OpenSSL library files: ssleay32.dll and libeay32.dll

Connecting and Using Transmission Remote GUI

Connecting to your Transmission is a relatively simple process.

Creating a New Connection

Upon your first launch, you should be greeted with a box to input your details, which are as follows:

Remote host: (servername refers to your server eg, myles)
Port: 443
Use SSL: Ticked
Authentication required: Ticked
Always Auto-Connect: Ticked
Username: Found in your Control Panel
Password: Found in your Control Panel
RPC path: /transmission/rpc/web

If you had to backtrack because of SSL Error, you could also go to Manage Connections in the top left corner

If you receive a popup regarding Geo IP, select yes, as this will allow you to see the Peers Country’s location.

Add your first .torrent file

Add a .torrent file to transmission via the remote first click Torrent in the top left of the small GUI, add a torrent. This will open your file explorer for you to add your .torrent file

Add your first Magnet Link


Enable Public Torrent Seeding (Optional)

  • Public torrents are stopped after download by default to avoid HDD IO resource abuse and inadvertent usage of upload traffic. You can easily enable public torrent seeding with the instructions given below.
  • Login to your service via SSH. How to connect to your slot via SSH
  • Execute the following SSH command:
app-transmission restart --remove-pubscript
  • That's it.
  • Note that changing the password of the torrent client or re-installing it will disable public torrent seeding again.

Torrent Queueing

If you have an service with HDD instead of NVME, you need to be mindful of your disk neighbors and not hammer the disk with high IO utilization. See this guide for more information on how to check your disk IO utilization.

One way to mitigate this is to limit the amount of active downloads in your torrent client. Below you will find instructions on how to do this for Transmission.

  • Connect to your service via SSH
  • Once connected, execute the following command: app-transmission stop
  • Then, execute: nano ~/.config/transmission-daemon/settings.json
  • Make sure download-queue-enabled is set to true, and set download-queue-size to the desired value.
    "download-queue-enabled": true,
    "download-queue-size": 2,
  • Once you have edited the values, press CTRL+X, then Y and ENTER to save and exit.
  • Execute app-transmission restart to reload and apply the config file.

Auto Unpack Torrents

To automatically unpack multifile .rar torrents, you can create a script that executes upon torrent download completion. Follow the below instructions to create and enable the script for Transmission.

  • Begin by creating a scripts directory and the script itself
mkdir -p ~/scripts && touch
  • Next, open the script in the nano editor
nano ~/scripts/
  • Paste the following into the script:
    • Make sure to replace your-user-name with your specific username from the UCP

echo Extracting $SRC_DIR >> $LOG_FILE

unrar e *.rar >> $LOG_FILE
  • Save and exit the nano editor with CTRL+x and y, press ENTER to confirm.
  • Make the script executable with the following command:
chmod +x ~/scripts/
  • Next, make sure to stop Transmission from the UCP or by executing the following command:
app-transmission stop
  • Once Transmission has been stopped, you need to configure Transmission to execute the script at torrent download completion. Open the Transmission settings file in the nano editor:
nano ~/.config/transmission-daemon/settings.json
  • Ensure you have these settings:
    • Make sure to replace your-user-name with your specific username from the UCP
    "script-torrent-done-enabled": true,
    "script-torrent-done-filename": "/home/your-user-name/scripts/",
  • Save and exit the nano editor with CTRL+x and y, press ENTER to confirm.
  • Restart Transmission from the UCP or by executing the following command:
app-transmission restart
  • Download a new torrent that includes a multifile .rar archive
  • Check the log to see if it worked:
tail ~/scripts/transmission_unrar.log

Upgrade Transmission v3 to v4

Please note, downgrading of Transmission can be a bit buggy and it should be avoided.

In this section, we will show you how to successfully upgrade your Transmission instance from v3 to v4. Before proceeding with the upgrade, we recommend taking a backup of your Transmission config directory and torrent session state.

  • First, stop Transmission from the Apps tab on the UCP.
  • Connect to your service via SSH, and execute the following command:
cp -r ~/.config/transmission-daemon ~/.config/transmission-daemon.bak
  • Next, go back to the UCP and uninstall Transmission. Make sure to let at least one minute pass after Transmission has been uninstalled.
  • Then, while still on the UCP, go to the Installers tab and re-install Transmission while choosing version v4.
    • DO NOT click the Cleanup button, as that will wipe your Transmission config directory and torrent session state. Even though we have previously backed it up, we want to avoid doing this.
  • Once the installation has been completed, you can proceed with accessing the Transmission Web UI. If successful, your Transmission configuration and torrent session state will be preserved.

Restore Backup

If the Transmission configuration and torrent session state was not successfully preserved after the upgrade. It can be manually restored from the backup that was made pre-upgrade.

  • First, stop Transmission from the Apps tab on the UCP.
  • Connect to your service via SSH, and execute the following command:
rm -rf ~/.config/transmission-daemon && cp -r ~/.config/transmission-daemon.bak ~/.config/transmission-daemon
  • Next, restart Transmission by executing app-transmission restart, or go back to the UCP and restart Transmission from the Apps tab.
  • Access your Transmission Web UI to confirm the backup restoration was successful.