How to verify my qBittorrent Docker network settings run through my VPN on NAS?

VPN
1

Basically the title.

Is there a way to verify I set up everything correctly and both my NAS and qBit via Docker run through the VPN?

I can provide whichever pictures needed.

2

docker exec into the container, then run a curl to an ip address identifier.

something like:

  1. docker exec -it qbittorrent bash
  2. curl curl -4 icanhazip.com
3

You can use ipleak, download a magnet link from their site and compare your ip to the torrenting ip.

4

Can I ask what docker image are you using? Been looking for something that would work with wireguard on a Synology amd.

5

Try this: https://torguard.net/checkmytorrentipaddress.php?

Edited to add that the “Download” button is a magnet link that adds a zero sized torrent to your torrent client.

6

This worked perfectly, thanks!

7

for clarity, after these commands should the expected return be something like this? with the IP shown not equal to the actual IP of the network?

root@****a:/# curl curl -4 icanhazip.comcurl: (6) Could not resolve host: curl37.19.211.113root@****a:/#

8

Yea I tried that and I ran the Torrent thing locally, it works fine (shows VPN info).

But when I run it on qBit on my NAS, it never shows up on the site. Waited several minutes.

Any idea what might be the issue?

9

Thanks for the site, really helpful!

I ran the Torrent thing locally, and it works fine (shows VPN info).

But when I run it on qBit on my NAS, it never shows up on the site. Waited several minutes.

Any idea what might be the issue?

10

I believe it is this one.

https://hub.docker.com/r/linuxserver/qbittorrent

11

Thanks for the site.

I ran the Torrent thing locally, and it works fine (shows VPN info).

But when I run it on qBit on my NAS, it never shows up on the site. Waited several minutes.

Any idea what might be the issue? qBit is currently working on my NAS so it is definitely connected.

12

Then the question is if your Qbit container is actually running in the first place. Try a different magnet link which works locally and if that doesn’t work then your container has issues. Alternatively you could run “curl ipinfo.io/ip” in the docker container’s shell. If you don’t have curl use “wget -q0- https://ifconfig.io/” this will return your public ip from that container.

13

nope, you’d need the hotio image of qbittorrent to use a wireguard vpn

14

That’s weird. At the very minimum, it should’ve shown you your WAN IP on the torguard website. Sounds like qBit isn’t connecting at all via your NAS.

15

qBit works for all the other stuff, it doesn’t work only with that specific magnet link. That’s the weird part.

By the docker container’s shell, do you mean this, or something else?

https://imgur.com/a/MzlLeML

16

Thanks for the suggestions. I am actually using qBit currently and it works fine, it just an issue with that magnet link.

Well, the issue is on my end I am sure, because it shows up when I use it on my PC locally.

17

I’m using the linuxserver image just fine in conjunction with gluetun.

18

Thanks for the suggestions. I am actually using qBit currently and it works fine, it just an issue with that magnet link.

Well, the issue is on my end I am sure, because it shows up when I use it on my PC locally.

19

yes, with a second container. You can also use hotio container and have it take care of the VPN in the single container

20

This is what I ended up doing. I did get hotio image working with wg but gluetun seemed a better solution.