Hi there binhex,

I've started using Tailscale recently and am now configuring it for your qBt container.

 

The wireguard and tailscale network interfaces clash, as you pointed out in Q30:

Quote

Q30. I can view the applications Web UI from my home LAN, but whenever I connect to my home LAN using a remote connection (such as Tailscale, Cloudflare, OpenVPN or Wireguard) I can no longer view the application Web UI, I can view all other docker container Web UI's but not the **VPN ones, why is this and how can I fix it?.

 

A30. This is due to strict iptables rules, you need to add the VPN network to the LAN_NETWORK value using a comma as a separator, e.g. LAN_NETWORK=192.168.1.0/24,192.168.2.0/24, if you are having difficulty calculating the CIDR mask (digits after the forward slash) or finding out the network then see Q4 above.

 

So I've added "100.64.0.0/10", which should cover the full Tailscale range from 100.64.0.0 to 100.127.255.255, to the LAN_NETWORK key of the docker container. I can see it in the docker logs when I start it like this:

2025-04-22 11:34:42.545004 [info] LAN_NETWORK defined as '192.168.2.0/24,100.64.0.0/10'
2025-04-22 11:34:42.566671 [info] LAN_NETWORK exported as '192.168.2.0/24,100.64.0.0/10'

 

Unfortunately I am still stuck in the wireguard up/down loop, as seen from the logs below. What am I doing wrong?

 

2025-04-22 11:41:55,441 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2025-04-22 11:41:55,442 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2025-04-22 11:41:55,443 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2025-04-22 11:42:46,031 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2025-04-22 11:42:51,504 DEBG 'start-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2025-04-22 11:42:51,506 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2025-04-22 11:42:51,513 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'...

2025-04-22 11:42:51,519 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'...

2025-04-22 11:42:51,525 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'...

2025-04-22 11:42:51,530 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, performing tests before setting to '127.0.0.1'...
[info] Show name servers defined for container

2025-04-22 11:42:51,531 DEBG 'start-script' stdout output:
# resolv.conf(5) file generated by tailscale
# For more info, see https://tailscale.com/s/resolvconf-overwrite
# DO NOT EDIT THIS FILE BY HAND -- CHANGES WILL BE OVERWRITTEN

nameserver 100.100.100.100
search [REDACTED].ts.net

2025-04-22 11:42:51,531 DEBG 'start-script' stdout output:
[info] Show contents of hosts file

2025-04-22 11:42:51,531 DEBG 'start-script' stdout output:
127.0.0.1       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.17.0.9      8e9ea6256209

2025-04-22 11:42:51,532 DEBG 'start-script' stdout output:
[info] VPN provider 'airvpn' not supported for automatic port forwarding, skipping incoming port assignment

2025-04-22 11:42:51,533 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2025-04-22 11:43:21,533 DEBG 'start-script' stdout output:
[info] Sending 'down' command to WireGuard due to dns failure...

2025-04-22 11:43:21,534 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'down'...

2025-04-22 11:41:55,441 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2025-04-22 11:41:55,442 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2025-04-22 11:41:55,443 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

 

Edited April 22, 20251 yr by PaulieW

17 minutes ago, PaulieW said:

# resolv.conf(5) file generated by tailscale
# For more info, see https://tailscale.com/s/resolvconf-overwrite
# DO NOT EDIT THIS FILE BY HAND -- CHANGES WILL BE OVERWRITTEN

nameserver 100.100.100.100
search [REDACTED].ts.net

Tailscale messes with DNS causing name lookup failure, you cannot use it with this container, Please see Q36 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

5 hours ago, binhex said:

Tailscale messes with DNS causing name lookup failure, you cannot use it with this container, Please see Q36 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Ah I see. I indeed have MagicDNS enabled, TAILSCALE_USERSPACE_NETWORKING is already set to FALSE. So MagicDNS is probably my issue then.

 

I have lots of containers like radarr.my-tsname.ts.net, sonarr.my-tsname.ts.net, etc for which I would like to keep using MagicDNS

 

Edit: I see here https://tailscale.com/kb/1235/resolv-conf that:

Quote

you can either disable MagicDNS for all devices in your tailnet or run tailscale set --accept-dns=false to disable MagicDNS on a single device.

So it should be possible to only disable MagicDNS for the qBittorrent container, right? Would I just run this command

tailscale set --accept-dns=false

in the console window of the binhex-qbittorrent container?

 

Edit2: I believe I've done it, by adding the parameter 

--accept-dns=false

 

to the Extra Parameters field:

 

For some reason I can now connect to it using the MagicDNS address, but not the IPv4 address. I was expecting it to be the other way around. Maybe it has to do with the HTTPS certificate I put in place. Anyways, I think this does the job.

Edited April 22, 20251 yr by PaulieW

Ok, I was not sure whats cause and whats just a resulting problem. I'll take a deeper look at that. Thanks

Hey Binhex! I've recently switched from Windscribe to Proton and how I can't get my WebUI to open. I've removed & added the ports per the FAQ on Github, but I'm not getting any success getting the WebUI to open. Are there logs I can gather & share to make this easier?

I recently just swapped over to PIA from Mullvad and I have it set up for the most part in the qbittorrent-vpn container and after watching a video I was able to update the wg0.conf so that I was no longer connecting to nl-amserdam. I was watching a video and they swapped to ca-toronto.privacy.network:1337 which seems to work for me too.

However, my question, is there a convenient list of this endpoint addresses that are available to use with wireguard? Or is the standard "country-city.privacy.network:1337"? Also I see that not all these endpoints support port forwarding but based in the log I can see that the toronto endpoint I am using currently does support it.

 

I tried searching through this long forum post for answers but wasn't having much luck. I really enjoy this container and all the support there is for it.

Any advice is greatly appreciated!

Is anybody having issues with files only saving straight to the array disk one no matter what you do with data location set to?

Hi - 

 

You may or may not be aware that a not insignificant portion of your user base use trackers that heavily restrict the specific versions of clients they allow to connect (applies to any torrent client, not just qbit, so the following feedback applies to all the clients you distribute).  Most that I'm aware of have blanket approvals for qBit 5.0.x, but the recently released 5.1.x remains verboten. 

 

With the information available in the Unraid update UI, I have no idea of accepting the update will break my ability to connect to such trackers.  

 

I would ask at a minimum that you include a changelog that includes the specific version of the given torrent client contained therein.  

 

My personal sanity would ask that you provide a docker tag for at least for each major/minor version (e.g., an update channel each for 5.0.x and 5.1.x in the case of qbit) so that I don't have to ignore an update until all my trackers support that version.  

5 hours ago, dmw_chef said:

With the information available in the Unraid update UI, I have no idea of accepting the update will break my ability to connect to such trackers. 

The tags i use should give you the information you require, the tag format is <app version>--<upstream build number>-<my build number>, so for example '5.1.0-01-01' means app version v5.1.0, upstream build 01,  my build 01.

Tags can be found for every image at docker hub:- https://hub.docker.com/r/binhex/arch-qbittorrentvpn/tags

 

5 hours ago, dmw_chef said:

My personal sanity would ask that you provide a docker tag for at least for each major/minor version (e.g., an update channel each for 5.0.x and 5.1.x in the case of qbit) so that I don't have to ignore an update until all my trackers support that version.  

Or alternatively don't use 'latest' and instead use the specific version tags shown in the link above, adding in automated tagging for major-minor versions is tricky as i would need to cover all different version schemes for all the applications i support (60+), it's possible but its work.

 

p.s. 5.1.0 has literally just been built, so if your tracker has not ok'd that version then do NOT update at this time.

Hi,

Would like to run a second instance of the docker binhex-readarr.  My first one is running happily through the binhex-qbittorrentvpn.  I see in the FAQ for this forum that web interface must have a different port number.  by default its on 8787 from memory.  What do i need to tweak in the docker and also the binhex-qbittorrentvpn to get the web interface to work.

 

Thanks,

Dwarfboysim

 

Seem to have a random issue where my downloading torrents show up for a few seconds after I refresh the browser and then disappear.

They are still there downloading - but just disappear. Whatever filter on the left column I hit nothing shows unless I refresh.

I uninstalled and reinstalled and seems to have fixed it!

@binhex Is it seriously too much to ask that the client version included in the image be in the update changelog?

Edited April 30, 20251 yr by dmw_chef
me fail english, that's unpossible

8 hours ago, leejbarker said:

I uninstalled and reinstalled and seems to have fixed it!

Same issue.

3 hours ago, dmw_chef said:

@binhex Is it seriously too much to ask that the client version included in the image be in the update changelog?

Is it seriously too much to ask for you to click on a single link to view the version before upgrading? if i programmatically generated a changelog it would consist of the same information as the tag, plus any commits (of which the vast majority of the time there will be none), what benefit is that?, do keep in mind I have 60+ repositories to support here, and what you might think is a trivial change is not for me.

EDIT - I will see how tricky it is to create versioned tags as I do see the benefit in this.

On 4/28/2025 at 9:43 AM, Dwarfboysim said:

Hi,

Would like to run a second instance of the docker binhex-readarr.  My first one is running happily through the binhex-qbittorrentvpn.  I see in the FAQ for this forum that web interface must have a different port number.  by default its on 8787 from memory.  What do i need to tweak in the docker and also the binhex-qbittorrentvpn to get the web interface to work.

 

Thanks,

Dwarfboysim

 

You would need to avoid any host port clashes, so yes different ports will be required, you will also need to have a different host path for /config, on top of that you will need to use a different browser for the different containers, this is due to qbittorrent cookies related issues.

After updating I can no longer see torrents listed in the web gui on Firefox. If I switch over to Chrome I can see them. I tried clearing cookies on Firefox and restarting the container, but those didn't seem to work. Any advice?

Edited April 30, 20251 yr by pantsonadog
Typo

10 hours ago, pantsonadog said:

After updating I can no longer see torrents listed in the web gui on Firefox. If I switch over to Chrome I can see them. I tried clearing cookies on Firefox and restarting the container, but those didn't seem to work. Any advice?

Came to ask the same question. Torrents were not showing in Chrome. Tried Edge and Firefox and both working. Was able to get Chrome working by following these steps

To clear the cache for a specific website in Google Chrome, navigate to the website, open Developer Tools (F12), go to the "Application" tab, select "Storage", and then click "Clear site data"

 

In Firefox try (ctrl + shift + i) then "storage" then on the left you can delete Cache Storage for each catagory.

Edited May 1, 20251 yr by Merkas

Is there a way to create a torrent from within this container? It seems to be missing some options that the "normal" version has on my personal computer.

No, the container version doesn't have the torrent creator

7 hours ago, domrego said:

Is there a way to create a torrent from within this container? It seems to be missing some options that the "normal" version has on my personal computer.

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/page/177/#findComment-1546747

 

13 hours ago, binhex said:

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/page/177/#findComment-1546747

 

Essentially, use a different torrent client if I want to do this? Just want to make sure i'm not misunderstanding lol

2 hours ago, domrego said:

Essentially, use a different torrent client if I want to do this? Just want to make sure i'm not misunderstanding lol

I'm dumb, I'm seeing now that this is like a skin, and the alternate UI has the ability to create a torrent

On 4/30/2025 at 8:33 AM, binhex said:

EDIT - I will see how tricky it is to create versioned tags as I do see the benefit in this.

This has now been implemented:- 

 

 

Wanna see if anyone is having an issue using the new feature in 5.1.0 'FEATURE: Display External IP Address in status bar'

When I start up the container, it will show the PIA VPN IP address that I'm using but than a few minutes later it will change and show my real External IP address.  That shouldn't be happening, right?

Edited May 6, 20251 yr by ibmsynchronous