I’ve set everything up using this guide, but qbittorrentvpn container won’t start and it’s giving me this error:
No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...
I’m using portainer and mullvad btw. Here is qbit stack:
qbittorrentvpn:
image: markusmcnugen/qbittorrentvpn
container_name: qbittorrentvpn
privileged: true
environment:
- PUID=998
- PGID=100
- WEBUI_PORT=6011
- TZ=America/New York
volumes:
- /server/Docker/Configs/QBittorrentVPN:/config
- /server/Docker/Torrents:/downloads
- /etc/timezone:/etc/timezone:ro #This is for TimeZone
network_mode: container:gluetun-mullvad
restart: unless-stopped
Here is gluetun stack:
version: "3"
services: gluetun: image: qmcgaw/gluetun container_name: gluetun-mullvadcap_add: - NET_ADMIN ports: #make sure to include these for qbittorrent to work - 6081:6881 - 6081:6881/udp - 6011:6011environment: - VPN_SERVICE_PROVIDER=mullvad - VPN_TYPE=wireguard - WIREGUARD_PRIVATE_KEY=(key from downloaded file) - WIREGUARD_ADDRESSES=(ip from downloaded file) - SERVER_CITIES=Atlanta GA #choose any available city volumes: - /server/Docker/Gluetun:/gluetun restart: unless-stopped
Not sure why qbit is looking for ovpn when I’m using wireguard.
Update: This is all on a desktop machine, I ended up ditching the docker torrent client and using the gui I already had installed on the desktop. Works perfectly so far.
You haven’t set everything up as in the guide you linked. You’re using a different image. Use the same container image as in the guide: ghcr.io/linuxserver/qbittorrent
If gluetun is handling the vpn, you don’t need a special qbittorrent image with vpn support. That’s what the error message is saying: “hey, I (the qbittorrent image with VPN support) cannot find the VPN config”.
If you use the “normal” qbittorrent image with network_mode: container:gluetun-mullvad the connection will go through gluetun and thus your vpn.
Note that you probably also want to add depends_on: gluetun-mullvad so that this container waits to start until gluetun has started.
Bittorrentvpn will likely conflict with gluetun. As noted
In gluetun -
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- “/lib/modules:/lib/modules:ro”
ports:
I had to add SYS_ADMIN or SYS_MODULE under cap_add to get it to work. I put both, and I am too superstitious to take one or the other out. I run as a regular user, not root. You may not need these modules with a root user. The 6999 port may be for the openvpn method. You may be good without it w/ wireguard
In qbittorrent
network_mode: “service:gluetun”
depends_on:
gluetun:
- condition: service_healthy
These are in the same stack. Your container:gluetun works if they are on different stacks, same network. The service_healthy mattered. My gluetun comes up and tries to register to the VPN. It fails, pauses, and then retries. The second try is always successful.
Reddit is torturing me with formatting. Sorry folks
Ah I think I did a stack with normal qbit first then found that guide, I’ll try again in a moment
depends_on: gluetun-mullvad
I think I’m getting somewhere but gluetun-mullvad is in another stack, what’s the most straightforward way of making the dependency work?
I nixed qbittorrentvpn for plain qbittorrent, but now I’m encountering a new issue. This is all being done on a desktop with gui. I already had qbittorrent desktop installed. Now when I try to open localhost 6011, it tries to do so with xdg-open, presumably to open my existing qbit desktop install. I’ve tried uninstalling and changing ports with no luck.
Flush your arp table? Flush any caches associated with the desktop qbit?
Some daemon or cache on your computer or router is persisting mapping, is my guess. After that, I am not sure where to go.
I’ll try that. As a temporary fixed I just used transmission for this docker stack, works fine