Selfhosted

43015 readers

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

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!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

[Help Requested] Port Forwarding w/ Qbittorrent & Gluetun Docker Compose? (leminal.space)

submitted 3 weeks ago* (last edited 3 weeks ago) by fenndev@leminal.space to c/selfhosted@lemmy.world

8 comments fedilink hide all child comments

I'm trying to get Qbittorrent set up within Docker on my home server and want to configure port forwarding through my VPN for all of those Linux ISOs. Ideally, I also want to get a pipeline going with the *arr stack. I've heard the easiest way to do this is with Gluetun but I can't for the life of me figure it out or know how to test it. Anyone been through something similar?

Here is my current Docker Compose for reference:


services:
  gluetun:
    image: qmcgaw/gluetun:latest
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_SERVICE_PROVIDER=airvpn
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY="[redacted]"
      - WIREGUARD_PRESHARED_KEY="[redacted]
      - WIREGUARD_ADDRESSES=10.131.184.14/32
      - FIREWALL_VPN_INPUT_PORTS=8069
      - SERVER_COUNTRIES=United States
    devices:
      - /dev/net/tun:/dev/net/tun
    volumes:
      - /home/fenndev/.config/gluetun:/config
    ports:
      - 9091:9091  # WebUI
     - 6881:6881
      - 6881:6881/udp
    restart: unless-stopped

qbit:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbit
    network_mode: "service:gluetun"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Los_Angeles  # Timezone set to Los A>
      - WEBUI_PORT=9091  # Qbittorrent webUI port
    volumes:
      - /home/fenndev/.config/qbit:/config  # Configura>
      - /home/fenndev/torrents:/downloads  # Torrent da>
    depends_on:
      glueten:
        condition: service_healthy

you are viewing a single comment's thread
view the rest of the comments

[–] Selfhoster1728@infosec.pub 4 points 3 weeks ago (4 children)

To enable port forwarding with gluetun see the port forwarding section in the gluetun wiki on their github page. It's pretty clear what you need to do there.

For port forwarding with qbit, gluetun's v3.40.0 release introduced an environment variable that allows the running of a script whenever the VPN changes port (see PR https://github.com/qdm12/gluetun/pull/2399). If you take a look at the PR some people shared commands to put under the env variable VPN_PORT_FORWARDING_UP_COMMAND.

So all you need to do is put that new environment variable in the environment section, take one of the example commands that uses the qbitorrent API to change the port when needed, and it should be all.

To test if port forwarding works qbittorrent will display a little green planet in the bottom bar, and if port forwarding is not working, a fire (to say it's firewalled).

[–] HotChickenFeet@sopuli.xyz 2 points 3 weeks ago (1 children)

allows the running of a script whenever the VPN changes port (see PR https://github.com/qdm12/gluetun/pull/2399).

That's an unknown, but welcome change. My experience for protonvpn was cludgy because you effectively had to run another service to spin and update qbittorrent's port whenever it changed. Happy to see some form of baked in support for it now.

[–] Selfhoster1728@infosec.pub 1 points 3 weeks ago

I was having a lot of trouble keeping port forwarding stable before this change with protonvpn too. Probably the best change I've seen with gluetun so far!

load more comments (2 replies)