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

I'd like to ask for help with configuring binhex-sonarr to connect to binhex-qbittorrentvpn.

 

My docker containers are running under Unraid, on a custom network, br0. My sonarr instance is at 10.1.1.77/24, while my qbittorrent instance is at 10.1.1.74/24. My desktop PC at 10.0.0.10/24, and it can browse to the qbittorrent webUI just fine, hopping through my router from my home vlan to my server vlan.

 

When I configure qbittorrent as a downloader in sonarr, and I click, "Test," this error message appears in the supervisord log: "Http request timed out".

 

Why does the webUI work fine for a device in another subnet, but connectivity to a device in the same subnet fails?

 

qBittorrentvpn is configured to use a VPN service, and the LAN_NETWORK variable has this value: "10.0.0.0/24, 10.1.1.0/24".

 

Here's my run commands:
 

#sonarr
docker run   -d   --name='binhex-radarr'   --net='br0'   --ip='10.1.1.77'   --pids-limit 2048   -e TZ="America/Chicago"   -e HOST_OS="Unraid"   -e HOST_HOSTNAME="homeserver"   -e HOST_CONTAINERNAME="binhex-radarr"   -e 'TCP_PORT_7878'='7878'   -e 'SHARED_NETWORK'='no'   -e 'PUID'='99'   -e 'PGID'='100'   -e 'UMASK'='002'   -l net.unraid.docker.managed=dockerman   -l net.unraid.docker.webui='http://[IP]:[PORT:7878]'   -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/radarr-icon.png'   -v '/mnt/user/appdata/binhex-radarr':'/config':'rw'   -v '/mnt/user/media/':'/data':'rw'   -v 'binhex-shared':'/shared':'rw' 'binhex/arch-radarr' 
  
#qbittorrent-vpn
docker run -d --name='binhex-qbittorrentvpn' --net='br0' --ip='10.1.1.74' --pids-limit 2048 --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="homeserver" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8118'='8118' -e 'TCP_PORT_9118'='9118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='[Redacted]' -e 'VPN_PASS'='[Redacted]' -e 'VPN_PROV'='protonvpn' -e 'VPN_CLIENT'='openvpn' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'ENABLE_SOCKS'='no' -e 'SOCKS_USER'='admin' -e 'SOCKS_PASS'='socks' -e 'LAN_NETWORK'='10.0.0.0/24, 10.1.1.0/24' -e 'WEBUI_PORT'='8080' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'TCP_PORT_58946'='58946' -e 'UDP_PORT_58946'='58946' -e 'VPN_OPTIONS'='' -e 'ENABLE_STARTUP_SCRIPTS'='no' -e 'USERSPACE_WIREGUARD'='no' -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 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -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' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' -v '/mnt/user/media/torrents/':'/data':'rw' -v 'binhex-shared':'/shared':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' 

 

radarr-supervisord.log qbittorrent-supervisord.log

  • Replies 5.2k
  • Views 1.1m
  • 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

  • Author
37 minutes ago, wgstarks said:

Yeah. Thanks. Been looking for an easy way to pull template updates but looks like I can either modify files that wont survive a reboot (I hate mc) or take screenshots of the settings, install a fresh version of the docker and configure everything all over again.

word of warning, if you do go down the wipe and do it again route i have drastically changed the template to make it more user friendly, so things will look a bit different.

On 1/3/2024 at 2:00 PM, wgstarks said:

 

Another option would be to whitelist connections from your local network.

 

IMG_2629.thumb.jpeg.b3d5a7508d9d9155f8e09d804babbb27.jpeg

 

172.17.0.0/24 is the network assigned to docker0 in my unRAID machine. You can verify yours by checking Settings>Network Settings>Routing Tables.

 

 

 

Thanks for this.  I was having trouble getting my subnet in the whitelist when accessing over tailscale, adding 172.17.0.0/24 worked.

How do I setup a Watch Folder to auto load torrents put in it. I have it working in PC version, but I can't get it to work in Unraid dockerScreenshot2024-12-12100952.png.ba8df0b0b2db6f5b65260b949d82c3fa.png

What happens when you drop a torrent file into whatever folder that container path is mapped to?

1 minute ago, wgstarks said:

What happens when you drop a torrent file into whatever folder that container path is mapped to?

nothing. I have to add it to Q manually

Did the docker create this folder when you configured the setting?

I'm having some trouble lately with the container and can't figure out why.

 

text  error  warn  system  array  login  

[info] montenegro.privacy.network
[info] austria.privacy.network
[info] no.privacy.network
[info] lu.privacy.network
[info] is.privacy.network
[info] au-adelaide-pf.privacy.network
[info] bogota.privacy.network
[info] italy.privacy.network
[info] de-berlin.privacy.network
[info] malta.privacy.network
[info] za.privacy.network
[info] philippines.privacy.network
[info] nl-amsterdam.privacy.network
[info] japan.privacy.network
[info] gt-guatemala-pf.privacy.network
[info] lt.privacy.network
[info] panama.privacy.network
[info] hungary.privacy.network
[info] liechtenstein.privacy.network
[info] macau.privacy.network
[info] morocco.privacy.network
[info] nigeria.privacy.network
[info] nl-netherlands-so.privacy.network
[info] vietnam.privacy.network
[info] gr.privacy.network
[info] kualalumpur.privacy.network
[info] saudiarabia.privacy.network
[info] hk.privacy.network
[info] ar.privacy.network
[info] bahamas.privacy.network
[info] egypt.privacy.network
[info] denmark.privacy.network
[info] china.privacy.network
[info] yerevan.privacy.network
[info] srilanka.privacy.network
[info] lv.privacy.network
[info] ad.privacy.network
[info] ee.privacy.network
[info] greenland.privacy.network

2024-12-17 13:47:39,711 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'

2024-12-17 13:48:25,665 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.40.160.216 different, marking for reconfigure

2024-12-17 13:48:25,676 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2024-12-17 13:48:25,677 DEBG 'watchdog-script' stdout output:
[info] qBittorrent incoming port 6881 and VPN incoming port 31230 different, marking for reconfigure

2024-12-17 13:48:25,679 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2024-12-17 13:48:25,737 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2024-12-17 13:48:25,743 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2024-12-17 13:48:26,424 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2024-12-17 13:57:39,808 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'

2024-12-17 14:07:39,906 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'

2024-12-17 14:17:40,028 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'

2024-12-17 14:27:40,273 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'

2024-12-17 14:37:40,366 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'

2024-12-17 14:47:40,474 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'

2024-12-17 14:57:40,583 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'

2024-12-17 15:07:40,675 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '31230'


This is my latest logfile but when I check for open ports by a website like portchecker.co it says the port is closed. also the torrentwebsites say so. Also the torrentsites display that I'm not connectable.

I'm using wireguard PIA. Does someone know what might be the issue.

I especially wonder about these 2 lines:

[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.40.160.216 different, marking for reconfigure
[info] qBittorrent incoming port 6881 and VPN incoming port 31230 different, marking for reconfigure

grafik.png

Edited by matuopm

  • Author
5 minutes ago, matuopm said:

[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.40.160.216 different, marking for reconfigure

That ip address is the internal ip address used to establish the tunnel, its not your internet external ip, check the log again it should mention what your external ip is, if you cant see it then use the 'console' for the container and then issue the command 'curl ifconfig.io'

omg iam using the container for ages and did not know that. sadly my log is not long enough for me to see that but
curl ifconfig.io worked, i got the external IP now.
and it also displays the port as open now. thank you much

  • Author
4 minutes ago, matuopm said:

omg iam using the container for ages and did not know that. sadly my log is not long enough for me to see that but
curl ifconfig.io worked, i got the external IP now.
and it also displays the port as open now. thank you much

Any IP in the 10.x.x.x range is reserved

Previously had this working for a docker container in Qnap. Switched to Unraid. Was able to set it up easily and it was initially working with Nordvpn.

 

Now I'm getting the following error using:

 

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2024-12-19 13:13:51.904117 [info] Host is running unRAID
2024-12-19 13:13:51.917702 [info] System information: Linux ebccd6005156 6.1.118-Unraid #1 SMP PREEMPT_DYNAMIC Thu Nov 21 15:54:38 PST 2024 x86_64 GNU/Linux
2024-12-19 13:13:51.930566 [info] Image tags: BASE_RELEASE_TAG=2024110703,INT_RELEASE_TAG=2024110703,IMAGE_RELEASE_TAG=5.0.3-1-01
2024-12-19 13:13:51.944800 [info] PUID defined as '99'
2024-12-19 13:13:51.961581 [info] PGID defined as '100'
2024-12-19 13:13:52.007313 [info] UMASK defined as '000'
2024-12-19 13:13:52.021605 [info] Permissions already set for '/config'
2024-12-19 13:13:52.036443 [info] Deleting files in /tmp (non recursive)...
2024-12-19 13:13:52.053709 [info] VPN_ENABLED defined as 'yes'
2024-12-19 13:13:52.069494 [info] VPN_CLIENT defined as 'openvpn'
2024-12-19 13:13:52.083969 [info] VPN_PROV defined as 'custom'
2024-12-19 13:13:52.104802 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/se400.nordvpn.com.udp.ovpn
2024-12-19 13:13:52.139339 [info] VPN remote server(s) defined as '37.120.209.219,'
2024-12-19 13:13:52.152996 [info] VPN remote port(s) defined as '1194,'
2024-12-19 13:13:52.165963 [info] VPN remote protcol(s) defined as 'udp,'
2024-12-19 13:13:52.181317 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-12-19 13:13:52.195223 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-12-19 13:13:52.209223 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2024-12-19 13:13:52.347781 [info] LAN_NETWORK defined as '192.168.1.0/24'
2024-12-19 13:13:52.368919 [info] LAN_NETWORK exported as '192.168.1.0/24'
2024-12-19 13:13:52.383447 [info] VPN_USER defined as REDACTED
2024-12-19 13:13:52.398099 [info] VPN_PASS defined as REDACTED
2024-12-19 13:13:52.414594 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2024-12-19 13:13:52.428972 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2024-12-19 13:13:52.445129 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2024-12-19 13:13:52.460057 [info] ENABLE_SOCKS defined as 'no'
2024-12-19 13:13:52.475430 [info] ENABLE_PRIVOXY defined as 'yes'
2024-12-19 13:13:52.490087 [info] WEBUI_PORT defined as '8080'
2024-12-19 13:13:52.507132 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-12-19 13:13:52.520710 [info] Starting Supervisor...
2024-12-19 13:13:52,609 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2024-12-19 13:13:52,609 INFO Set uid to user 0 succeeded
2024-12-19 13:13:52,610 INFO supervisord started with pid 7
2024-12-19 13:13:53,613 INFO spawned: 'start-script' with pid 292
2024-12-19 13:13:53,614 INFO spawned: 'watchdog-script' with pid 293
2024-12-19 13:13:53,614 INFO reaped unknown pid 8 (exit status 0)
2024-12-19 13:13:53,616 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2024-12-19 13:13:53,616 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-19 13:13:53,616 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-19 13:13:53,621 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible

2024-12-19 13:13:53,749 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via adapter eth0

2024-12-19 13:13:53,750 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2024-12-19 13:13:53,751 DEBG 'start-script' stdout output:
default via 172.18.0.1 dev eth0 
172.18.0.0/16 dev eth0 proto kernel scope link src 172.18.0.11 
192.168.1.0/24 via 172.18.0.1 dev eth0 

2024-12-19 13:13:53,751 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.18.0.11 dev eth0 table local proto kernel scope host src 172.18.0.11 
broadcast 172.18.255.255 dev eth0 table local proto kernel scope link src 172.18.0.11 
--------------------

2024-12-19 13:13:53,754 DEBG 'start-script' stdout output:
iptable_mangle         16384  1
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               45056  16 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,ip6_tables,ipt_REJECT,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2024-12-19 13:13:53,754 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2024-12-19 13:13:53,785 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2024-12-19 13:13:53,785 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 37.120.209.219/32 -i eth0 -j ACCEPT
-A INPUT -s 172.18.0.0/16 -d 172.18.0.0/16 -j ACCEPT
-A INPUT -s 37.120.209.219/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8080 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.18.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -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 37.120.209.219/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.18.0.0/16 -d 172.18.0.0/16 -j ACCEPT
-A OUTPUT -d 37.120.209.219/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8080 -j ACCEPT
-A OUTPUT -s 172.18.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8118 -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-12-19 13:13:53,786 DEBG 'start-script' stdout output:
--------------------

2024-12-19 13:13:53,787 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-12-19 13:13:53,792 DEBG 'start-script' stdout output:
2024-12-19 13:13:53 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-12-19 13:13:53 Note: '--allow-compression' is not set to 'no', disabling data channel offload.

2024-12-19 13:13:53,792 DEBG 'start-script' stdout output:
2024-12-19 13:13:53 WARNING: file 'credentials.conf' is group or others accessible
2024-12-19 13:13:53 OpenVPN 2.6.12 [git:makepkg/038a94bae57a446c+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Dec 16 2024
2024-12-19 13:13:53 library versions: OpenSSL 3.4.0 22 Oct 2024, LZO 2.10
2024-12-19 13:13:53 DCO version: N/A

2024-12-19 13:13:53,792 DEBG 'start-script' stdout output:
2024-12-19 13:13:53 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2024-12-19 13:13:53 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2024-12-19 13:13:53,793 DEBG 'start-script' stdout output:
2024-12-19 13:13:53 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.209.219:1194
2024-12-19 13:13:53 Socket Buffers: R=[212992->212992] S=[212992->212992]
2024-12-19 13:13:53 UDPv4 link local: (not bound)
2024-12-19 13:13:53 UDPv4 link remote: [AF_INET]37.120.209.219:1194

2024-12-19 13:13:53,803 DEBG 'start-script' stdout output:
2024-12-19 13:13:53 TLS: Initial packet from [AF_INET]37.120.209.219:1194, sid=5e594959 3b18b8d4

2024-12-19 13:13:53,827 DEBG 'start-script' stdout output:
2024-12-19 13:13:53 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
2024-12-19 13:13:53 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA9

2024-12-19 13:13:53,827 DEBG 'start-script' stdout output:
2024-12-19 13:13:53 VERIFY KU OK
2024-12-19 13:13:53 Validating certificate extended key usage
2024-12-19 13:13:53 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-12-19 13:13:53 VERIFY EKU OK
2024-12-19 13:13:53 VERIFY OK: depth=0, CN=se400.nordvpn.com

2024-12-19 13:13:53,837 DEBG 'start-script' stdout output:
2024-12-19 13:13:53 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-12-19 13:13:53 [se400.nordvpn.com] Peer Connection Initiated with [AF_INET]37.120.209.219:1194
2024-12-19 13:13:53 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
2024-12-19 13:13:53 TLS: tls_multi_process: initial untrusted session promoted to trusted

2024-12-19 13:13:55,058 DEBG 'start-script' stdout output:
2024-12-19 13:13:55 SENT CONTROL [se400.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2024-12-19 13:14:00,292 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 SENT CONTROL [se400.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2024-12-19 13:14:00,302 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 AUTH: Received control message: AUTH_FAILED
2024-12-19 13:14:00 SIGTERM[soft,auth-failure] received, process exiting

2024-12-19 13:14:00,303 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-12-19 13:14:00,309 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 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-12-19 13:14:00 Note: '--allow-compression' is not set to 'no', disabling data channel offload.

2024-12-19 13:14:00,309 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 WARNING: file 'credentials.conf' is group or others accessible
2024-12-19 13:14:00 OpenVPN 2.6.12 [git:makepkg/038a94bae57a446c+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Dec 16 2024
2024-12-19 13:14:00 library versions: OpenSSL 3.4.0 22 Oct 2024, LZO 2.10
2024-12-19 13:14:00 DCO version: N/A

2024-12-19 13:14:00,309 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2024-12-19 13:14:00 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2024-12-19 13:14:00,310 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.209.219:1194

2024-12-19 13:14:00,310 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 Socket Buffers: R=[212992->212992] S=[212992->212992]
2024-12-19 13:14:00 UDPv4 link local: (not bound)
2024-12-19 13:14:00 UDPv4 link remote: [AF_INET]37.120.209.219:1194

2024-12-19 13:14:00,320 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 TLS: Initial packet from [AF_INET]37.120.209.219:1194, sid=14c32d7d 9886ab42

2024-12-19 13:14:00,348 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
2024-12-19 13:14:00 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA9

2024-12-19 13:14:00,348 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 VERIFY KU OK
2024-12-19 13:14:00 Validating certificate extended key usage
2024-12-19 13:14:00 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-12-19 13:14:00 VERIFY EKU OK
2024-12-19 13:14:00 VERIFY OK: depth=0, CN=se400.nordvpn.com

2024-12-19 13:14:00,360 DEBG 'start-script' stdout output:
2024-12-19 13:14:00 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-12-19 13:14:00 [se400.nordvpn.com] Peer Connection Initiated with [AF_INET]37.120.209.219:1194
2024-12-19 13:14:00 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
2024-12-19 13:14:00 TLS: tls_multi_process: initial untrusted session promoted to trusted

2024-12-19 13:14:01,530 DEBG 'start-script' stdout output:
2024-12-19 13:14:01 SENT CONTROL [se400.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2024-12-19 13:14:06,714 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 SENT CONTROL [se400.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2024-12-19 13:14:06,724 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 AUTH: Received control message: AUTH_FAILED
2024-12-19 13:14:06 SIGTERM[soft,auth-failure] received, process exiting

2024-12-19 13:14:06,725 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-12-19 13:14:06,730 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 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-12-19 13:14:06 Note: '--allow-compression' is not set to 'no', disabling data channel offload.

2024-12-19 13:14:06,731 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 WARNING: file 'credentials.conf' is group or others accessible
2024-12-19 13:14:06 OpenVPN 2.6.12 [git:makepkg/038a94bae57a446c+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Dec 16 2024
2024-12-19 13:14:06 library versions: OpenSSL 3.4.0 22 Oct 2024, LZO 2.10
2024-12-19 13:14:06 DCO version: N/A

2024-12-19 13:14:06,731 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2024-12-19 13:14:06 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2024-12-19 13:14:06,732 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.209.219:1194

2024-12-19 13:14:06,732 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 Socket Buffers: R=[212992->212992] S=[212992->212992]
2024-12-19 13:14:06 UDPv4 link local: (not bound)
2024-12-19 13:14:06 UDPv4 link remote: [AF_INET]37.120.209.219:1194

2024-12-19 13:14:06,742 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 TLS: Initial packet from [AF_INET]37.120.209.219:1194, sid=ebb0f883 8c2f96d4

2024-12-19 13:14:06,767 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
2024-12-19 13:14:06 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA9

2024-12-19 13:14:06,768 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 VERIFY KU OK
2024-12-19 13:14:06 Validating certificate extended key usage
2024-12-19 13:14:06 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-12-19 13:14:06 VERIFY EKU OK
2024-12-19 13:14:06 VERIFY OK: depth=0, CN=se400.nordvpn.com

2024-12-19 13:14:06,778 DEBG 'start-script' stdout output:
2024-12-19 13:14:06 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-12-19 13:14:06 [se400.nordvpn.com] Peer Connection Initiated with [AF_INET]37.120.209.219:1194
2024-12-19 13:14:06 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
2024-12-19 13:14:06 TLS: tls_multi_process: initial untrusted session promoted to trusted

 

Upon startup I can see that it is using the correct auth-info (user and pw). I have tried using three different ovpn configs and they all work on windows. Tried restarting the server without any success.

 

If I disable vpn I can get in to the webgui otherwise it times out.

 

Any clue as to why this is happening?

Edited by karleksbarn

Hello, 

 

Great work @binhex I love it please keep it up.

 

I am facing an issue with keeping the container connected to the vpn and the port open. Seems like the port closes or the container loses connection. Is there a way to trigger a reconnection or restart for the container when this happens? 

 

I am using ProtonVPN and wireguard. 

 

Quote


2024-12-20 09:54:58,221 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed

2024-12-20 17:40:26,309 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed

2024-12-21 00:21:28,036 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed
 

 

Hello, everything was working fine until it randomly was not. Now I cannot get the app to open. I reinstalled with no luck. Have included the command execution read out and supervisor log as requested. Anyone have any idea what is going on? Thanks

 

Edited by --Kyle--

  • Author
12 minutes ago, --Kyle-- said:

Hello, everything was working fine until it randomly was not. Now I cannot get the app to open. I reinstalled with no luck. Have included the command execution read out and supervisor log as requested. Anyone have any idea what is going on? Thanks

command execution 1.46 kB · 0 downloads supervisord.log 26.91 kB · 1 download

from your log:-
2024-12-23 09:54:25 [UNDEF] Inactivity timeout (--ping-restart), restarting

Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thank you for taking the time. Apologies for introducing more variables into this, but I have been meaning to switch to Proton and so took this opportunity to do that. I believe I have landed in about the same spot, still cannot load GUI. Posted updated logs below. Thanks again

 

Edited by --Kyle--

I realized that 2 factor auth was giving me authentication issues. I'm now using the bypass info from the Proton dashboard which does not require 2FA. Still cannot launch gui.

 

EDIT: Resolved. Thanks for all you do, Binhex!

Edited by --Kyle--

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

 

supervisord - updated.txt

image.png

Edited by bloom_server
updated the "supervisord.log"

Seeking assistance on my configuration that is throwing me for a loop.

 

I've got 3 subnets,

10.10.10.0/24

10.10.20.0/24 (this is the docker network). Qbittorent at 10.10.20.21

10.10.30.0/24

 

What works:

 

I can connect to the web interface from:

10.10.10.0/24

10.10.30.0/24

ping ONLY from from 10.10.20.0/24 to qbittorent

ping from qbittorent to anything on docker network

 

What doesn't work:

 

I can't connect to the web interface from the docker network. I can pcap on qbittroent docker and see packets coming in and responses leaving, but not making it back to my originating docker container (docker container 1 to qbittorent over tcp does not work)

ping from 10.10.10.0/24 and 10.10.30.0/24 to qbittorent doesn't work.

 

Any thoughts on what the issue is ?

 

I have this configured like this:
image.thumb.png.4d773fc06d948c66bed0906804cb5466.png

 

 

 

image.png

I am with Mullvad and having issues with even accessing the webUI after I enable VPN. I have dropped the conf file that Mullvad generated to the wireguard folder.

 

Some logs below:

2024-12-29 00:50:14,148 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 4 retries left

 

2024-12-29 00:47:38,980 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired 'XX.XX.XX.XX'

 

Questions: Is the above debug IP listed provided by VPN provider?

Having some trouble getting wireguard nordvpn going.  I've got my private key through a ubuntu vm and have disconnected from nordvpn in the VM and the .conf file from https://nord-configs.onrender.com/.  This is the error I'm getting:  Can someone lend me a hand?
 

2024-12-30 17:44:56.904458 [info] Image tags: BASE_RELEASE_TAG=2024110703,INT_RELEASE_TAG=2024110703,IMAGE_RELEASE_TAG=5.0.3-1-01
2024-12-30 17:44:56.987862 [info] PUID defined as '99'
2024-12-30 17:44:57.107871 [info] PGID defined as '100'
2024-12-30 17:44:57.246804 [info] UMASK defined as '000'
2024-12-30 17:44:57.335307 [info] Permissions already set for '/config'
2024-12-30 17:44:57.457932 [info] Deleting files in /tmp (non recursive)...
2024-12-30 17:44:57.570000 [info] VPN_ENABLED defined as 'yes'
2024-12-30 17:44:57.652759 [info] VPN_CLIENT defined as 'wireguard'
2024-12-30 17:44:57.751046 [info] VPN_PROV defined as 'custom'
2024-12-30 17:44:57.876446 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2024-12-30 17:44:57.997686 [crit] VPN configuration file /config/wireguard/wg0.conf does not contain 'Endpoint' line, showing contents of file before exit...
[Interface]
PrivateKey=****
Address=10.5.0.2/16
DNS=103.86.96.100

[Peer]
PublicKey=qIhtTW9K4iXWFo5Q4dOPdXg8/xubXr9yEGoN55D8xnA=
AllowedIPs=0.0.0.0/0,::/0
Endpoint=ca1502.nordvpn.com:51820
PersistentKeepalive=25

** Press ANY KEY to close this window ** 

Edited by ryry

25 minutes ago, ryry said:

configuration file /config/wireguard/wg0.conf does not contain 'Endpoint' line

This is your problem. The endpoint line tells WireGuard where to connect to. You should probably download a new file from NordVPN.

2 minutes ago, wgstarks said:

This is your problem. The endpoint line tells WireGuard where to connect to. You should probably download a new file from NordVPN.

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?

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.