Selfhosted

39257 readers

239 users here now

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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Transmission (BT) through a proxy (lemmy.cat)

submitted 1 year ago by retiolus@lemmy.cat to c/selfhosted@lemmy.world

5 comments fedilink hide all child comments

Hello, for my home installation, I'm using a Raspberry Pi with YunoHost installed on it. My server is exposed through a Neutrinet VPN, but I would like to use another VPN, for example Mullvad VPN, for downloads made with Transmission, and only for that, is it possible?

I'm afraid that by installing Mullvad VPN it will take over from the other VPNs, whereas I just want it to be used as a proxy by Transmission.

top 5 comments

sorted by: hot top controversial new old

[–] Pissio@feddit.it 2 points 1 year ago

I’m using this one: https://hub.docker.com/r/haugene/transmission-openvpn

[–] crunchymunchytoast@lemmy.world 1 points 1 year ago

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.

[–] Reliant1087@lemmy.world 0 points 1 year ago (1 children)

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.

[–] Garthski@lemmy.world 0 points 1 year ago (1 children)

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

[–] Reliant1087@lemmy.world 1 points 1 year ago

I have exactly the same setup 😀