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
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
You are correct the FIREWALL_VPN_INPUT_PORT is to allow the port to be opened on the vpn side of the connection. You will add the port provided to you from Air as that variable and set the same port within qbittorrent.
You should not be adding the port 6881 anywhere, example compose below from the guide on my website.
https://paste.drfrankenstein.co.uk/?6be32ded3f56a96c#9q46W92Ah424RMoB4qM2o8UHL1CBxickoZKZgH9Nsfop
Hmm I see, I had the port in 6881 docker-compose and used it for the incoming connections in qBittorrent for 2 days or so, would that get me a notice from the ISP? I've been using network_mode: "service:gluetun" the whole time and the curl https://ipleak.net/json/ from the qBittorrent container console always delivered the ip of my vpn.
Hey, unlikely as the wan traffic should be going via the vpn. But at least you set it correctly now.
I see, thanks for the answers and your time.
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)