Skip to main content

Transmission

This setup uses the container maintained here: haugene/docker-transmission-openvpn

Settings mentioned below should already exist in your inventory/group_vars/all/vpn.yml or inventory/group_vars/all/transmission.yml file

OpenVPN​

Requires the following variables:

  • hmsdocker_vpn_provider: see the official docs page
  • hmsdocker_vpn_user: Your VPN account/service account username
  • hmsdocker_vpn_pass: Your VPN account/service account password

Using a different VPN location or type​

For supported providers, you can change the server location and/or type.

  1. Make sure hmsdocker_vpn_provider is set to your correct provider

    a. You can find supported providers at the official docs page

  2. Find your VPN providers folder in this github repo

  3. Find the correct VPN config you want to use, and use this as the value for transmission_ovpn_config_file, and remove the .ovpn from the end

For example, if you wanted to use the US Chicago server for mullvad:

hmsdocker_vpn_provider: MULLVAD
...
transmission_ovpn_config_file: us_chi

Custom Provider​

Using a local OpenVPN config file​

  1. Change hmsdocker_vpn_provider to custom

  2. Change transmission_ovpn_config_file to the .ovpn file name, and remove the .ovpn from the end

  3. Change transmission_ovpn_config_local_dir to the folder path where the above file is stored

    a. If needed by your provider/server, make sure certificate files and any others are also in the same folder

For example, if you had a custom file named test-vpn.ovpn located in /opt/hms-docker/vpn_configs (this folder does not exist by default, just an example):

transmission_ovpn_config_file: test-vpn
transmission_ovpn_config_local_dir: /opt/hms-docker/vpn_configs

Error Pages​

The Error Pages container will not work with Transmission, probably due to there already being a proxy in place for the container and the first POST to /transmission/rpc results in a 409, so it is not enabled for the Transmission or Transmission Proxy container.