Run Transmission torrent downloads inside a Docker container with a built-in kill-switch that stops traffic if the VPN disconnects.
Use a preconfigured VPN provider profile to route torrent traffic through your preferred VPN without managing OpenVPN config files manually.
Access the Transmission web interface from other devices on your home network while keeping all download traffic tunneled through VPN.
Deploy a self-hosted, VPN-protected torrent setup on a home server or NAS using Docker Compose.
Requires a VPN subscription with OpenVPN credentials and Docker installed, VPN provider must support OpenVPN protocol.
This repository provides a Docker container image that combines two pieces of software: Transmission, a torrent client, and OpenVPN, a tool for connecting to a VPN (virtual private network). The key behavior is that Transmission is only allowed to run when the VPN tunnel is active. If the VPN connection drops, torrent traffic stops, which is sometimes called a kill-switch behavior. Getting started requires a VPN subscription with a provider that issues OpenVPN credentials. You pass your provider name, the server or region you want to connect through, your username, and your password as environment variables when starting the container. The container takes care of establishing the VPN connection and starting Transmission behind it. Once running, the Transmission web interface is accessible on port 9091 in your browser, where you can add and manage torrents. The container has built-in configuration profiles for many popular VPN providers, so you do not have to supply custom OpenVPN config files manually for those providers. The README shows example startup commands for Docker run, Podman, and Docker Compose, all using Private Internet Access as the example provider. You map a local storage folder into the container where downloaded files will be saved, and optionally a config folder for persistent settings. A LOCAL_NETWORK variable lets you specify your home network range so that devices on your network can still reach the Transmission web interface even when VPN routing is active. The project is open-source and community-maintained. Versioned releases follow semantic versioning, with an edge tag tracking the latest code. The documentation is hosted separately on GitHub Pages rather than in the README itself.
← haugene on gitmyhub — every repo by this author, as a profile.
Verify against the repo before relying on details.