Skip to content

Download Clients and VPNs

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

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

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
  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

This setup uses the container maintained here: binhex/arch-qbittorrentvpn

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

Requires the following variables:

  • hmsdocker_vpn_type: openvpn
  • hmsdocker_vpn_user: Your VPN account/service account username
  • hmsdocker_vpn_pass: Your VPN account/service account password

If using OpenVPN for your VPN connection, please update or place the .ovpn file and any other required files in the directory: /opt/hms-docker/apps/qbittorrent/config/openvpn (default)

This folder will not exist until the playbook is ran or the container runs for the first time

Requires the following variables:

  • hmsdocker_vpn_type: wireguard

If using WireGuard for your VPN connection, please update or place the wg0.conf file and any other required files in the directory: /opt/hms-docker/apps/qbittorrent/config/wireguard (default)

This folder will not exist until the playbook is ran or the container runs for the first time

If you are using PIA and want to use port forwarding through the VPN, see the Container Overrides docs

This setup uses the container maintained here: binhex/arch-delugevpn

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

The default password is deluge

Requires the following variables:

  • hmsdocker_vpn_type: openvpn
  • hmsdocker_vpn_user: Your VPN account/service account username
  • hmsdocker_vpn_pass: Your VPN account/service account password

If using an OpenVPN config file for your VPN connection, please update or place the .ovpn file and any other required files in the directory: /opt/hms-docker/apps/deluge/config/openvpn (default)

This folder will not exist until the playbook is ran or the container runs for the first time

Requires the following variables:

  • hmsdocker_vpn_type: wireguard

If using WireGuard for your VPN connection, please update or place the wg0.conf file and any other required files in the directory: /opt/hms-docker/apps/deluge/config/wireguard (default)

This folder will not exist until the playbook is ran or the container runs for the first time

If you are using PIA and want to use port forwarding through the VPN, see the Container Overrides docs