Gluetun with Proton VPN with qBittorrent with Docker #2686
Unanswered
DancingPotatoes
asked this question in
Q&A
Replies: 2 comments 27 replies
-
|
Here's a docker-compose.yml that's 90% of the way there. Look to update all the variables ( For Gluetun will write the port you receive from protonvpn to a file and the In qbittorrent, make sure you check |
Beta Was this translation helpful? Give feedback.
27 replies
-
|
@dutchcodes Have you solved it? If still needed I can post my compose, but it's nothing extra. Check your gluetun logs for lines related to the port forwarding, usually at the end. |
Beta Was this translation helpful? Give feedback.
-
I can't speak for @dutchcodes, but it would help me if you would post your compose. 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@xeno391-sys this is what I'm running currently. It works without issue. This is evolved from what I started the thread with. Setting a protonvpn host was the key to making it work reliably |
Beta Was this translation helpful? Give feedback.
-
Here is what I am using, without the forward manager. It works with wireguard as well. services:
gluetun:
image: qmcgaw/gluetun
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun:/dev/net/tun
restart: unless-stopped
ports:
- 8085:8085 # qBittorrent WebUI
volumes:
- /gluetun/data:/gluetun
environment:
- VPN_SERVICE_PROVIDER=protonvpn
- OPENVPN_USER=userkey+pmp # +pmp is needed to enable port forwarding
- OPENVPN_PASSWORD=pwd
- SERVER_COUNTRIES=...
- VPN_PORT_FORWARDING=on
- PORT_FORWARD_ONLY=on
- VPN_PORT_FORWARDING_UP_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":{{PORTS}}}" http://127.0.0.1:8085/api/v2/app/setPreferences 2>&1'
qbittorrent:
image: lscr.io/linuxserver/qbittorrent
container_name: qbittorrent
network_mode: "service:gluetun"
environment:
- WEBUI_PORT=8085
- PUID=0
- PGID=0
volumes:
- /qbittorrent/data:/config
depends_on:
- gluetun
restart: unless-stoppedAnd as I said in the qBittorrent settings you have to allow local access without authentication. This setup works fine for me, on restarts I get a new IP, and the port is automatically set in the torrenting client. And doing an external port forwarding check shows the port is open. However one issue still remains, seeding barely works with this setup. I get 30 MB/s downloads just fine, but I can not seed, which is a big issue for my private linux iso trackers. I have not found a solution for this yet. |
Beta Was this translation helpful? Give feedback.
-
|
hello i keep having issues with proton vpn and glueton working and i belive from the logs that the vpn conencts but then it can't ping 1.1.1.1 so it then trys again here are the 2 docker.yml files i gave tried |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, total beginner here.
I'm trying to set up ProtonVPN, Gluetun, and qBittorrent with a properly forwarded port, but I can't figure it out. Since Proton assigns a random port, is there a compose file or guide that explains how to set this up?
I found some guides, but they seem outdated, and I'm not sure how to adapt them to the latest setup.
Also, as a side question—do Prowlarr, Sonarr, and Radarr need to run through Gluetun as well, or do they just communicate with qBittorrent? I'm a bit confused about how this works.
Any help would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions