Jump to content

[Support] binhex - qBittorrentVPN


Recommended Posts

Hello everyone.


I am currently trying to get the Docker binhex-qbittorrentvpn running.

I use https://www.perfect-privacy.com as VPN. The protocol here runs via openVPN


I have left all settings of the container at default except the VPN login data.


VPN_ENABLED -> YES

VPN_PROV -> custom

VPN_CLIENT -> openvpn

Then I inserted my login data.

Screenshot2024-06-26114029.thumb.png.a0f9704b9096b85570bb5fb1454d5ca5.png

Screenshot2024-06-26114046.thumb.png.9d8b96f7b0c753d438ff7342ec7539b9.png

Screenshot2024-06-26114056.thumb.png.d5d93e77b834d1401e4b4c2c1bf3738f.png

 

Then downloaded the current ovpn files from my provider and inserted "amsterdam" into the openvpn folder of qbittorrent as a test

Screenshot2024-06-26114156.png.a428f9359827fc05fb0635762d875e4f.png


when i look at the logs now i get the following error.


 

Screenshot2024-06-26114229.thumb.png.39fb7610e712d70a4e1267dcb455aaba.png

 

here is the supervisord.log

 

Quote

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

2024-06-26 12:11:35.822000 [info] Host is running unRAID
2024-06-26 12:11:35.846839 [info] System information Linux ecf8c3011dae 6.1.49-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 x86_64 GNU/Linux
2024-06-26 12:11:35.872982 [info] PUID defined as '99'
2024-06-26 12:11:35.901736 [info] PGID defined as '100'
2024-06-26 12:11:35.947805 [info] UMASK defined as '000'
2024-06-26 12:11:35.973496 [info] Permissions already set for '/config'
2024-06-26 12:11:36.000871 [info] Deleting files in /tmp (non recursive)...
2024-06-26 12:11:36.036981 [info] VPN_ENABLED defined as 'yes'
2024-06-26 12:11:36.064380 [info] VPN_CLIENT defined as 'openvpn'
2024-06-26 12:11:36.091059 [info] VPN_PROV defined as 'custom'
2024-06-26 12:11:36.123600 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Amsterdam.ovpn
2024-06-26 12:11:36.265796 [info] VPN remote server(s) defined as '95.168.167.236,95.168.167.236,95.168.167.236,95.211.95.233,95.211.95.233,95.211.95.233,95.211.95.244,95.211.95.244,95.211.95.244,37.48.94.1,37.48.94.1,37.48.94.1,'
2024-06-26 12:11:36.289915 [info] VPN remote port(s) defined as '44,443,4433,44,443,4433,44,443,4433,44,443,4433,'
2024-06-26 12:11:36.313980 [info] VPN remote protcol(s) defined as 'udp,udp,udp,udp,udp,udp,udp,udp,udp,udp,udp,udp,'
2024-06-26 12:11:36.340857 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-06-26 12:11:36.367450 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-06-26 12:11:36.683643 [info] LAN_NETWORK defined as '192.168.178.0/24'
2024-06-26 12:11:36.715589 [info] LAN_NETWORK exported as '192.168.178.0/24'
2024-06-26 12:11:36.741665 [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'
2024-06-26 12:11:36.767871 [info] VPN_USER defined as 'XXXXXXXXX'
2024-06-26 12:11:36.794785 [info] VPN_PASS defined as 'XXXXXXXXX'
2024-06-26 12:11:36.821323 [info] ENABLE_PRIVOXY defined as 'no'
2024-06-26 12:11:36.849486 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2024-06-26 12:11:36.875962 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2024-06-26 12:11:36.902452 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2024-06-26 12:11:36.928716 [info] WEBUI_PORT defined as '8080'
2024-06-26 12:11:36.958433 [info] Starting Supervisor...
2024-06-26 12:11:37,141 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2024-06-26 12:11:37,142 INFO Set uid to user 0 succeeded
2024-06-26 12:11:37,144 INFO supervisord started with pid 7
2024-06-26 12:11:38,147 INFO spawned: 'start-script' with pid 556
2024-06-26 12:11:38,148 INFO spawned: 'watchdog-script' with pid 557
2024-06-26 12:11:38,149 INFO reaped unknown pid 8 (exit status 0)
2024-06-26 12:11:38,151 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2024-06-26 12:11:38,152 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-06-26 12:11:38,152 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-06-26 12:11:38,188 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2024-06-26 12:11:38,190 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2024-06-26 12:11:38,192 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2024-06-26 12:11:38,193 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2024-06-26 12:11:38,195 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2024-06-26 12:11:38,197 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2024-06-26 12:11:38,378 DEBG 'start-script' stdout output:
[info] Adding 192.168.178.0/24 as route via adapter eth0

2024-06-26 12:11:38,380 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2024-06-26 12:11:38,381 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2
192.168.178.0/24 via 172.17.0.1 dev eth0

2024-06-26 12:11:38,382 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.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2
fd17::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fd17::1 dev eth0 metric 1024 pref medium
local ::1 dev lo table local proto kernel metric 0 pref medium
local fd17::242:ac11:2 dev eth0 table local proto kernel metric 0 pref medium
local fe80::42:acff:fe11:2 dev eth0 table local proto kernel metric 0 pref medium
multicast ff00::/8 dev eth0 table local proto kernel metric 256 pref medium

2024-06-26 12:11:38,382 DEBG 'start-script' stdout output:
--------------------

2024-06-26 12:11:38,386 DEBG 'start-script' stdout output:
iptable_mangle         16384  1
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               45056  17 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,nft_compat,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-06-26 12:11:38,386 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2024-06-26 12:11:38,507 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2024-06-26 12:11:38,509 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/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 -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/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

2024-06-26 12:11:38,510 DEBG 'start-script' stdout output:
--------------------

2024-06-26 12:11:38,510 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-06-26 12:11:38,518 DEBG 'start-script' stdout output:
Options error: Unrecognized option or missing or extra parameter(s) in /config/openvpn/Amsterdam.ovpn:222: register-dns (2.6.10)
Use --help for more information.


Furthermore, I cannot call up webui. I assume that this is related to the error!


What have I overlooked here? What would I have to change or set to get the container to run?


I would be very happy about a help :)


Best regards

Smoky

 

 

Edited by Smoky93
Link to comment

I just want to make sure im doing this safely. I want to route my firefox container through the binhex-qbittorrentvpn container.

Firefox container settings

Network Type: none

Extra parameters: --network container:binhex-qbittorrentvpn
Remove other container ports

binhex-qbittorrentvpn settings
 

Add a new port for firefox
Firefox container port: 5800

Host port: 5800

And lastly add port 5800 to VPN_INPUT_PORTS

Does this look safe? i dont want to accidentally open up my firefox container to everyone on the internet.

 

Best Regards!

Link to comment

Have a new unRaid build going, and my processor is struggling when downloading using this container. Admittedly, this processor is a lowly n5105, so if this sort of performance is to be expected, then I'll learn to live with it (for now...). When downloading 5 torrents, the cpu usage is around 40-90%. I'm using wireguard, although I did attempt using openVPN beforehand with similar results.

 

Thank you for any insights, much appreciated.

Link to comment

I'm having issues where the RSS downloader rules are not saving correctly. I can change the search strings and which feeds the rule applies to, but changing most of the options, such as whether to create a subfolder, whether or not to add paused, or save to a different directory, will not be saved once I close out of the download rules window. I've found moderate success trying to edit the json file with the downloading rules, but it's hard to know what options to use when I can't save the options I want to use as a basis.

Link to comment
Posted (edited)
On 6/30/2024 at 11:23 PM, celticGreen said:

Have a new unRaid build going, and my processor is struggling when downloading using this container. Admittedly, this processor is a lowly n5105, so if this sort of performance is to be expected, then I'll learn to live with it (for now...). When downloading 5 torrents, the cpu usage is around 40-90%. I'm using wireguard, although I did attempt using openVPN beforehand with similar results.

 

Thank you for any insights, much appreciated.

If you are downloading to a share in the fuse layer (none exclusive share) it might take up a good deal of CPU.

Please note that if you change it to an exclusive share you won't be able to use hard links when moving files.

Edited by Yock
  • Thanks 1
Link to comment

In my system there is a memory leak on QbittorrentVPN container. The ram grow up until crash the system. I've limited my resource on docker to 94GB of RAM 

 

Screenshot2024-07-03at21_44_19.thumb.png.d2828ddef0f23c52c0c866493b7c4f4a.png

(from 22.30 to 9.00 the system runs in power saving mode)

 

And the system should be limited to 32GB + 8GB for torrent checks:

Screenshot2024-07-03at21_41_31.thumb.png.30fe8599176275aebfa8abe67f7b6b80.png

 

Someone can help me to understand what I can do to avoid it? 

  • Upvote 1
Link to comment
4 minutes ago, Lagadin said:

Today after updating I keep getting "Error: error sending query: Error creating socket" in my log both on wireguard or on openvpn with different servers. Anyone else getting this error?

I have the same error, using openvpn.

Link to comment
Posted (edited)

Same here, I turned on debug and see this in my logs...

 

2024-07-04 12:10:48.781171 [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'
2024-07-04 12:10:48.798036 [debug] iptables default policies available, setting policy to drop...2024-07-04 12:10:48.814055 [debug] ip6tables default policies available, setting policy to drop...
Error: error sending query: Error creating socket
2024-07-04 12:10:48.852032 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:10:53.868701 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:10:58.884607 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:11:03.901040 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:11:08.916784 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:11:13.932828 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...

 

Some sort of dns error? I'm using PIA

Edited by Gex2501
Link to comment
Posted (edited)

Me as well getting the Error creating socket.

Found that it appears that having a custom docker network (so i can assign a custom ip to the container), is at least part of the issue. if i change network back to BRIDGE instead of BR0 then everything seems to fire up as per before. although a temp fix, i do need this docker (as well as others that i have piggy backing off the connection) to be running under a manually specified IP.

Edited by Migraine
Link to comment
Posted (edited)
5 minutes ago, Migraine said:

Me as well getting the Error creating socket.

Found that it appears that having a custom docker network (so i can assign a custom ip to the container, is at least part of the issue. if i change network back to BR0 then everything seems to fire up as per before. although a temp fix, i do need this docker (as well as others that i have piggy backing off the connection) to be running under a manually specified IP.

 

I set my tag to :4.6.5-1-05 and I'm back in business. It would seem there is an error with the :latest or :4.6.5-1-06 that was pushed just a few hours ago...

Edited by Gex2501
Link to comment
Posted (edited)
7 minutes ago, Gex2501 said:

 

I set my tag to :4.6.5-1-05 and I'm back in business. It would seem there is an error with the :latest or :4.6.5-1-06 that was just a few hours ago...

Yeah, I've reverted back to the tag mentioned above, and all is working again, thanks for posting the tag so i didn't have to go looking!, will wait till this issue can be rectified before upgrading.

 

** If your running your qbit on a manually specified network / ip hold off updating or revert back to the tag mentioned by Gex2501 (:4.6.5-1-05) **

 

*** If your running qbit on the typical bridge network then in theory you might be fine either way (updated or not) ***

Edited by Migraine
Link to comment

is there a way to get "Display torrent content and some options" under "when adding a torrent" like the windows version of qbittorrent?

What it looks like and the option inside the windows version for context. \/\/
image.png.adc9136008bf3f58c04f91a9718927b8.png
image.thumb.png.73156c6d2e8b01d8907eb49c20b4bd8e.png

Link to comment

Im getting this same error "Error: error sending query: Error creating socket" since the update, using PIA via OpenVPN, i know someone else who is using PIA via wireguard with the same issue too.

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.

×
×
  • Create New...