[Support] binhex - qBittorrentVPN


Recommended Posts

7 hours ago, Parakka said:

I added the port number to the VPN_INPUT_PORTS list, and now it is working.

this is not correct, dont do this, taken from my guide:-

'This is used to define input ports for the network of the container, this allows you to access additional applications running in containers that share the VPN network. For example if you had DelugeVPN container running you could bind the network for Sonarr to the DelugeVPN container so that all traffic for Sonarr is then sent down the VPN tunnel encrypted. In order to then access the Sonarr Web UI you would need to define the Sonarr Web UI port using this key.'

 

assigning a incoming port is done at the vpn side and then configured in the app, in this case qbittorrent, thats all there is to it. - note for pia users this is done automatically for you.

  • Thanks 1
Link to comment

@ParakkaI think you might be having the same issue I was over the last few days (scroll up). I saw the same mentions of adding that port in a lot of places. binhex's comment above is what I was told to do too.

 

I think this one could use a clearly updated and identified new process, unless there is one that I never ran across, or couldn't discern from all the others?  Until I got a response here, i didn't see any mention of needing to update from within the app after it's running as opposed to unraid container settings.

 

Thanks for all the help!

Link to comment

Speaking on the VPN_INPUT_PORT key... @binhex following your guide in the FAQ you wrote, I've been able to get Lidarr (my test container before I do this to all my *arr containers) to use qbtvpn's network. I can bash it and pull up the IP and it is the correct VPN IP. But, I've had no luck getting it set to be able to log into the web ui for Lidarr. I've tried a few different things. One, I've added the port 8686 to the VPN_INPUT_PORT key. When I go to the IP:Port, it fails to load. I've tried both leaving the Host Port 1 port (8686) in Lidarr, as well as removing it (as you say in your FAQ). In that same FAQ you talk about using localhost instead of IP, but don't really explain where I'm supposed to add that change. 

 

Can you help with this at all please?

Link to comment

Hi everyone,

 

I have been using the proxy feature for over a year with no issues when suddenly within the last couple of weeks I have started getting "Failed to test proxy" messages in services that are using Privoxy. I looked over the FAQ's and guides and it looks like everything is configured correctly. The weird thing is that if I restart the service, it will work fine for sometime however eventually it will give me a "Failed to test proxy" message and stop working. Any thoughts?

Link to comment
On 12/28/2022 at 5:27 PM, Lonewolf147 said:

Speaking on the VPN_INPUT_PORT key... @binhex following your guide in the FAQ you wrote, I've been able to get Lidarr (my test container before I do this to all my *arr containers) to use qbtvpn's network. I can bash it and pull up the IP and it is the correct VPN IP. But, I've had no luck getting it set to be able to log into the web ui for Lidarr. I've tried a few different things. One, I've added the port 8686 to the VPN_INPUT_PORT key. When I go to the IP:Port, it fails to load. I've tried both leaving the Host Port 1 port (8686) in Lidarr, as well as removing it (as you say in your FAQ). In that same FAQ you talk about using localhost instead of IP, but don't really explain where I'm supposed to add that change. 

 

Can you help with this at all please?

I kept playing around with it and it started to work now. I found that local host has to go in the download client settings of *arr apps.  

I have a new problem though. I have two instances of Lidarr running (to monitor two different music libararies). Each on has it's own port, but the container is still 8686 for each. When I try to set up the second instance of Lidarr with qbvpn, it doesn't let me log in to the Lidarr webui. I can log into the primary instance of it though. Any ideas?

 

Link to comment

I have ProtonVPN and it supports user downloadable Wireguard configs. And I'm trying to run Qbittorrentvpn on a Synology NAS with DSM 7.1. After much troubleshooting, I did manage to get your docker container working. But it's a hack, so I'm hoping there is a more elegant solution.

 

The tl;dr of the solution is that I had to add VPN_DEVICE_TYPE = wg0 to the container environment, or the binhex tunnel up script would not detect that the Wireguard tunnel came up. After I got past the hurdle there is apparently some oddity with how WG works on a Synology. I found a Reddit post (link below) that came to the rescue. It has additional postup/postdown steps that resolved the internet connectivity issue, along with tweaking AllowIPs = 0.0.0.0/1,128.0.0.0/1. 

 

The biggest problem with my hack, is that if I modify the ProtonVPN WG config file to add the needed changes, when the container starts and it creates the wg0.conf file, the custom postup/postdown lines are lost. So I have to modify the wg0.conf file after the container starts and wait for the watchdog process to re-try the tunnel, at which point everything works. Not elegant. 

 

www.reddit. com/r/synology/comments/xkxjfh/fya_how_to_connect_synology_to_a_wireguard_vpn/

 

Hacked solution:

 

Start binhex container, then open the generated wg0.conf file and modify it as follows (note it's important to run the Synology postup/postdown commands BEFORE the binhex inserted commands). Save the config file and wait for the watchdog process to re-try the tunnel, at which point it comes up and life is good. 

 

[Interface]

Table = 2468
PostUp = wg set wg0 fwmark 1234
PostUp = ip rule add not fwmark 1234 table 2468
PostUp = ip rule add table main suppress_prefixlength 0
PostUp = iptables -I FORWARD -i %i -m state --state NEW -j DROP; iptables -t nat -A POSTROUTING -o %i -j MASQUERADE
PostUp = '/root/wireguardup.sh'
PostDown = iptables -D FORWARD -i %i -m state --state NEW -j DROP; iptables -t nat -D POSTROUTING -o %i -j MASQUERADE
PostDown = ip rule del table main suppress_prefixlength 0
PostDown = ip rule del not fwmark 1234 table 2468
PostDown = '/root/wireguarddown.sh'

# Key for qbittorrent
# Bouncing = 5
# NetShield = 0
# Moderate NAT = off
# NAT-PMP (Port Forwarding) = on
# VPN Accelerator = on
PrivateKey = xxxxxx
Address = 10.2.0.2/32
DNS = 1.1.1.1

[Peer]
# CA#21
PublicKey = xxxx
AllowedIPs = 0.0.0.0/1,128.0.0.0/1
Endpoint = xxxxx:51820

 

I'll be the first to admit I have no idea what the additional IP rules do, but they work. Here's the container variables that work:

 

DEBUG true

ENABLE_PRIVOXY yes

HOME /home/nobody

LAN_NETWORK 10.13.2.1/24

LAN Gen_GB.UTF-8

NAME_SERVERS 1.1.1.1

PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

PGID 100

PUID 1024

STRICT_PORT_FORWARD yes

TERM xterm

UMASK 000

VPN_CLIENT wireguard

VPN_DEVICE_TYPE wg0

VPN_ENABLED yes

VPN_INPUT_PORTS 50004

VPN_OUTPUT_PORTS 56780

VPN_PROV protonvpn

WEBUI_PORT 8080

 

The biggest issue is the postup/postdown rules getting lost and for some reason I had to define VPN_DEVICE_TYPE which I didn't see documented anywhere (bug?).

 

Edited by Globe89
updates
Link to comment

Can anyone tell me why I can't access webui?  Everything seems to be loading fine, log attached.

 

12/31/2022 11:21:06 PM
Created by...
12/31/2022 11:21:06 PM
___.   .__       .__
12/31/2022 11:21:06 PM
\_ |__ |__| ____ |  |__   ____ ___  ___
12/31/2022 11:21:06 PM
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
12/31/2022 11:21:06 PM
 | \_\ \  |   |  \   Y  \  ___/ >    <
12/31/2022 11:21:06 PM
 |___  /__|___|  /___|  /\___  >__/\_ \
12/31/2022 11:21:06 PM
     \/        \/     \/     \/      \/
12/31/2022 11:21:06 PM
   https://hub.docker.com/u/binhex/
12/31/2022 11:21:06 PM
12/31/2022 11:21:06 PM
2022-12-31 23:21:06.926435 [info] System information Linux 8459f3bb2289 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 GNU/Linux
12/31/2022 11:21:06 PM
2022-12-31 23:21:06.966197 [info] OS_ARCH defined as 'x86-64'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.008423 [info] PUID defined as '1000'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.056049 [info] PGID defined as '1000'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.102230 [info] UMASK defined as '000'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.136143 [info] Permissions already set for '/config'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.186579 [info] Deleting files in /tmp (non recursive)...
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.231188 [info] VPN_ENABLED defined as 'yes'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.271041 [info] VPN_CLIENT defined as 'wireguard'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.306170 [info] VPN_PROV defined as 'pia'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.468557 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.529349 [info] VPN_REMOTE_SERVER defined as 'nl-amsterdam.privacy.network'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.609340 [info] VPN_REMOTE_PORT defined as '1337'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.644955 [info] VPN_DEVICE_TYPE defined as 'wg0'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.680386 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.718838 [info] LAN_NETWORK defined as '192.168.0.1/24'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.757340 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.797117 [info] VPN_USER defined as 'xxxxxxxxx'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.837698 [info] VPN_PASS defined as 'xxxxxxxxx'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.879612 [info] STRICT_PORT_FORWARD defined as 'yes'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.921280 [info] ENABLE_PRIVOXY defined as 'yes'
12/31/2022 11:21:07 PM
2022-12-31 23:21:07.970186 [info] VPN_INPUT_PORTS defined as '1234'
12/31/2022 11:21:08 PM
2022-12-31 23:21:08.012937 [info] VPN_OUTPUT_PORTS defined as '5678'
12/31/2022 11:21:08 PM
2022-12-31 23:21:08.055195 [info] WEBUI_PORT defined as '7070'
12/31/2022 11:21:08 PM
2022-12-31 23:21:08.141987 [info] Starting Supervisor...
12/31/2022 11:21:08 PM
2022-12-31 23:21:08,493 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
12/31/2022 11:21:08 PM
2022-12-31 23:21:08,493 INFO Set uid to user 0 succeeded
12/31/2022 11:21:08 PM
2022-12-31 23:21:08,495 INFO supervisord started with pid 7
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,507 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,507 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,511 DEBG 'watchdog-script' stdout output:
12/31/2022 11:21:09 PM
[info] qBittorrent config file already exists, skipping copy
12/31/2022 11:21:09 PM
[info] Removing session lock file (if it exists)...
12/31/2022 11:21:09 PM
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,512 DEBG 'start-script' stdout output:
12/31/2022 11:21:09 PM
[info] Adding 84.200.69.80 to /etc/resolv.conf
12/31/2022 11:21:09 PM
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,516 DEBG 'start-script' stdout output:
12/31/2022 11:21:09 PM
[info] Adding 37.235.1.174 to /etc/resolv.conf
12/31/2022 11:21:09 PM
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,521 DEBG 'start-script' stdout output:
12/31/2022 11:21:09 PM
[info] Adding 1.1.1.1 to /etc/resolv.conf
12/31/2022 11:21:09 PM
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,525 DEBG 'start-script' stdout output:
12/31/2022 11:21:09 PM
[info] Adding 37.235.1.177 to /etc/resolv.conf
12/31/2022 11:21:09 PM
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,529 DEBG 'start-script' stdout output:
12/31/2022 11:21:09 PM
[info] Adding 84.200.70.40 to /etc/resolv.conf
12/31/2022 11:21:09 PM
12/31/2022 11:21:09 PM
2022-12-31 23:21:09,534 DEBG 'start-script' stdout output:
12/31/2022 11:21:09 PM
[info] Adding 1.0.0.1 to /etc/resolv.conf
12/31/2022 11:21:09 PM
12/31/2022 11:21:47 PM
2022-12-31 23:21:47,766 DEBG 'start-script' stdout output:
12/31/2022 11:21:47 PM
[info] Token generated for PIA wireguard authentication
12/31/2022 11:21:47 PM
12/31/2022 11:21:47 PM
2022-12-31 23:21:47,808 DEBG 'start-script' stdout output:
12/31/2022 11:21:47 PM
[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'...
12/31/2022 11:21:47 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,232 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
[info] Default route for container is 172.17.0.1
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,430 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
[info] Docker network defined as    172.17.0.0/16
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,436 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
[info] Adding 192.168.0.1/24 as route via docker eth0
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,438 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
Error: Invalid prefix for given prefix length.
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,439 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
[info] ip route defined as follows...
12/31/2022 11:21:48 PM
--------------------
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,440 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
default via 172.17.0.1 dev eth0 
12/31/2022 11:21:48 PM
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.8 
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,441 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
12/31/2022 11:21:48 PM
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
12/31/2022 11:21:48 PM
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
12/31/2022 11:21:48 PM
local 172.17.0.8 dev eth0 table local proto kernel scope host src 172.17.0.8 
12/31/2022 11:21:48 PM
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.8 
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,441 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
--------------------
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,450 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
iptable_mangle         16384  0
12/31/2022 11:21:48 PM
ip_tables              32768  2 iptable_filter,iptable_mangle
12/31/2022 11:21:48 PM
x_tables               53248  10 xt_conntrack,iptable_filter,nft_compat,xt_tcpudp,xt_addrtype,xt_nat,ip_tables,xt_MASQUERADE,iptable_mangle,xt_mark
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,450 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
[info] iptable_mangle support detected, adding fwmark for tables
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,580 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
[info] iptables defined as follows...
12/31/2022 11:21:48 PM
--------------------
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,582 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
-P INPUT DROP
12/31/2022 11:21:48 PM
-P FORWARD DROP
12/31/2022 11:21:48 PM
-P OUTPUT DROP
12/31/2022 11:21:48 PM
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -s 154.47.21.177/32 -i eth0 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -s 195.78.54.81/32 -i eth0 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -s 195.78.54.225/32 -i eth0 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -i eth0 -p tcp -m tcp --dport 7070 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -i eth0 -p udp -m udp --dport 7070 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -i eth0 -p tcp -m tcp --dport 1234 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -i eth0 -p udp -m udp --dport 1234 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --sport 5678 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -i lo -j ACCEPT
12/31/2022 11:21:48 PM
-A INPUT -i wg0 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -d 154.47.21.177/32 -o eth0 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -d 195.78.54.81/32 -o eth0 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -d 195.78.54.225/32 -o eth0 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -o eth0 -p tcp -m tcp --sport 7070 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -o eth0 -p udp -m udp --sport 7070 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -o eth0 -p tcp -m tcp --sport 1234 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -o eth0 -p udp -m udp --sport 1234 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --dport 5678 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -o lo -j ACCEPT
12/31/2022 11:21:48 PM
-A OUTPUT -o wg0 -j ACCEPT
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,584 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
--------------------
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,588 DEBG 'start-script' stdout output:
12/31/2022 11:21:48 PM
[info] Attempting to bring WireGuard interface 'up'...
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,600 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
Warning: `/config/wireguard/wg0.conf' is world accessible
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,608 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] ip link add wg0 type wireguard
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,611 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] wg setconf wg0 /dev/fd/63
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,615 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] ip -4 address add 10.48.233.245 dev wg0
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,624 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] ip link set mtu 1420 up dev wg0
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,638 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] wg set wg0 fwmark 51820
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,640 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,642 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] ip -4 rule add not fwmark 51820 table 51820
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,644 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] ip -4 rule add table main suppress_prefixlength 0
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,649 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,651 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] iptables-restore -n
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,741 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
[#] '/root/wireguardup.sh'
12/31/2022 11:21:48 PM
12/31/2022 11:21:48 PM
2022-12-31 23:21:48,773 DEBG 'start-script' stderr output:
12/31/2022 11:21:48 PM
egrep: warning: egrep is obsolescent; using grep -E
12/31/2022 11:21:48 PM
12/31/2022 11:21:49 PM
2022-12-31 23:21:49,782 DEBG 'start-script' stderr output:
12/31/2022 11:21:49 PM
egrep: warning: egrep is obsolescent; using grep -E
12/31/2022 11:21:49 PM
12/31/2022 11:21:49 PM
2022-12-31 23:21:49,792 DEBG 'start-script' stderr output:
12/31/2022 11:21:49 PM
egrep: warning: egrep is obsolescent; using grep -E
12/31/2022 11:21:49 PM
12/31/2022 11:21:49 PM
2022-12-31 23:21:49,988 DEBG 'start-script' stdout output:
12/31/2022 11:21:49 PM
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...
12/31/2022 11:21:49 PM
12/31/2022 11:21:58 PM
2022-12-31 23:21:58,316 DEBG 'start-script' stderr output:
12/31/2022 11:21:58 PM
egrep: warning: egrep is obsolescent; using grep -E
12/31/2022 11:21:58 PM
12/31/2022 11:21:58 PM
2022-12-31 23:21:58,322 DEBG 'start-script' stdout output:
12/31/2022 11:21:58 PM
[info] Successfully retrieved external IP address 154.47.21.177
12/31/2022 11:21:58 PM
12/31/2022 11:21:58 PM
2022-12-31 23:21:58,324 DEBG 'start-script' stdout output:
12/31/2022 11:21:58 PM
[info] WireGuard interface 'up'
12/31/2022 11:21:58 PM
12/31/2022 11:21:58 PM
2022-12-31 23:21:58,341 DEBG 'start-script' stdout output:
12/31/2022 11:21:58 PM
[info] Script started to assign incoming port
12/31/2022 11:21:58 PM
12/31/2022 11:21:58 PM
2022-12-31 23:21:58,341 DEBG 'start-script' stdout output:
12/31/2022 11:21:58 PM
[info] Port forwarding is enabled
12/31/2022 11:21:58 PM
[info] Checking endpoint 'nl-amsterdam.privacy.network' is port forward enabled...
12/31/2022 11:21:58 PM
12/31/2022 11:22:06 PM
2022-12-31 23:22:06,935 DEBG 'start-script' stdout output:
12/31/2022 11:22:06 PM
[info] PIA endpoint 'nl-amsterdam.privacy.network' is in the list of endpoints that support port forwarding
12/31/2022 11:22:06 PM
12/31/2022 11:22:06 PM
2022-12-31 23:22:06,937 DEBG 'start-script' stdout output:
12/31/2022 11:22:06 PM
[info] List of PIA endpoints that support port forwarding:-
12/31/2022 11:22:06 PM
12/31/2022 11:22:06 PM
2022-12-31 23:22:06,937 DEBG 'start-script' stdout output:
12/31/2022 11:22:06 PM
[info] mexico.privacy.network
12/31/2022 11:22:06 PM
[info] uk-2.privacy.network
12/31/2022 11:22:06 PM
12/31/2022 11:22:06 PM
2022-12-31 23:22:06,937 DEBG 'start-script' stdout output:
12/31/2022 11:22:06 PM
[info] cambodia.privacy.network
12/31/2022 11:22:06 PM
[info] bogota.privacy.network
12/31/2022 11:22:06 PM
[info] tr.privacy.network
12/31/2022 11:22:06 PM
[info] santiago.privacy.network
12/31/2022 11:22:06 PM
[info] uk-london.privacy.network
12/31/2022 11:22:06 PM
[info] venezuela.privacy.network
12/31/2022 11:22:06 PM
[info] brussels.privacy.network
12/31/2022 11:22:06 PM
[info] czech.privacy.network
12/31/2022 11:22:06 PM
[info] france.privacy.network
12/31/2022 11:22:06 PM
[info] kualalumpur.privacy.network
12/31/2022 11:22:06 PM
[info] kazakhstan.privacy.network
12/31/2022 11:22:06 PM
[info] egypt.privacy.network
12/31/2022 11:22:06 PM
[info] morocco.privacy.network
12/31/2022 11:22:06 PM
[info] in.privacy.network
12/31/2022 11:22:06 PM
[info] panama.privacy.network
12/31/2022 11:22:06 PM
[info] mongolia.privacy.network
12/31/2022 11:22:06 PM
[info] swiss.privacy.network
12/31/2022 11:22:06 PM
[info] hk.privacy.network
12/31/2022 11:22:06 PM
[info] hungary.privacy.network
12/31/2022 11:22:06 PM
[info] ee.privacy.network
12/31/2022 11:22:06 PM
[info] israel.privacy.network
12/31/2022 11:22:06 PM
[info] man.privacy.network
12/31/2022 11:22:06 PM
12/31/2022 11:22:06 PM
2022-12-31 23:22:06,938 DEBG 'start-script' stdout output:
12/31/2022 11:22:06 PM
[info] sweden-2.privacy.network
12/31/2022 11:22:06 PM
[info] yerevan.privacy.network
12/31/2022 11:22:06 PM
[info] lu.privacy.network
12/31/2022 11:22:06 PM
[info] philippines.privacy.network
12/31/2022 11:22:06 PM
[info] ca-toronto.privacy.network
12/31/2022 11:22:06 PM
[info] zagreb.privacy.network
12/31/2022 11:22:06 PM
[info] italy.privacy.network
12/31/2022 11:22:06 PM
[info] taiwan.privacy.network
12/31/2022 11:22:06 PM
[info] malta.privacy.network
12/31/2022 11:22:06 PM
[info] lv.privacy.network
12/31/2022 11:22:06 PM
[info] sweden.privacy.network
12/31/2022 11:22:06 PM
[info] vietnam.privacy.network
12/31/2022 11:22:06 PM
[info] nigeria.privacy.network
12/31/2022 11:22:06 PM
[info] sg.privacy.network
12/31/2022 11:22:06 PM
[info] cyprus.privacy.network
12/31/2022 11:22:06 PM
[info] rs.privacy.network
12/31/2022 11:22:06 PM
[info] denmark.privacy.network
12/31/2022 11:22:06 PM
[info] denmark-2.privacy.network
12/31/2022 11:22:06 PM
[info] ca-montreal.privacy.network
12/31/2022 11:22:06 PM
[info] ca-ontario.privacy.network
12/31/2022 11:22:06 PM
[info] ua.privacy.network
12/31/2022 11:22:06 PM
[info] lt.privacy.network
12/31/2022 11:22:06 PM
[info] de-berlin.privacy.network
12/31/2022 11:22:06 PM
[info] za.privacy.network
12/31/2022 11:22:06 PM
[info] dz.privacy.network
12/31/2022 11:22:06 PM
[info] nl-amsterdam.privacy.network
12/31/2022 11:22:06 PM
[info] liechtenstein.privacy.network
12/31/2022 11:22:06 PM
[info] uk-southampton.privacy.network
12/31/2022 11:22:06 PM
12/31/2022 11:22:06 PM
2022-12-31 23:22:06,938 DEBG 'start-script' stdout output:
12/31/2022 11:22:06 PM
[info] sk.privacy.network
12/31/2022 11:22:06 PM
[info] china.privacy.network
12/31/2022 11:22:06 PM
[info] japan-2.privacy.network
12/31/2022 11:22:06 PM
[info] japan.privacy.network
12/31/2022 11:22:06 PM
[info] spain.privacy.network
12/31/2022 11:22:06 PM
[info] ad.privacy.network
12/31/2022 11:22:06 PM
[info] au-australia-so.privacy.network
12/31/2022 11:22:06 PM
[info] ca-vancouver.privacy.network
12/31/2022 11:22:06 PM
[info] sanjose.privacy.network
12/31/2022 11:22:06 PM
[info] fi.privacy.network
12/31/2022 11:22:06 PM
[info] jakarta.privacy.network
12/31/2022 11:22:06 PM
[info] bahamas.privacy.network
12/31/2022 11:22:06 PM
[info] md.privacy.network
12/31/2022 11:22:06 PM
[info] ro.privacy.network
12/31/2022 11:22:06 PM
[info] bangladesh.privacy.network
12/31/2022 11:22:06 PM
[info] au-sydney.privacy.network
12/31/2022 11:22:06 PM
[info] ireland.privacy.network
12/31/2022 11:22:06 PM
[info] ae.privacy.network
12/31/2022 11:22:06 PM
[info] srilanka.privacy.network
12/31/2022 11:22:06 PM
[info] de-frankfurt.privacy.network
12/31/2022 11:22:06 PM
[info] monaco.privacy.network
12/31/2022 11:22:06 PM
[info] aus-perth.privacy.network
12/31/2022 11:22:06 PM
[info] qatar.privacy.network
12/31/2022 11:22:06 PM
12/31/2022 11:22:06 PM
2022-12-31 23:22:06,938 DEBG 'start-script' stdout output:
12/31/2022 11:22:06 PM
[info] es-valencia.privacy.network
12/31/2022 11:22:06 PM
[info] slovenia.privacy.network
12/31/2022 11:22:06 PM
[info] italy-2.privacy.network
12/31/2022 11:22:06 PM
[info] poland.privacy.network
12/31/2022 11:22:06 PM
[info] austria.privacy.network
12/31/2022 11:22:06 PM
[info] br.privacy.network
12/31/2022 11:22:06 PM
[info] georgia.privacy.network
12/31/2022 11:22:06 PM
[info] aus-melbourne.privacy.network
12/31/2022 11:22:06 PM
[info] ar.privacy.network
12/31/2022 11:22:06 PM
[info] saudiarabia.privacy.network
12/31/2022 11:22:06 PM
[info] sofia.privacy.network
12/31/2022 11:22:06 PM
[info] gr.privacy.network
12/31/2022 11:22:06 PM
[info] mk.privacy.network
12/31/2022 11:22:06 PM
[info] macau.privacy.network
12/31/2022 11:22:06 PM
[info] uk-manchester.privacy.network
12/31/2022 11:22:06 PM
[info] montenegro.privacy.network
12/31/2022 11:22:06 PM
[info] pt.privacy.network
12/31/2022 11:22:06 PM
[info] fi-2.privacy.network
12/31/2022 11:22:06 PM
[info] greenland.privacy.network
12/31/2022 11:22:06 PM
[info] ba.privacy.network
12/31/2022 11:22:06 PM
[info] no.privacy.network
12/31/2022 11:22:06 PM
[info] is.privacy.network
12/31/2022 11:22:06 PM
[info] al.privacy.network
12/31/2022 11:22:06 PM
[info] nz.privacy.network
12/31/2022 11:22:06 PM
12/31/2022 11:22:06 PM
2022-12-31 23:22:06,941 DEBG 'start-script' stderr output:
12/31/2022 11:22:06 PM
egrep: warning: egrep is obsolescent; using grep -E
12/31/2022 11:22:06 PM
12/31/2022 11:22:07 PM
2022-12-31 23:22:07,949 DEBG 'start-script' stderr output:
12/31/2022 11:22:07 PM
egrep: warning: egrep is obsolescent; using grep -E
12/31/2022 11:22:07 PM
12/31/2022 11:22:07 PM
2022-12-31 23:22:07,960 DEBG 'start-script' stderr output:
12/31/2022 11:22:07 PM
egrep: warning: egrep is obsolescent; using grep -E
12/31/2022 11:22:07 PM
12/31/2022 11:22:17 PM
2022-12-31 23:22:17,563 DEBG 'start-script' stdout output:
12/31/2022 11:22:17 PM
[info] Successfully assigned and bound incoming port '53274'
12/31/2022 11:22:17 PM
12/31/2022 11:22:38 PM
2022-12-31 23:22:38,071 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:38 PM
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.48.233.245 different, marking for reconfigure
12/31/2022 11:22:38 PM
12/31/2022 11:22:38 PM
2022-12-31 23:22:38,169 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:38 PM
[info] qBittorrent not running
12/31/2022 11:22:38 PM
12/31/2022 11:22:38 PM
2022-12-31 23:22:38,173 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:38 PM
[info] Privoxy not running
12/31/2022 11:22:38 PM
12/31/2022 11:22:38 PM
2022-12-31 23:22:38,174 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:38 PM
[info] qBittorrent incoming port 6881 and VPN incoming port 53274 different, marking for reconfigure
12/31/2022 11:22:38 PM
12/31/2022 11:22:38 PM
2022-12-31 23:22:38,174 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:38 PM
[info] Removing session lock file (if it exists)...
12/31/2022 11:22:38 PM
12/31/2022 11:22:38 PM
2022-12-31 23:22:38,183 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:38 PM
[info] Attempting to start qBittorrent...
12/31/2022 11:22:38 PM
12/31/2022 11:22:38 PM
2022-12-31 23:22:38,941 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:38 PM
[info] qBittorrent process started
12/31/2022 11:22:38 PM
[info] Waiting for qBittorrent process to start listening on port 7070...
12/31/2022 11:22:38 PM
12/31/2022 11:22:39 PM
2022-12-31 23:22:39,528 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:39 PM
[info] qBittorrent process listening on port 7070
12/31/2022 11:22:39 PM
12/31/2022 11:22:39 PM
2022-12-31 23:22:39,622 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:39 PM
[info] Attempting to start Privoxy...
12/31/2022 11:22:39 PM
12/31/2022 11:22:40 PM
2022-12-31 23:22:40,662 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:40 PM
[info] Privoxy process started
12/31/2022 11:22:40 PM
[info] Waiting for Privoxy process to start listening on port 8118...
12/31/2022 11:22:40 PM
12/31/2022 11:22:40 PM
2022-12-31 23:22:40,670 DEBG 'watchdog-script' stdout output:
12/31/2022 11:22:40 PM
[info] Privoxy process listening on port 8118
12/31/2022 11:22:40 PM

 

Link to comment

I've stayed at 4.3.9 for a while after the 4.4.0 debacle and am finally considering moving to 4.4.5. I'm assuming it will try to reset my settings again as I see others are still facing this issue in the last few pages.

 

Is there any simple way to combat the settings reset or am I stuck setting everything back up from scratch? I assume my old qbit config will be overwritten each time I place it in the config folder and start the container since that's what happened last time. Is the only option to rebuild it via the UI following the upgrade?

Link to comment
4 hours ago, BrttClne22 said:

I've stayed at 4.3.9 for a while after the 4.4.0 debacle and am finally considering moving to 4.4.5. I'm assuming it will try to reset my settings again as I see others are still facing this issue in the last few pages.

 

Is there any simple way to combat the settings reset or am I stuck setting everything back up from scratch? I assume my old qbit config will be overwritten each time I place it in the config folder and start the container since that's what happened last time. Is the only option to rebuild it via the UI following the upgrade?

I have always been able to manually restore the correct download settings after the update. Haven’t had the issue with the most recent updates. Doesn’t mean that others haven’t had a Robles though. Current on 4.5.0.

Link to comment
2 hours ago, wgstarks said:

I see that you have changed the webUI port number. Did you follow the instructions?

 https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Scroll down to Q4.

Thank you for the reply, I don't actually use Unraid, I'm using the container on docker with an Ubuntu 22.04 host.  As you can see from the logs, however, the container runs fine.  I have ensured that the webui environment variable port matches the host (7070); for what it's worth, however, I don't get the webui if I leave everything at 8080.   When I try to access the webui, however, the request eventually times out.  What is odd is that a check from an -arr (radarr, sonarr) will find Qbittorrent.  Should have included this before, here is my docker run command:

docker run -d \
    --sysctl="net.ipv4.conf.all.src_valid_mark=1" \
    --privileged=true \
    -p 6881:6881 \
    -p 6881:6881/udp \
    -p 7070:7070 \
    -p 8118:8118 \
    --name=qbittorrentvpn \
    -v /root/docker/data:/data \
    -v /root/docker/config:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e VPN_ENABLED=yes \
    -e VPN_USER=pxxxxxxxxx \
    -e VPN_PASS=xxxxxxxxxx \
    -e VPN_PROV=pia \
    -e VPN_CLIENT=wireguard \
    -e STRICT_PORT_FORWARD=yes \
    -e ENABLE_PRIVOXY=no \
    -e LAN_NETWORK=192.168.0.1/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=1234 \
    -e VPN_OUTPUT_PORTS=5678 \
    -e DEBUG=false \
    -e WEBUI_PORT=7070 \
    -e UMASK=000 \
    -e PUID=1000 \
    -e PGID=1000 \
    binhex/arch-qbittorrentvpn

 

Link to comment
28 minutes ago, wgstarks said:

The docker is running so the arrs can connect. Are you trying to access from the same LAN?

Yes.  Server is running on my r710, and I'm just trying to connect from my desktop on same LAN.  I have another container running qb (routed through a Gluetun container), and that webui works fine.   I'd just rather be using wireguard.

Link to comment
1 hour ago, cthog said:

Well, *that's* embarrassing.  I know better, but missed it.  Thanks so much for catching it, and thank you for the great work on your container.  Up and running with wg.  Thank you to wgstarks as well for jumping in.

 

--Chris

I missed it too. 🤦‍♂️

  • Like 1
Link to comment
On 12/29/2022 at 10:15 PM, davbay1 said:

Hi everyone,

 

I have been using the proxy feature for over a year with no issues when suddenly within the last couple of weeks I have started getting "Failed to test proxy" messages in services that are using Privoxy. I looked over the FAQ's and guides and it looks like everything is configured correctly. The weird thing is that if I restart the service, it will work fine for sometime however eventually it will give me a "Failed to test proxy" message and stop working. Any thoughts?

 

Same here but I'm using SABNZBDvpn docker. Are you using PIA VPN? 

Once I disable proxy in the settings everything connects just fine.

Link to comment
On 12/31/2022 at 6:10 AM, Globe89 said:

I have ProtonVPN and it supports user downloadable Wireguard configs. And I'm trying to run Qbittorrentvpn on a Synology NAS with DSM 7.1. After much troubleshooting, I did manage to get your docker container working. But it's a hack, so I'm hoping there is a more elegant solution.

 

The tl;dr of the solution is that I had to add VPN_DEVICE_TYPE = wg0 to the container environment, or the binhex tunnel up script would not detect that the Wireguard tunnel came up. After I got past the hurdle there is apparently some oddity with how WG works on a Synology. I found a Reddit post (link below) that came to the rescue. It has additional postup/postdown steps that resolved the internet connectivity issue, along with tweaking AllowIPs = 0.0.0.0/1,128.0.0.0/1. 

 

The biggest problem with my hack, is that if I modify the ProtonVPN WG config file to add the needed changes, when the container starts and it creates the wg0.conf file, the custom postup/postdown lines are lost. So I have to modify the wg0.conf file after the container starts and wait for the watchdog process to re-try the tunnel, at which point everything works. Not elegant. 

 

www.reddit. com/r/synology/comments/xkxjfh/fya_how_to_connect_synology_to_a_wireguard_vpn/

 

Hacked solution:

 

Start binhex container, then open the generated wg0.conf file and modify it as follows (note it's important to run the Synology postup/postdown commands BEFORE the binhex inserted commands). Save the config file and wait for the watchdog process to re-try the tunnel, at which point it comes up and life is good. 

 

[Interface]

Table = 2468
PostUp = wg set wg0 fwmark 1234
PostUp = ip rule add not fwmark 1234 table 2468
PostUp = ip rule add table main suppress_prefixlength 0
PostUp = iptables -I FORWARD -i %i -m state --state NEW -j DROP; iptables -t nat -A POSTROUTING -o %i -j MASQUERADE
PostUp = '/root/wireguardup.sh'
PostDown = iptables -D FORWARD -i %i -m state --state NEW -j DROP; iptables -t nat -D POSTROUTING -o %i -j MASQUERADE
PostDown = ip rule del table main suppress_prefixlength 0
PostDown = ip rule del not fwmark 1234 table 2468
PostDown = '/root/wireguarddown.sh'

# Key for qbittorrent
# Bouncing = 5
# NetShield = 0
# Moderate NAT = off
# NAT-PMP (Port Forwarding) = on
# VPN Accelerator = on
PrivateKey = xxxxxx
Address = 10.2.0.2/32
DNS = 1.1.1.1

[Peer]
# CA#21
PublicKey = xxxx
AllowedIPs = 0.0.0.0/1,128.0.0.0/1
Endpoint = xxxxx:51820

 

I'll be the first to admit I have no idea what the additional IP rules do, but they work. Here's the container variables that work:

 

DEBUG true

ENABLE_PRIVOXY yes

HOME /home/nobody

LAN_NETWORK 10.13.2.1/24

LAN Gen_GB.UTF-8

NAME_SERVERS 1.1.1.1

PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

PGID 100

PUID 1024

STRICT_PORT_FORWARD yes

TERM xterm

UMASK 000

VPN_CLIENT wireguard

VPN_DEVICE_TYPE wg0

VPN_ENABLED yes

VPN_INPUT_PORTS 50004

VPN_OUTPUT_PORTS 56780

VPN_PROV protonvpn

WEBUI_PORT 8080

 

The biggest issue is the postup/postdown rules getting lost and for some reason I had to define VPN_DEVICE_TYPE which I didn't see documented anywhere (bug?).

 

@binhex Any ideas on how this can be resolved? Seems like the container startup scripts that modify wg0.conf need a bit more logic added.

Link to comment

I too have trouble accessing the GUI.

The VPN worked, but it stopped in the meantime. 

 

Here is the config for the container:

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='swagproxy'
  --ip='172.18.0.55'
  --privileged=true
  -e TZ="Europe/Budapest"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="MARVIN"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='XXXXXX'
  -e 'VPN_PASS'='XXXXXX'
  -e 'VPN_PROV'='custom'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='yes'
  -e 'WEBUI_PORT'='8116'
  -e 'LAN_NETWORK'='192.168.42.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:8116]/'
  -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 '8116:8080/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'
472b97658a6912de72f09983597e5e10396a903086b61288959d8968f13fdb86

If anybody has ideas, let me know.

Edited by Forty Two
Link to comment
6 minutes ago, Forty Two said:

Thanks!

I don't have that option in the gui? How would I go about changing that setting?

Assuming you are running this docker on unraid, go to the docker tab and click the name of this docker to view/edit the configuration.

14265538_Screenshot2023-01-02at11_33_50AM.thumb.png.b69b789f4b735a2ac69a8b77271ec7f6.png

 

Find the entry for that port (on mine it’s host port 3) and delete it.

Select add a new path at the bottom of the page. Set config type to port. Name can be whatever you want. Host Port and Container Port should both match webui port (8116). Description and Default value are optional. Connection type will be TCP.

Click “Save” and then “Apply”.

Link to comment
28 minutes ago, wgstarks said:

Assuming you are running this docker on unraid, go to the docker tab and click the name of this docker to view/edit the configuration.

14265538_Screenshot2023-01-02at11_33_50AM.thumb.png.b69b789f4b735a2ac69a8b77271ec7f6.png

 

Find the entry for that port (on mine it’s host port 3) and delete it.

Select add a new path at the bottom of the page. Set config type to port. Name can be whatever you want. Host Port and Container Port should both match webui port (8116). Description and Default value are optional. Connection type will be TCP.

Click “Save” and then “Apply”.

Thanks,

 

I am indeed running UnRaid. 

I've run into similar difficulties with Deluge, and decided to switch, as Qbittorrent has a better gui anyway. 

 

Here is how that looks now:

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='swagproxy'
  --ip='172.18.0.55'
  --privileged=true
  -e TZ="Europe/Budapest"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="MARVIN"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='XXXXXXXX'
  -e 'VPN_PASS'='XXXXXXXX'
  -e 'VPN_PROV'='custom'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='yes'
  -e 'WEBUI_PORT'='8116'
  -e 'LAN_NETWORK'='192.168.42.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:8116]/'
  -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 '8118:8118/tcp'
  -p '8116:8116/tcp'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'
6ae71aedc744cddfe750d687c842587862458728cdc225513e1f367db68c8af5

The command finished successfully!

Still no access to the UI. 

The browser says "This site can’t be reached"

Edited by Forty Two
Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.