I’m using this one: https://hub.docker.com/r/haugene/transmission-openvpn
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Save yourself my troubles and go with this suggestion. I’m using this with a few different OpenVPN service providers and it works wonderfully.
Initially I had tried gluetun + transmission with gluetun acting as a socks5 proxy for the transmission instance but the shadowsocks impl it uses won’t support socks5 from any of the torrent clients I tested with.
Hi, thanks all for your suggestions, but I don't use docker and I don't want to use docker. I don't like the "container" aspect of it.
I think your options are mainly virtualization or something like this
Virtualization is definitely easiest though; there's a transmission docker image out there that's preconfigured for a ton of VPN providers, including mullvad. It can be touchy to get working but is amazing when it does work.
I didn't know it was possible to do split tunnelling with the Mullvad cli! I'll have a look and give my feedback, thanks!
Edit: Oh, it's using OpenVPN of course
There is a docker container which has transmission and openVPN. The other option is to use any VPN container such as gluetun and route transmission container's network through that using docker network mode.
This is what I do but with qbittorrent and ProtonVPN. Just put the port details in the gluetun section and in the qbittorrent section put in network_mode: "service:gluetun". Works just fine so far for me.
https://github.com/qdm12/gluetun/wiki/Connect-a-container-to-gluetun
***
version: "2.1"
services:
gluetun:
image: qmcgaw/gluetun
container_name: gluetun
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun:/dev/net/tun
network_mode: bridge
ports:
- 8081:8000/tcp # http control
- 8888:8888/tcp # HTTP proxy
- 8080:8080/tcp # qBittorrent
- 9117:9117/tcp # Jackett
volumes:
- /docker/gluetun:/gluetun
environment:
- VPN_SERVICE_PROVIDER=protonvpn
- TZ=Europe/London
- SERVER_COUNTRIES=Netherlands
- OPENVPN_USER=USERNAME
- OPENVPN_PASSWORD=PASSWORD
- HTTPPROXY=on
- HTTPPROXY_STEALTH=on
- HTTPPROXY_USER=username
- HTTPPROXY_PASSWORD=password
restart: always
qbittorrent:
image: ghcr.io/linuxserver/qbittorrent
container_name: qbittorrent
network_mode: "service:gluetun"
environment:
- PUID=1000
- PGID=100
- TZ=Europe/London
- WEBUI_PORT=8080
- DOCKER_MODS=arafatamim/linuxserver-io-mod-vuetorrent
volumes:
- /docker/qbittorrent:/config
- /srv/mergerfs/downloads/torrents:/downloads
restart: always
I have exactly the same setup 😀