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

submitted 1 year ago by whereBeWaldo@lemmy.dbzer0.com to c/piracy@lemmy.dbzer0.com

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

[-] drfrankenstein@sh.itjust.works 5 points 1 year ago* (last edited 1 year ago)

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

[-] whereBeWaldo@lemmy.dbzer0.com 1 points 1 year ago* (last edited 1 year ago)

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.