Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54577 readers

697 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

[email protected]

Gluetun/qBittorrent Port Forwarding (lemmy.dbzer0.com)

submitted 1 year ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

Hello people I recently set up a qBittorrent + Arr setup that is being run through a Gluetun container. I also got a port from AirVPN and added it as the FIREWALL_VPN_INPUT_PORTS environment variable to the docker-compose file. I am also able to see it on canyouseeme.

Gluetun is running on the port 6881 and the "Port used for incoming connections" is also 6881 in the qBittorrent settings. Should I change the incoming port to the one I got from AirVPN in the qBittorrent or is Gluetun already handling it for me?

Also should I run the Gluetun on the port I got from the AirVPN or is 6881 fine?

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

[–] [email protected] 1 points 1 year ago

The only ports you need to expose from Gluetun are the ones for the webUI for each of the containers you're running thru it. You should never expose the port for incoming connections since that would make your torrenting traffic avoid the VPN.

Your qBittorrent and *arr containers should be run with network: "service: gluetun" in your docker-compose file (assuming you're using compose)