Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Destroy the container, alter the docker run command to incorporate it and run it again.Sorry how do I edit it exactly? It's already added in docker and I can only edit the volume, port and environment settings.
That's simple... relocate the port entries from the qbittorrent container to the gluetun container. Using docker-compose, it looks like this:How do I put my existing linuxserver-qbittorrent container through it?
version: "3"
services:
gluetun:
image: qmcgaw/gluetun
container_name: gluetun
hostname: gluetun
cap_add:
- NET_ADMIN
ports:
- 9117:9117 # jackett
- 8080:8080 # qbt web interface
- 6881:6881/tcp # qbt
- 6881:6881/udp # qbt
environment:
- VPN_SERVICE_PROVIDER=custom
- VPN_TYPE=wireguard
docker run -d --rm --cap-add=NET_ADMIN -e VPN_SERVICE_PROVIDER=surfshark \
-p 8080:8080 \
-p 6881:6881/tcp \
-p 6881:6881/udp \
-e VPN_TYPE=wireguard \
-e WIREGUARD_PRIVATE_KEY=<privatekey> \
-e WIREGUARD_ADDRESSES="10.14.0.2/16" \
-e SERVER_COUNTRIES=Netherlands qmcgaw/gluetun
curl ipconfig.io
Thats half of the story, you might confuse the OP. Also, compose is not something that he is familiar with.That's simple... relocate the port entries from the qbittorrent container to the gluetun container. Using docker-compose, it looks like this:
So in your case (adjust using the qbt ports you chose for your qbt container)...Code:version: "3" services: gluetun: image: qmcgaw/gluetun container_name: gluetun hostname: gluetun cap_add: - NET_ADMIN ports: - 9117:9117 # jackett - 8080:8080 # qbt web interface - 6881:6881/tcp # qbt - 6881:6881/udp # qbt environment: - VPN_SERVICE_PROVIDER=custom - VPN_TYPE=wireguard
Code:docker run -d --rm --cap-add=NET_ADMIN -e VPN_SERVICE_PROVIDER=surfshark \ -p 8080:8080\ -p 6881:6881/tcp\ -p 6881:6881/udp\ -e VPN_TYPE=wireguard \ -e WIREGUARD_PRIVATE_KEY=<privatekey> \ -e WIREGUARD_ADDRESSES="10.14.0.2/16" \ -e SERVER_COUNTRIES=Netherlands qmcgaw/gluetun
Once this is running, SSH into the qbt container and issue this command…
curl ipconfig.io
It will return the IP address that qbt is using. If done correctly, that will be your VPN IP.
For security sake, in qbt's advanced settings, set your network adaptor to use "tun".
The docker command is also in that post. This cannot be done from Synology's docker GUI AFAIK, as "cap add" is unsupported (Yes?).Thats half of the story, you might confuse the OP
Correct but there is no torrent client side of things just the vpn side and that is not enough in a separated scenario that’s what I meantThe docker command is also in that post. This cannot be done from Synology's docker GUI AFAIK.
Well... honestly, you have confused me. You must add the client (qbt) ports to the gluetun container for this to work.Correct but there is no torrent client side of things just the vpn side and that is not enough in a separated scenario that’s what I meant
network_mode: "container:gluetun"
docker run -d \
--name=linuxserver-qbittorrent \
-e PUID=1027 \
-e PGID=100 \
-e TZ=Europe/Amsterdam \
-e WEBUI_PORT=8080 \
-p 8080:8080 \
-p 6881:6881 \
-p 6881:6881/udp \
-v /volume1/docker/qbittorrent:/config \
-v /video/downloads:/video/downloads \
--restart unless-stopped \
--network=gluetun-wireguard:gluetun
lscr.io/linuxserver/qbittorrent:latest
Since I brought up the gluetun approach, I felt obligated to follow-up when I saw this thread take a turn in that direction. I'll not interfere further... I'll leave this to @Rusty , unless I'm pinged here.Should I run this code in putty as root?
As Telos said, you will need to make changes but in this case to both containers, vpn one and qbit.I'm now a bit confused indeed
Should I run this code in putty as root? (after removing the existing container)
Or should something also be changed in the gluetun-wireguard container?
Code:docker run -d \ --name=linuxserver-qbittorrent \ -e PUID=1027 \ -e PGID=100 \ -e TZ=Europe/Amsterdam \ -e WEBUI_PORT=8080 \ -p 8080:8080 \ -p 6881:6881 \ -p 6881:6881/udp \ -v /volume1/docker/qbittorrent:/config \ -v /video/downloads:/video/downloads \ --restart unless-stopped \ --network=gluetun-wireguard:gluetun lscr.io/linuxserver/qbittorrent:latest
-p 8080:8080 \
-p 6881:6881 \
-p 6881:6881/udp \
--network=container:<name of your container>
. So --network=container
are system parameters, leave those and just correct for the name.-p 8080:8080 \
-p 6881:6881 \
-p 6881:6881/udp \
Correct. --network=container:nameofyourcontainerAllright so do i need to addCode:--network=container:gluetun
docker run -d \
--name=linuxserver-qbittorrent \
-e PUID=1027 \
-e PGID=100 \
-e TZ=Europe/Amsterdam \
-e WEBUI_PORT=8080 \
-v /volume1/docker/qbittorrent:/config \
-v /volume1/video/downloads:/video/downloads \
--restart unless-stopped \
--network=container:gluetun-wireguard \
lscr.io/linuxserver/qbittorrent:latest
# Wireguard
docker run -d --cap-add=NET_ADMIN -e VPN_SERVICE_PROVIDER=surfshark \
-p 8080:8080 \
-p 6881:6881 \
-p 6881:6881/udp \
-e VPN_TYPE=wireguard \
-e WIREGUARD_PRIVATE_KEY=<<privatekey>> \
-e WIREGUARD_ADDRESSES="10.14.0.2/16" \
-e SERVER_COUNTRIES=Netherlands qmcgaw/gluetun
Just recreate the vpn container with that name and all the rest of the parameter needed and start fresh. Add the —name=gluten-wireguard as part of your docker run as well as all the rest of the parameters.Then I tried to change the name of the container to the correct 'gluetun-wireguard'
Ok so looks like you are on the right track. There might be a custom port that is needed to be added to the vpn container (like the rest) depending on the tracker you are using. If it’s a private one then you will know what it is. If it’s a public one then not sure, not using torrents myself.Okay I managed to get both containers working by re-adding the qbittorrent container but with right name that was given to the gluetun container (while the gluetun container was running).
I can now access qbittorrent at port 8080, but something seems to not be working correctly. It takes very long to find any peers after adding a magnet link, if it finds some at all. Some that I tried just stay at 'stalled' or 'metadata' without finding any peers.
Is there anything I need to change about the portforwarding maybe?
Guess a test of internet connectivity via vpn container should be next.Yeah Im trying different magnets and torrents. And tried an ubuntu iso file as well, but it stays stalled.
Tried a private tracker as well as public ones, but both stay either stalled or finding metadata.
We use essential cookies to make this site work, and optional cookies to enhance your experience.