[Support] binhex - qBittorrentVPN


binhex

Recommended Posts

On 7/4/2021 at 6:16 AM, GuitaristTom said:

I lost power at my house today, and for some reason my qBittorrent config file reset. A friend of mine has a similar issue.

 

It's fine if the container is stopped and restarted normally, it's just if the power is cut to the server while the container itself is running.

 

All of the stats remained, it was just the config file that reset.

 

This happens to me after powerloss reset as well.

I run a daily backup of this docker so I can restore normally, one of the most annoying things is the way it moves all my torrents into it's docker folder because it forgets all the category mapping.

Link to comment
On 7/11/2021 at 5:49 PM, samba_69 said:

Hey! I have been using binhex-qbittorrent  for a month and it was butter smooth!

I was using Custom Wireguard config to connect to my VPN network. Everything was okaish, except the speed, for which I decided to move to a new VPN provider (Surfshark)

The new VPN provider provides openvpn configurations to users which gives acceptable speed for me. 
Thus I changed VPN_CLIENT to openvpn, and uploaded the .opvn file in config/openvpn (/mnt/user/appdata/binhex-qbittorrentvpn/openvpn) folder. 

In short
I made the following change:
VPN_CLIENT changed from wirequard to openvpn. I have also change the vpn files, but

With the following change:
1. I can access WebUI and download using my new VPN configuration
2. I cannot connect qbittorrent from sonaar/radaar. They always fails if VPN_CLIENT is set ot openvpn
    The problem gets resoved once I switch back to wiregurad.

Any solution to this?

Follow up repost!
Any senior member here who can address this?

I cannot connect to qbittorrent APIs when using custom open vpn as vpn of choice!

Link to comment
  • 2 weeks later...

hi everyone, i've been trying to make sense of the whole docker configuration thing but i encounter many search results stating that once the docker runs, qbittorrent should just work

however, i've been trying all night to figure it out, since apparently, on my unraid machine, qbittorrent does not appear to communicate with internet at all : trackers are  "not working" and connectivity icon is the little flame etc

no VPN set up for now ( curently my attempts only make me lose webui acess..)
network type bridge or custom with static IP
all docker settings defaults except share path access

Unraid itself has no problem downloading or updating anything from outside LAN
Deluge docker does connect out of the box so i guess the problem is limited to my qbittorrent docker's config somewhere...

 

 

[EDIT] i tried out of cursiosity the basic LINUXSERVER.IO version of qbittorrent and it does connect, so what could be limiting the binhex's VPN enhanced version?

Edited by Nickie
Link to comment
21 hours ago, Nickie said:

no VPN set up for now ( curently my attempts only make me lose webui acess..)
network type bridge or custom with static IP
all docker settings defaults except share path access

if you have vpn_enabled set to no then it should simply be a case of port forwarding on your router, then set qbittorrent to use the same port as you port forwarded.

Link to comment
On 12/29/2020 at 12:28 AM, kim_sv said:

I'm running this in qBit:

but it doesn't work if there is a season pack like you describe. I've just copy pasted the code from some thread in the forum. Does your code do anything else but extract the file to the same folder as the .rar files?

Hi

 

Did you crack unpacking season packs?


Thanks

Link to comment

@binhex I've taken your advice and I'm giving qbittorrentvpn another go.  But, I'm stuck right at the start as I can't get the webui http://192.168.1.81:8080/ to load - any ideas?  Thanks

 

ErrorWarningSystemArrayLogin


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

2021-08-04 10:20:02.743555 [info] Host is running unRAID
2021-08-04 10:20:02.765052 [info] System information Linux a3351c613287 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2021-08-04 10:20:02.789918 [info] OS_ARCH defined as 'x86-64'
2021-08-04 10:20:02.814062 [info] PUID defined as '99'
2021-08-04 10:20:02.942450 [info] PGID defined as '100'
2021-08-04 10:20:02.982983 [info] UMASK defined as '000'
2021-08-04 10:20:03.005662 [info] Permissions already set for volume mappings
2021-08-04 10:20:03.030413 [info] Deleting files in /tmp (non recursive)...
2021-08-04 10:20:03.057839 [info] VPN_ENABLED defined as 'no'
2021-08-04 10:20:03.078248 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2021-08-04 10:20:03.101931 [info] WEBUI_PORT defined as '8084'
2021-08-04 10:20:03.411356 [info] Starting Supervisor...
2021-08-04 10:20:03,551 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2021-08-04 10:20:03,551 INFO Set uid to user 0 succeeded
2021-08-04 10:20:03,554 INFO supervisord started with pid 8
2021-08-04 10:20:04,556 INFO spawned: 'shutdown-script' with pid 80
2021-08-04 10:20:04,557 INFO spawned: 'start-script' with pid 81
2021-08-04 10:20:04,559 INFO spawned: 'watchdog-script' with pid 82
2021-08-04 10:20:04,559 INFO reaped unknown pid 9 (exit status 0)
2021-08-04 10:20:04,565 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2021-08-04 10:20:04,566 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22399161397648 for <Subprocess at 22399161202912 with name start-script in state STARTING> (stderr)>
2021-08-04 10:20:04,566 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-04 10:20:04,566 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-04 10:20:04,566 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-04 10:20:04,566 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22399161203584 for <Subprocess at 22399161202912 with name start-script in state RUNNING> (stdout)>
2021-08-04 10:20:04,566 INFO exited: start-script (exit status 0; expected)
2021-08-04 10:20:04,566 DEBG received SIGCHLD indicating a child quit
2021-08-04 10:20:04,567 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2021-08-04 10:20:04,583 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2021-08-04 10:20:04,584 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2021-08-04 10:20:04,592 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2021-08-04 10:20:04,622 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8084...

2021-08-04 10:20:04,736 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8084

 

root@Highlander:/mnt/apps/appdata/dockers# docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose qbittorrentvpn
version: "3"
services:
  qbittorrentvpn:
    command:
      - '/bin/bash /usr/local/bin/init.sh'
    container_name: qbittorrentvpn
    cpuset: 1,2,3,4,8,9,13,14,15,17,18,19,20,24,25,29,30,31,
    entrypoint:
      - /usr/bin/tini
      - -g
      - --
    environment:
      - TZ=Europe/London
      - UMASK=000
      - PUID=99
      - TCP_PORT_19182=19182
      - HOST_OS=Unraid
      - TCP_PORT_8118=8118
      - 'VPN_PASS=vpn password'
      - ENABLE_PRIVOXY=no
      - LAN_NETWORK=192.168.1.0/24
      - VPN_INPUT_PORTS=
      - DEBUG=false
      - UDP_PORT_42565=42565
      - TCP_PORT_6881=6881
      - TCP_PORT_8080=8080
      - WEBUI_PORT=8084
      - PGID=100
      - TCP_PORT_42565=42565
      - UDP_PORT_6881=6881
      - VPN_OPTIONS=
      - NAME_SERVERS=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
      - VPN_ENABLED=no
      - VPN_PROV=airvpn
      - VPN_CLIENT=openvpn
      - TCP_PORT_58124=58124
      - STRICT_PORT_FORWARD=yes
      - 'VPN_USER=vpn username'
      - VPN_OUTPUT_PORTS=
      - PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
      - HOME=/home/nobody
      - TERM=xterm
      - LANG=en_GB.UTF-8
    expose:
      - 6881/tcp
      - 8080/tcp
      - 8118/tcp
    hostname: a3351c613287
    image: binhex/arch-qbittorrentvpn
    ipc: private
    labels:
      org.opencontainers.image.authors: binhex
    logging:
      driver: json-file
      options:
        max-file: 3
        max-size: 50m
    networks:
      - br0
    privileged: true
    security_opt:
      - label=disable
    volumes:
      - /mnt/user/mount_mergerfs/tdrive_vfs/downloads/qbittorrent:/data:rw
      - /mnt/user/:/user:rw
      - /mnt/user/appdata/dockers/qbittorrentvpn:/config:rw
networks:
  br0:
    external: true

 

Link to comment
7 minutes ago, DZMM said:

I can't get the webui http://192.168.1.81:8080/ to load - any ideas?  Thanks

you have set it to port 8084:- 

 

7 minutes ago, DZMM said:

WEBUI_PORT defined as '8084'

also just to make sure you are aware, you have the vpn disabled, probably on purpose i guess:-

 

8 minutes ago, DZMM said:

[info] VPN not enabled, skipping configuration of VPN

 

Link to comment
4 minutes ago, binhex said:

you have set it to port 8084:- 

 

also just to make sure you are aware, you have the vpn disabled, probably on purpose i guess:-

 

 

sorted it.  VPN wasn't enabled yet - just wanted to build the config files first and test the webui

Link to comment

Sorry, me again.

 

I can access the WEBUI ok if I turn off the VPN, but if I turn the VPN on I can't.  Everything looks fine in the logs - am I doing something stupid (probably)?

 

Thanks

 

ErrorWarningSystemArrayLogin


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

2021-08-04 11:48:24.246532 [info] Host is running unRAID
2021-08-04 11:48:24.267335 [info] System information Linux 13a02b1de59b 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2021-08-04 11:48:24.291095 [info] OS_ARCH defined as 'x86-64'
2021-08-04 11:48:24.314769 [info] PUID defined as '99'
2021-08-04 11:48:24.359866 [info] PGID defined as '100'
2021-08-04 11:48:24.408771 [info] UMASK defined as '000'
2021-08-04 11:48:24.431569 [info] Permissions already set for volume mappings
2021-08-04 11:48:24.455040 [info] Deleting files in /tmp (non recursive)...
2021-08-04 11:48:24.482320 [info] VPN_ENABLED defined as 'yes'
2021-08-04 11:48:24.506423 [info] VPN_CLIENT defined as 'openvpn'
2021-08-04 11:48:24.529076 [info] VPN_PROV defined as 'airvpn'
2021-08-04 11:48:24.557172 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/AirVPN_United-Kingdom_UDP-443.ovpn
2021-08-04 11:48:24.602177 [info] VPN remote server(s) defined as 'gb.vpn.airdns.org,'
2021-08-04 11:48:24.622914 [info] VPN remote port(s) defined as '443,'
2021-08-04 11:48:24.642965 [info] VPN remote protcol(s) defined as 'udp,'
2021-08-04 11:48:24.668104 [info] VPN_DEVICE_TYPE defined as 'tun0'
2021-08-04 11:48:24.691043 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2021-08-04 11:48:24.713667 [info] LAN_NETWORK defined as '192.168.1.0/24'
2021-08-04 11:48:24.737759 [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'
2021-08-04 11:48:24.760422 [info] ENABLE_PRIVOXY defined as 'no'
2021-08-04 11:48:24.786812 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2021-08-04 11:48:24.810419 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2021-08-04 11:48:24.833076 [info] WEBUI_PORT defined as '8080'
2021-08-04 11:48:25.131383 [info] Starting Supervisor...
2021-08-04 11:48:25,270 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2021-08-04 11:48:25,270 INFO Set uid to user 0 succeeded
2021-08-04 11:48:25,273 INFO supervisord started with pid 7
2021-08-04 11:48:26,275 INFO spawned: 'shutdown-script' with pid 167
2021-08-04 11:48:26,276 INFO spawned: 'start-script' with pid 168
2021-08-04 11:48:26,278 INFO spawned: 'watchdog-script' with pid 169
2021-08-04 11:48:26,279 INFO reaped unknown pid 8 (exit status 0)
2021-08-04 11:48:26,283 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2021-08-04 11:48:26,283 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-04 11:48:26,283 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-04 11:48:26,283 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-08-04 11:48:26,286 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2021-08-04 11:48:26,292 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible

2021-08-04 11:48:26,296 DEBG 'start-script' stdout output:
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2021-08-04 11:48:26,338 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2021-08-04 11:48:26,341 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2021-08-04 11:48:26,344 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2021-08-04 11:48:26,347 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2021-08-04 11:48:26,349 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2021-08-04 11:48:26,351 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2021-08-04 11:48:26,354 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2021-08-04 11:48:26,357 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2021-08-04 11:48:26,596 DEBG 'start-script' stdout output:
[info] Default route for container is 192.168.1.254

2021-08-04 11:48:26,608 DEBG 'start-script' stdout output:
[info] Docker network defined as 192.168.1.0/24

2021-08-04 11:48:26,611 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2021-08-04 11:48:26,612 DEBG 'start-script' stderr output:
RTNETLINK answers: File exists

2021-08-04 11:48:26,612 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2021-08-04 11:48:26,613 DEBG 'start-script' stdout output:
default via 192.168.1.254 dev eth0
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.61

2021-08-04 11:48:26,613 DEBG 'start-script' stdout output:
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
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
broadcast 192.168.1.0 dev eth0 table local proto kernel scope link src 192.168.1.61
local 192.168.1.61 dev eth0 table local proto kernel scope host src 192.168.1.61
broadcast 192.168.1.255 dev eth0 table local proto kernel scope link src 192.168.1.61

2021-08-04 11:48:26,613 DEBG 'start-script' stdout output:
--------------------

2021-08-04 11:48:26,615 DEBG 'start-script' stdout output:
iptable_mangle 16384 1
ip_tables 28672 3 iptable_filter,iptable_nat,iptable_mangle
x_tables 28672 14 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,ip6_tables,ipt_REJECT,ip_tables,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2021-08-04 11:48:26,615 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2021-08-04 11:48:26,658 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2021-08-04 11:48:26,659 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT
-A INPUT -s 84.39.117.56/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 -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT
-A OUTPUT -d 84.39.117.56/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 -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2021-08-04 11:48:26,659 DEBG 'start-script' stdout output:
--------------------

2021-08-04 11:48:26,660 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2021-08-04 11:48:26,666 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.


2021-08-04 11:48:26,666 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 WARNING: file 'credentials.conf' is group or others accessible

2021-08-04 11:48:26 OpenVPN 2.5.3 [git:makepkg/ecaf88f8a4e75856+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jun 18 2021
2021-08-04 11:48:26 library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10

2021-08-04 11:48:26,666 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2021-08-04 11:48:26,667 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-08-04 11:48:26 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

2021-08-04 11:48:26,667 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 TCP/UDP: Preserving recently used remote address: [AF_INET]84.39.117.56:443

2021-08-04 11:48:26,667 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 Socket Buffers: R=[212992->212992] S=[212992->212992]
2021-08-04 11:48:26 UDP link local: (not bound)
2021-08-04 11:48:26 UDP link remote: [AF_INET]84.39.117.56:443

2021-08-04 11:48:26,679 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 TLS: Initial packet from [AF_INET]84.39.117.56:443, sid=d82e76e1 74d819ac

2021-08-04 11:48:26,703 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org

2021-08-04 11:48:26,703 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 VERIFY KU OK
2021-08-04 11:48:26 Validating certificate extended key usage
2021-08-04 11:48:26 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2021-08-04 11:48:26 VERIFY EKU OK
2021-08-04 11:48:26 VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Naos, emailAddress=info@airvpn.org

2021-08-04 11:48:26,722 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bit RSA, signature: RSA-SHA512
2021-08-04 11:48:26 [Naos] Peer Connection Initiated with [AF_INET]84.39.117.56:443

2021-08-04 11:48:26,848 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 10.24.204.1,route-gateway 10.24.204.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.24.204.29 255.255.255.0,peer-id 0,cipher AES-256-GCM'
2021-08-04 11:48:26 OPTIONS IMPORT: timers and/or timeouts modified
2021-08-04 11:48:26 OPTIONS IMPORT: compression parms modified
2021-08-04 11:48:26 OPTIONS IMPORT: --ifconfig/up options modified
2021-08-04 11:48:26 OPTIONS IMPORT: route options modified
2021-08-04 11:48:26 OPTIONS IMPORT: route-related options modified
2021-08-04 11:48:26 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2021-08-04 11:48:26 OPTIONS IMPORT: peer-id set
2021-08-04 11:48:26 OPTIONS IMPORT: adjusting link_mtu to 1625
2021-08-04 11:48:26 OPTIONS IMPORT: data channel crypto options modified
2021-08-04 11:48:26 Data Channel: using negotiated cipher 'AES-256-GCM'

2021-08-04 11:48:26,848 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2021-08-04 11:48:26 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2021-08-04 11:48:26 net_route_v4_best_gw query: dst 0.0.0.0
2021-08-04 11:48:26 net_route_v4_best_gw result: via 192.168.1.254 dev eth0
2021-08-04 11:48:26 ROUTE_GATEWAY 192.168.1.254/255.255.255.0 IFACE=eth0 HWADDR=02:42:c0:a8:01:3d

2021-08-04 11:48:26,848 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 TUN/TAP device tun0 opened
2021-08-04 11:48:26 net_iface_mtu_set: mtu 1500 for tun0
2021-08-04 11:48:26 net_iface_up: set tun0 up

2021-08-04 11:48:26,848 DEBG 'start-script' stdout output:
2021-08-04 11:48:26 net_addr_v4_add: 10.24.204.29/24 dev tun0
2021-08-04 11:48:26 /root/openvpnup.sh tun0 1500 1553 10.24.204.29 255.255.255.0 init

2021-08-04 11:48:31,602 DEBG 'start-script' stdout output:
2021-08-04 11:48:31 net_route_v4_add: 84.39.117.56/32 via 192.168.1.254 dev [NULL] table 0 metric -1

2021-08-04 11:48:31,602 DEBG 'start-script' stdout output:
2021-08-04 11:48:31 net_route_v4_add: 0.0.0.0/1 via 10.24.204.1 dev [NULL] table 0 metric -1
2021-08-04 11:48:31 net_route_v4_add: 128.0.0.0/1 via 10.24.204.1 dev [NULL] table 0 metric -1
2021-08-04 11:48:31 Initialization Sequence Completed

2021-08-04 11:48:32,970 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2021-08-04 11:48:33,270 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 84.39.117.57

2021-08-04 11:48:33,270 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2021-08-04 11:48:47,989 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.24.204.29 different, marking for reconfigure

2021-08-04 11:48:47,992 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2021-08-04 11:48:47,992 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2021-08-04 11:48:47,999 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2021-08-04 11:48:48,015 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2021-08-04 11:48:48,129 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2021-08-04 11:48:47,999 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2021-08-04 11:48:48,015 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2021-08-04 11:48:48,129 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

 

Link to comment
14 minutes ago, binhex said:

Think so.  My ISP router is: 192.168.1.254

 

root@Highlander:~# ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.1  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 30:9c:23:9d:67:3d  txqueuelen 1000  (Ethernet)
        RX packets 11072566  bytes 10170092868 (9.4 GiB)
        RX errors 0  dropped 10159  overruns 0  frame 0
        TX packets 2853296  bytes 13614611695 (12.6 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

Edited by DZMM
Link to comment
44 minutes ago, DZMM said:

[info] Docker network defined as 192.168.1.0/24

i see docker network is on the same range as your lan network, this will not work, im assuming you have it set to custom bridge or macvlan, switch it back to network type 'bridge'

  • Thanks 1
Link to comment
49 minutes ago, binhex said:

i see docker network is on the same range as your lan network, this will not work, im assuming you have it set to custom bridge or macvlan, switch it back to network type 'bridge'

Thanks - sorted.  I used to have pfsense/VLANs setup that I removed last week, so my settings were a bit messed up.

Link to comment

@binhex Hopefully my last question.  I'm trying to move the docker off port 8080 as I use that for something else, but it doesn't work.  Everything looks ok in the logs, but when I go to the new webui port e.g. 8086 it doesn't load.

 

Thanks

 

root@Highlander:/mnt/apps/local/tdrive_vfs/unfiled/movies/lists# docker run --rm -v /var/run/docker.sock:/var/run/docker.sopose qbittorrentvpn
version: "3"
services:
  qbittorrentvpn:
    command:
      - '/bin/bash /usr/local/bin/init.sh'
    container_name: qbittorrentvpn
    cpuset: 1,2,3,4,8,9,13,14,15,17,18,19,20,24,25,29,30,31,
    entrypoint:
      - /usr/bin/tini
      - -g
      - --
    environment:
      - 'VPN_USER=vpn username'
      - 'VPN_PASS=vpn password'
      - VPN_PROV=airvpn
      - VPN_OPTIONS=
      - ENABLE_PRIVOXY=yes
      - WEBUI_PORT=8086
      - NAME_SERVERS=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
      - VPN_INPUT_PORTS=
      - TZ=Europe/London
      - HOST_OS=Unraid
      - VPN_CLIENT=openvpn
      - UMASK=000
      - PUID=99
      - PGID=100
      - STRICT_PORT_FORWARD=yes
      - LAN_NETWORK=192.168.1.0/24
      - VPN_ENABLED=yes
      - VPN_OUTPUT_PORTS=
      - DEBUG=false
      - PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
      - HOME=/home/nobody
      - TERM=xterm
      - LANG=en_GB.UTF-8
    hostname: e104fe09b0ec
    image: binhex/arch-qbittorrentvpn
    ipc: private
    labels:
      org.opencontainers.image.authors: binhex
    logging:
      driver: json-file
      options:
        max-file: 3
        max-size: 50m
    mac_address: 02:42:ac:11:00:0e
    networks:
      - bridge
    ports:
      - 19182:19182/tcp
      - 6881:6881/tcp
      - 6881:6881/udp
      - 8086:8080/tcp
      - 8118:8118/tcp
    privileged: true
    security_opt:
      - label=disable
    volumes:
      - /mnt/user/mount_mergerfs/tdrive_vfs/downloads/qbittorrent/:/data:rw
      - /mnt/user/:/user:rw
      - /mnt/user/appdata/dockers/qbittorrentvpn:/config:rw
networks:
  bridge:
    external: true

 

 

Link to comment
19 minutes ago, binhex said:

so qbittorrent is special, its the only time you need to change the container port and the host port, so change that to 8086:8086 and you should be set.

Thanks.  I think the use of 8080 was causing my network to melt down as Unifi is hardcoded onto 8080 and the two were knocking out my house as pretty much everything (lights, heating, AV etc) is all on a smarthome

Link to comment

Hello,

 

Is there documentation or a guide on how to use Https for the WEB UI for QbittorrentVPN, 

 

I have already used openssl to create a key and crt files. 

 

just struggling with this part I guess

 

image.png.5b92f794dbc04e678cacf6028f462057.png

 

I added a path for the container

 

image.png.1c7c102a6b4d65c8d4efaca679248d37.png

 

but still does not seem to want to work

 

not sure if this is the correct way to do this.

and I possible made the crt/key wrong

 

Thanks

Edited by schuu
Link to comment

If you're bothering to enable https I assume you are exposing it to the internet.   I use the Swag docker container for a reverse proxy that has a configuration for qbittorrent built in, making sure to setup an htaccess file and uncomment the lines in the configuration needed to put basic auth in front of the webUI.  

 

The container handles renewing a LetsEncrypt cert automatically, has most of the best practices in terms of protocols and headers configured for you, and has fail2ban included.  

 

I'd consider carefully though if you want to expose it to the internet at all before doing so.  Even with precautions it is still a lot riskier than having it be accessible only locally.  

Link to comment
11 hours ago, THF13 said:

If you're bothering to enable https I assume you are exposing it to the internet.   I use the Swag docker container for a reverse proxy that has a configuration for qbittorrent built in, making sure to setup an htaccess file and uncomment the lines in the configuration needed to put basic auth in front of the webUI.  

 

The container handles renewing a LetsEncrypt cert automatically, has most of the best practices in terms of protocols and headers configured for you, and has fail2ban included.  

 

I'd consider carefully though if you want to expose it to the internet at all before doing so.  Even with precautions it is still a lot riskier than having it be accessible only locally.  

 

I was not going to expose it, just wanted https locally, but I probably will not bother now, I've changed from swag to nginx proxy manager(NPM) to try it out, 

 

Edit:

NPM has access lists, I added the local subnet, and denied everything else, just need to work out how to get qbittorrent to work with it.

Edited by schuu
Link to comment

So I have followed the FAQ Question #2 directions from https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md on enabling Privoxy outside the LAN but I still cannot seem to get Privoxy to respond from the Internet. I have created a firewall rule on my firewall to allow port 8118 to go to my internal port 8118 on the UnRaid server. The firewall shows traffic coming in but Privoxy is NOT responding to the requests coming in to use it as the proxy server. If I use this from any other LAN device and point it to the IP of my Privoxy server and port it works flawlessly.

 

Is this FAQ possibly outdated and something has changed that I'm unaware of? Any assistance getting this working from OUTSIDE my LAN would be greatly appreciated.

 

Using UnRAID 6.9.2

Link to comment

Using UnRAID 6.9.2

binhex-qbitorrent - latest from binhex/arch-qbittorrentvpn

OpenVPN

PIA

 

I've downloaded the latest config.zip from PIA and put that in the openvpn directory. 

I start the container with DEBUG=true and let it run but it appears to never connect to PIA. I've verified that I can login to the site with my credentials an verified they are correct in qBit. Not sure what is happening. At first there was a DNS issue, but that has been resolved. Still having issues and no GUI available. Attached log file to this post.

 

Any assistance would be greatly appreciated. Got it working this far thanks to the help available on the internet.

supervisord.log

Link to comment

I am working on fixing some intermittent unraid server stability issues that have caused me to hard reboot the server a couple of times a few days apart.  

 

The past 2 times it has happened my Qbittorrent settings have reset to defaults, seemingly from the contents of the qBittorrent.conf being wiped and replaced with a nearly blank fresh file.  Everything else is fine, the vpn files, the active torrents, where they're saved, etc.  

 

I have moved my appdata folder from an unassigned disk to a second cache pool somewhat recently but can't think of anything else that's changed.  No other containers have had similar issues.  I run 2 qbittorrentvpn containers though and it affected both of them each time in exactly the same way.  It hasn't happened with clean array start/stops or with stopping/starting the docker service or the individual container.  

 

It's pretty easy to fix, I just drag the previous .conf file from a backup back into appdata and restart the container.  It is pretty annoying however because since my torrents are all in "Automatic" management mode it attempts to move every one to the default save location inside /config.  

 

Please let me know if anyone has an idea about why this is happening

Unfortunately fixed it before thinking to save the log file, if it happens a third time will grab that before fixing and restarting it.  

Link to comment

Hey folks,

 

Summary of my issue: QBitTorrent won't seed but ruTorrent with same WireGuard and Port config from Mullvad does

 

Not sure if i'm overlooking something silly here or not but I'm running unraid with both ruTorrent and QBitTorrent trying to determine which client I want to use for my Radarr/Sonarr/Plex setup.

 

Regardless of the client I'm using Mullvad. In my testing I'm able to both download and seed without issue on ruTorrent using the WireGuard configuration for Mullvad.

 

When I attempt to apply that same configuration to QBitTorrent I am able to download without issue, but I can never seed content. QBitTorrent attempts to seed but no data is actually being transmitted.

 

When testing only ruTorrent or QBitTorrent is on and running at one time. I can flip/flop between them and ruTorrent immediately starts downloading/seeds, and QBitTorrent only downloads.

 

Executing the following curl within QBitTorrent seems to be okay:

 

sh-5.1# curl https://am.i.mullvad.net/port/55310 {"ip":"XX.XX.XX.XX","port":55310,"reachable":true}sh-5.1#

 

Which is the port I have set in Mullvad but again, QBitTorrent doesn't seem to actually seed and in the QBitTorrent logs I see the following upon a restart:

 

(N) 2021-08-16T21:21:53 - Web UI: Now listening on IP: *, port: 8080 (I) 2021-08-16T21:21:53 - Successfully listening on IP: XXXXXXXX, port: TCP/55310 (I) 2021-08-16T21:21:53 - Successfully listening on IP: XXXXXXXX port: UDP/55310

 

View > Statistics "All-time upload" lists 24 GB but my tracker doesn't show that updated data

 

The connection status for upload speeds in the lower right corner will show 10KiBs, then 0 and this goes back and forth. The indicator is also that of a yellow up arrow. None of my torrents ever show consistent upload speeds whereas they do in ruTorrent.

 

Any suggestions?

 

Fresh logs attached and scrubbed for IP/Username

supervisord.log qbittorrent.log

Link to comment
On 7/16/2021 at 10:24 AM, questionbot said:

How can I "registers" my unraid torrent to a private tracker.. basically when  trying to download or upload I get "unrecognised host/passkey". The site I am looking at has some instructions for "seed boxes" and I was wondering if anyone knows how to adapt this for this docker.

 

Quote

1. Here on ???? menu above go to YOUR NAME > Preferences > Security
Note: YOUR  NAME - name on the tracker - for me it's ???.
2. There create a new session with your Seedbox Ip 
3. Once you submit the changes, you'll get a long string of data - your IP_session_cookie. 
4. Now open seedbox via ssh (or webmin). 
5. In the console of the seedbox enter:
sudo curl -c /path/docker/persists/???.cookies -b ???_id=IP_session_cookie https://????/json/dynamicSeedbox.php

This command should give you {"Success":true,"msg":"Completed"}
Note: Make sure you have admin rights. I've tried without sudo, but that gave me an error.
Note 2: IP_session_cookie here is that long string you've copied in step 3

So now this means, that you've created a session identified with you.

Does anyone recognise this and know what they are talking about and if there is a way I can adpat these instructions to work in unraid?

 

anyone able to help with this? If you need more info please let me know.

Edited by questionbot
Link to comment
On 8/11/2021 at 3:34 PM, therecker said:

So I have followed the FAQ Question #2 directions from https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md on enabling Privoxy outside the LAN but I still cannot seem to get Privoxy to respond from the Internet. I have created a firewall rule on my firewall to allow port 8118 to go to my internal port 8118 on the UnRaid server. The firewall shows traffic coming in but Privoxy is NOT responding to the requests coming in to use it as the proxy server. If I use this from any other LAN device and point it to the IP of my Privoxy server and port it works flawlessly.

 

Is this FAQ possibly outdated and something has changed that I'm unaware of? Any assistance getting this working from OUTSIDE my LAN would be greatly appreciated.

 

Using UnRAID 6.9.2

This has been posted for over a week now. Is anyone able to provide some insight into this please?

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.