20 minutes ago, ryry said:

 

That said, I wasn't aware that wireguard config files could be downloaded from NordVPN.  Are you sure that this is possible?

I don’t use nordvpn so not sure how they make the configuration available. This looks like the docker isn’t parsing the file correctly. Maybe @binhex can take a look.

Hi,

 

I am using Unraid 7.0's tailscale plugin to connect to my dockers outside of my LAN. I seem to have DNS issues when I have tailscale enabled in any capacity. The only thing I've found that fixes it is to set TAILSCALE_USERSPACE_NETWORKING to true. While it's false, I can't curl google.com but I can curl the IP of google.com if I look up what it resolves to.

 

Is TAILSCALE_USERSPACE_NETWORKING true my best option here? Or is there something I can do to get the DNS working with false? I read the FAQs and also saw someone else mention disabling tailscale's magic dns, but disabling magic dns didn't work for me, and I would also prefer to keep using the machine names in my tailscale URLs rather than IPs.

 

I have use Tailscale's DNS turned off in Unraid's Tailscale setting's, and Override Local DNS on Tailscale admin disabled. Also, without TAILSCALE_USERSPACE_NETWORKING enabled, I can't connect to my other dockers in same custom docker network via name. IP only. 

 

Thanks in advance.

 

EDIT: I decided to use the qbit container as a tailscale exit node for another docker, and this requires userspace networking enabled anyway, so I guess it is indeed the best option for me.

Edited December 31, 20241 yr by mkahane

Hi Binhex,

 

Thank you for developing this container. I really appreciate it.

 

I was wondering if I could get some help from anyone.

I am a new Unraid user and have recently installed qBittorentVPN (as well as radarr, sonarr and prowlarr) by following AlienTech42 videos. But for the life of me qbittorrent never downloaded anything. 

 

I can see that radarr  and sonarr have connected to qbit and queried files to download but I got a "status erroded". 

 

All I get in the container docker log is a loop as follow (but I have also attached the actual log file):

2025-01-01 17:28:30,150 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176

2025-01-01 17:28:30,150 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent incoming port is 23176
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:29:00,151 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:29:15,178 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.187.228'

2025-01-01 17:29:15,178 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:29:15,182 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:29:15,185 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176

2025-01-01 17:29:15,185 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:29:45,187 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:29:48,044 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '23176'

2025-01-01 17:30:05,248 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.184.164'

2025-01-01 17:30:05,248 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:30:05,252 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:30:05,256 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176

2025-01-01 17:30:05,256 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:30:35,258 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:30:50,285 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.200.4'

2025-01-01 17:30:50,285 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:30:50,289 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:30:50,293 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:31:20,294 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:31:20,305 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.200.4'

2025-01-01 17:31:20,305 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:31:20,308 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:31:20,312 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176

2025-01-01 17:31:20,312 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:31:50,314 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:32:05,341 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.187.196'

2025-01-01 17:32:05,341 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:32:05,345 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:32:05,349 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

 

qbittorrent.log

3 hours ago, Yannoviche said:

Hi Binhex,

 

Thank you for developing this container. I really appreciate it.

 

I was wondering if I could get some help from anyone.

I am a new Unraid user and have recently installed qBittorentVPN (as well as radarr, sonarr and prowlarr) by following AlienTech42 videos. But for the life of me qbittorrent never downloaded anything. 

 

I can see that radarr  and sonarr have connected to qbit and queried files to download but I got a "status erroded". 

 

All I get in the container docker log is a loop as follow (but I have also attached the actual log file):

2025-01-01 17:28:30,150 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176

2025-01-01 17:28:30,150 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent incoming port is 23176
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:29:00,151 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:29:15,178 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.187.228'

2025-01-01 17:29:15,178 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:29:15,182 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:29:15,185 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176

2025-01-01 17:29:15,185 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:29:45,187 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:29:48,044 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '23176'

2025-01-01 17:30:05,248 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.184.164'

2025-01-01 17:30:05,248 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:30:05,252 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:30:05,256 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176

2025-01-01 17:30:05,256 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:30:35,258 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:30:50,285 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.200.4'

2025-01-01 17:30:50,285 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:30:50,289 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:30:50,293 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:31:20,294 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:31:20,305 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.200.4'

2025-01-01 17:31:20,305 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:31:20,308 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:31:20,312 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176

2025-01-01 17:31:20,312 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

2025-01-01 17:31:50,314 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2025-01-01 17:32:05,341 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.187.196'

2025-01-01 17:32:05,341 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-01-01 17:32:05,345 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-01-01 17:32:05,349 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 23176
[debug] qBittorrent incoming port is 23176
[debug] VPN IP is 10.18.217.46
[debug] qBittorrent IP is 10.18.217.46

 

qbittorrent.log 24.12 kB · 1 download

i suspect you do not understand docker bind mounts, from your log:-
/mnt/user/downloads/incomplete/linuxmint-19-mate-32bit.iso) error: Permission denied"

looks like you are trying to save to your array directly, instead you want to save to the container paths bind mount, e.g. /data so try setting incomplete downloads to /data/incomplete and save path to something like /data/completed

On 12/31/2024 at 2:23 AM, ryry said:

Yes, thank you for isolating the error, however I should have explained better.  I've bolded the endpoint in the wg0.conf above showing that it is, in fact, there.

 

That said, I wasn't aware that wireguard config files could be downloaded from NordVPN.  Are you sure that this is possible?

 

On 12/31/2024 at 2:49 AM, wgstarks said:

I don’t use nordvpn so not sure how they make the configuration available. This looks like the docker isn’t parsing the file correctly. Maybe @binhex can take a look.

ok i've taken a look, it needs a tweak to the regex to parse the endpoint, i have made the code change but its not live and i have some other changes to include before this, so for now simply ensure there is a space between the equals sign for the endpoint e.g.

 

Endpoint = vpn.endpont.com:1234

14 hours ago, binhex said:

i suspect you do not understand docker bind mounts, from your log:-
/mnt/user/downloads/incomplete/linuxmint-19-mate-32bit.iso) error: Permission denied"

looks like you are trying to save to your array directly, instead you want to save to the container paths bind mount, e.g. /data so try setting incomplete downloads to /data/incomplete and save path to something like /data/completed

Thank you @binhex. It resolved my issue.

And yes I am learning how to use unraid properly 😂.

Hello! First of all thank you for this docker.

 

I'm new to all of this and I'm confused regarding Privoxy and Microsocks. 

 

I have configured both in the docker. On my local Firefox config I put my Privoxy:8118 address in Proxy settings.

I also installed FoxyProxy and configured my Microsocks:9118 address. I did all of this as a security measure to ensure a failover. 

 

Is this overkill? I don't quite understand the difference between the two products. Is one better than the other?

 

Also, if the VPN tunnel (PIA with OPENVPN) goes down, is there some kind of killswitch for Pivoxy and Microsocks?

 

Thank you again!

On 12/29/2024 at 9:14 PM, dynamo666 said:

Attaching logs and run commandsupervisord.log.txtdocker run.txt

Bumping this request. Not made any traction and still failing.

 

Here is the config:

 

 

Still stuck on the same output

 

Hi, is it possible to use added parameters like calling a script like scriptname.sh also in this docker? that runs when the connection is up?

is that what  VPN_OPTIONS= is for? format for doing this?

12 minutes ago, orlando500 said:

that what  VPN_OPTIONS= is for?

No. This is for setting CLI options for OpenVPN.

43 minutes ago, wgstarks said:

No. This is for setting CLI options for OpenVPN.

you know how i can trigger a script when connection is up?

4 minutes ago, orlando500 said:

you know how i can trigger a script when connection is up?

I’m not aware of anything like this.

HI, is there any chance the libtorrentv1 tag could be updated ? The last update was over a year ago.

Edited January 6, 20251 yr by Bioux

@binhex, I would like to ask, if there is a possibility to release QbittorrentVPN with implemented libtorrent 1.2.2.0 version?

Thank You.

On 12/26/2024 at 10:22 AM, bloom_server said:

Hi Team, 

 

I'm having a hard time making QBittorrentvpn run. It was all good the past couple of weeks until last week when everything seemed to stopped. I deleted and reinstalled QBittorrentvpn and still nothing. 

 

IF I disable VPN in the qbittorrent docker, I can access it. Otherwise, it won't let me

 

FYI - I've attached the logs for your reference. 

 

Step 1 - Command Line.txt 1.49 kB · 0 downloads

 

supervisord - updated.txt 28.43 kB · 0 downloads

@binhex i never got helped on my issue. Can you assist me please? Really appreciate it. 

1 hour ago, bloom_server said:

@binhex i never got helped on my issue. Can you assist me please? Really appreciate it. 

your issue definitely looks dns related, from your log:-

 

2024-12-26 07:36:01,874 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

So try setting NAME_SERVERS to simply have a value of '1.1.1.1' and see if that helps.

23 hours ago, binhex said:

your issue definitely looks dns related, from your log:-

 

2024-12-26 07:36:01,874 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

So try setting NAME_SERVERS to simply have a value of '1.1.1.1' and see if that helps.

Hi, I seem to have the same problem since a few days.

I did change to '1.1.1.1' only and the problem still is the same.

It worked for month without a problem and then i think after the last update it stoped working without me changing anything.

 

Command execution.txt supervisord.log

23 hours ago, binhex said:

your issue definitely looks dns related, from your log:-

 

2024-12-26 07:36:01,874 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

So try setting NAME_SERVERS to simply have a value of '1.1.1.1' and see if that helps.

It did make things work! Thanks @binhex

 

35 minutes ago, rognir said:

Hi, I seem to have the same problem since a few days.

I did change to '1.1.1.1' only and the problem still is the same.

It worked for month without a problem and then i think after the last update it stoped working without me changing anything.

 

Command execution.txt 1.41 kB · 0 downloads supervisord.log 41.06 kB · 0 downloads

ok.

I made a new wireguard config and now it works... seems it was a problem with my vpn server?

 

1 hour ago, rognir said:

 

ok.

I made a new wireguard config and now it works... seems it was a problem with my vpn server?

 

certain vpn providers change their configuration frequently requiring a re-download, this is a common issue.

On 1/6/2025 at 10:11 PM, Bioux said:

HI, is there any chance the libtorrentv1 tag could be updated ? The last update was over a year ago.

Is it possible to get an answer

On 10/1/2024 at 2:19 PM, xrichnj said:

having an issue with torrents adding as "unknown" since the 5.0.0 update. they download when force resumed, but i lose control over them (cant pause, regular resume, or set speed limits). rolling back to 4.6.7-1-01 works fine as it always did. 

 

came back 3 months and a couple of 'point' update releases later and still the same result. what am i missing?

2 hours ago, xrichnj said:

 

came back 3 months and a couple of 'point' update releases later and still the same result. what am i missing?

Using a custom theme? If so this will be the issue, switch back to the default theme.

35 minutes ago, binhex said:

Using a custom theme? If so this will be the issue, switch back to the default theme.

 

this was it, i forgot it was even custom i was on 4.x.x for so long. new (stock) theme for 5.x.x kinda sucks, will look for something better designed for v5. thank you for the quick response and for all the hard work you put in. it is appreciated, @binhex

On 1/3/2025 at 3:47 PM, dynamo666 said:

Bumping this request. Not made any traction and still failing.

 

Here is the config:

 

 

Still stuck on the same output

 

bumping and requesting for help. I ahve changed the nameserver to 1.1.1.1 ith no luck. Also tried about 5 different server configs from Mullvad with no result. Any other suggestions? Thanks!