Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - qBittorrentVPN

Featured Replies

Deleted and tried starting over again, if I turn the vpn enabled to no, it works and pops up immedaitely

  • Replies 5.3k
  • Views 1.2m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I rolled back to tag 5.1.1-1-01 which fixed the issue for me. I guess the new update wasn't tested for wireguard connections. Edit the docker container and change "Repository" from binhex/arch-qbitt

  • FWIW, I found this method in Reddit that seemed to work for me until they fix the log bug. But note if you have qbittorrent internet facing, it's a risk.   Add this line under [Preferences]

  • gustyScanner
    gustyScanner

    Hello! I have been using wireguard successfully for a long time with this container, today though when the container restarted I got the following error: 2025-06-27 10:35:26,490 DEBG 'start-script'

Posted Images

Finally figured it out deleted some of the privoxy stuff and tried a different port and it now works for some reason thanks

6 hours ago, erfly7 said:

Finally figured it out deleted some of the privoxy stuff and tried a different port and it now works for some reason thanks

You might post the changes you made to get it working. Someone (not me 😁) might be able to explain why they worked so that it may help others.

 

Glad it’s working for you.

Deleted the two privoxy lines, changed port to 8081 instead of 8100 and for some reason worked, I also started from scratch and generated a whole new wireguard file from airvpn.

Tried logging into my application today and I cannot connect.  I disabled the VPN and it let me in... but of course no VPN...

 

I am using PIA for VPN...  Any ideas what happened?  I changed nothing overnight.

Did you want the files mentioned on that page?

 

 

Here is the Command executiondocker run
  -d
  --name='qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='xxxxxxxxx'
  -e 'VPN_PASS'='xxxxxxxxxx
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'WEBUI_PORT'='8080'
  -e 'LAN_NETWORK'='192.168.1.0/24, 10.8.0.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8080:8080/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/share_media/':'/data':'rw'
  -v '/mnt/user/share_media/torrents/prowlarr':'/prowlarr':'rw'
  -v '/mnt/user/share_media/torrents/music/':'/musicdownloads':'rw'
  -v '/mnt/user/appdata/qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

8126552ec8dea889a9da06038f7fbc2cf7a91d94525764b1196d52f09287920b

The command finished successfully!

2 minutes ago, twidget2011 said:

Did you want the files mentioned on that page?

Yes. Those were instructions for what info to post. Be sure to redact user/password.

On 10/27/2024 at 5:08 PM, nerbonne said:

I assume you mean the 10.10.6.0/23 network?   Yes, my desktop PC is IP 10.10.6.7/23

 

Did you find a solution... I think I have the same issue...

Looks like a successful start followed by a few restarts. Have you tried using a different endpoint?

14 minutes ago, wgstarks said:

Looks like a successful start followed by a few restarts. Have you tried using a different endpoint?

What do you mean by endpoint? Do you mean like a different VPN Provider?

You’ll need to restart the docker after you make the changes.

Let me try that now...

47 minutes ago, wgstarks said:

Looks like a successful start followed by a few restarts. Have you tried using a different endpoint?

I changed it... same result....  If I disable VPN, I can connect... with VPN, I cannot connect to torrent client...

What IP are you trying to connect from?

I have tried two on my home network...

Is that 192.168.1.0/24?

6 minutes ago, wgstarks said:

Is that 192.168.1.0/24?

it was in that subnet...

I just tried again.. now it is up... I have no earthy idea why...  

Very annoying and strange...

The docker restart can sometimes take several minutes.

The arm64 docker image 5.0.1-1-01 is still using qBit 5.0.0

11 hours ago, twidget2011 said:

Did you find a solution... I think I have the same issue...

Nope.  I was hoping the maintainer ( @binhex ) would drop in. I appreciate @wgstarks replying to all the questions but hasn't been able to help and I worry that all the activity is hiding the fact that multiple people are having this problem.

Having a weird issue when launching the container. Have not changed anything within the container or docker image aside from updating image from time to time. Last I ran it (some weeks ago) it worked fine.

Found in the log that its struggling with creating a tun0 interface, but not sure why. I will mention that I sometimes run the container while running NordVPN on the host. I tested turning that off, but the issue remained.

Perhaps somebody here knows what can be done about this or where to start to troubleshoot.

Here is the log

 

2024-11-01 20:47:37,861 DEBG 'start-script' stdout output:
default via 172.19.0.1 dev eth0
172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.0.2
192.168.56.0/24 via 172.19.0.1 dev eth0

2024-11-01 20:47:37,861 DEBG 'start-script' stdout output:
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
local 172.19.0.2 dev eth0 table local proto kernel scope host src 172.19.0.2
broadcast 172.19.255.255 dev eth0 table local proto kernel scope link src 172.19.0.2
local ::1 dev lo table local proto kernel metric 0 pref medium

2024-11-01 20:47:37,861 DEBG 'start-script' stdout output:
--------------------

2024-11-01 20:47:37,897 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2024-11-01 20:47:37,898 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 95.174.66.27/32 -i eth0 -j ACCEPT
-A INPUT -s 172.19.0.0/16 -d 172.19.0.0/16 -j ACCEPT
-A INPUT -s 95.174.66.27/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 1337 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 1337 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -d 95.174.66.27/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.19.0.0/16 -d 172.19.0.0/16 -j ACCEPT
-A OUTPUT -d 95.174.66.27/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 1337 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 1337 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2024-11-01 20:47:37,899 DEBG 'start-script' stdout output:
--------------------

2024-11-01 20:47:37,899 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-11-01 20:47:37,904 DEBG 'start-script' stdout output:
2024-11-01 20:47:37 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

2024-11-01 20:47:37,904 DEBG 'start-script' stdout output:
2024-11-01 20:47:37 Note: '--allow-compression' is not set to 'no', disabling data channel offload.
2024-11-01 20:47:37 WARNING: file 'credentials.conf' is group or others accessible
2024-11-01 20:47:37 OpenVPN 2.6.12 [git:makepkg/038a94bae57a446c+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jul 18 2024
2024-11-01 20:47:37 library versions: OpenSSL 3.4.0 22 Oct 2024, LZO 2.10
2024-11-01 20:47:37 DCO version: N/A

2024-11-01 20:47:37,904 DEBG 'start-script' stdout output:
2024-11-01 20:47:37 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2024-11-01 20:47:37 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-11-01 20:47:37 NOTE: --fast-io is disabled since we are not using UDP

2024-11-01 20:47:37,905 DEBG 'start-script' stdout output:
2024-11-01 20:47:37 TCP/UDP: Preserving recently used remote address: [AF_INET]95.174.66.27:443

2024-11-01 20:47:37,905 DEBG 'start-script' stdout output:
2024-11-01 20:47:37 Socket Buffers: R=[131072->131072] S=[16384->16384]
2024-11-01 20:47:37 Attempting to establish TCP connection with [AF_INET]95.174.66.27:443

2024-11-01 20:47:37,953 DEBG 'start-script' stdout output:
2024-11-01 20:47:37 TCP connection established with [AF_INET]95.174.66.27:443
2024-11-01 20:47:37 TCPv4_CLIENT link local: (not bound)
2024-11-01 20:47:37 TCPv4_CLIENT link remote: [AF_INET]95.174.66.27:443

2024-11-01 20:47:38,048 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 TLS: Initial packet from [AF_INET]95.174.66.27:443, sid=2a172d4e 79aebbe9

2024-11-01 20:47:38,196 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2024-11-01 20:47:38,196 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA9

2024-11-01 20:47:38,196 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 VERIFY KU OK
2024-11-01 20:47:38 Validating certificate extended key usage
2024-11-01 20:47:38 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication

2024-11-01 20:47:38,196 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 VERIFY EKU OK
2024-11-01 20:47:38 VERIFY X509NAME OK: CN=no149.nordvpn.com
2024-11-01 20:47:38 VERIFY OK: depth=0, CN=no149.nordvpn.com

2024-11-01 20:47:38,376 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519
2024-11-01 20:47:38 [no149.nordvpn.com] Peer Connection Initiated with [AF_INET]95.174.66.27:443
2024-11-01 20:47:38 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1

2024-11-01 20:47:38,376 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 TLS: tls_multi_process: initial untrusted session promoted to trusted

2024-11-01 20:47:38,508 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,explicit-exit-notify,comp-lzo no,route-gateway 10.100.0.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.100.0.2 255.255.255.0,peer-id 0,cipher AES-256-GCM'

2024-11-01 20:47:38,508 DEBG 'start-script' stdout output:
2024-11-01 20:47:38 OPTIONS IMPORT: --explicit-exit-notify can only be used with --proto udp
2024-11-01 20:47:38 OPTIONS IMPORT: --ifconfig/up options modified
2024-11-01 20:47:38 OPTIONS IMPORT: route options modified
2024-11-01 20:47:38 OPTIONS IMPORT: route-related options modified
2024-11-01 20:47:38 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2024-11-01 20:47:38 net_route_v4_best_gw query: dst 0.0.0.0
2024-11-01 20:47:38 net_route_v4_best_gw result: via 172.19.0.1 dev eth0
2024-11-01 20:47:38 ROUTE_GATEWAY 172.19.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:13:00:02
2024-11-01 20:47:38 ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted (errno=1)
2024-11-01 20:47:38 Exiting due to fatal error

Appreciate any input.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.