[Support] binhex - qBittorrentVPN

[gvrx]

11 minutes ago, binhex said:

OK can you please also paste a screenshot of Options/Downloads in the qBittorrent web ui, i am particular interested in the completed and incomplete paths, my suspicion is that is not correctly defined and therefore it cannot start the torrent as it has nowhere to save to.

 

[ptr78]

I noticed that the "settings page" for this docker container has changed since I installed it. When I select 'Edit' it does not show the new variables such as "Path: /shared". What is the best practice to update the docker so that the latest set of variables will be visible? Thank you for any help!

[binhex]

16 minutes ago, ptr78 said:

I noticed that the "settings page" for this docker container has changed since I installed it. When I select 'Edit' it does not show the new variables such as "Path: /shared". What is the best practice to update the docker so that the latest set of variables will be visible? Thank you for any help!

click on ' Show more settings ...' at the bottom in the edit screen

[ptr78]

Just now, binhex said:

click on ' Show more settings ...' at the bottom in the edit screen

It only shows 'AppData Config Path:' and it has been there from the beginning when I installed the docker.

[binhex]

2 minutes ago, ptr78 said:

It only shows 'AppData Config Path:' and it has been there from the beginning when I installed the docker.

what has been there from the beginning?, "Path: /shared"? ,that has only been added in the past couple of weeks, screenshot please.

[binhex]

56 minutes ago, gvrx said:

 

ok that looks alright, just to double check try left click container, console then type 'touch /data/torrents/delme.txt' does it create a file without error?, look on your host can you see file '/mnt/user/data/torrents/delme.txt' ?

[ptr78]

25 minutes ago, binhex said:

what has been there from the beginning?, "Path: /shared"? ,that has only been added in the past couple of weeks, screenshot please.

Please, find attached a screenshot that shows what can be seen by clicking "Show more settings..."

Edited July 24 by ptr78

[binhex]

48 minutes ago, ptr78 said:

Please, find attached a screenshot that shows what can be seen by clicking "Show more settings..."

OK so thats the older template you have there, template updates are NOT pushed out to clients, if you want the latest template then you will need to remove the existing user template and reinstall from CA - i would recommend making a note of all your existing settings before doing this.

[ptr78]

1 hour ago, binhex said:

OK so thats the older template you have there, template updates are NOT pushed out to clients, if you want the latest template then you will need to remove the existing user template and reinstall from CA - i would recommend making a note of all your existing settings before doing this.

 

OK. So, "removing the user template" means that I need to remove the docker and then reinstall it from CA?

 

Edited July 24 by ptr78

[binhex]

4 hours ago, ptr78 said:

 

OK. So, "removing the user template" means that I need to remove the docker and then reinstall it from CA?

 

you need to delete your user template from unraid:-

1. go main docker tab in unraid web ui
2. click on 'add container' (yes its non intuitive)
3. click on select a template and ensure you are under 'user templates' section and select the template you want to delete
4. click on the X to the right of the template name and confirm deletion
5. go to CA and install the app and reconfigure.

 

[gvrx]

15 hours ago, binhex said:

ok that looks alright, just to double check try left click container, console then type 'touch /data/torrents/delme.txt' does it create a file without error?, look on your host can you see file '/mnt/user/data/torrents/delme.txt' ?

No error, the fiile showed up just fine

[Toibs]

Please could someone assist here, as i'm going round and around in circles. 

 

Until a few weeks ago everything worked fine. However for some reason I'm getting no IPAddress assigned locally (if i select "WebUI" it just comes up with "blocked"....

 

 

If anyone could give me any pointers would be appreciated - am guessing I have missed something here??

 

If i manually put an IP into "Fixed IP address (optional):" the container wont start (Execution Error 403).

 

Thanks!

Edited July 26 by Toibs

[BUSTER]

Hi Guys,

 

i have qBittorrentvpn installed on CasaOS witsh runs on Debian Bullseye, on CasaOS WebGUI i can see Application is running

but i cannot receive WebGUI from qBittorrentvpn, 

 

Docker log: --> docker logs -f qbittorrentvpn

tells me...

 

[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

 

i do this option for Ubuntu  '/sbin/modprobe iptable_mangle' but issue is persist can someone help me please 

following i case of code Docker & qBittorrent log´s 

 

Best regards

 

BUSTER

 

 

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

2024-07-26 18:23:06.785063 [info] System information Linux qbittorrentvpn 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
2024-07-26 18:23:06.815857 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-07-26 18:23:06.846375 [info] PUID defined as '0'
2024-07-26 18:23:06.908440 [info] PGID defined as '0'
2024-07-26 18:23:07.022024 [info] UMASK defined as '000'
2024-07-26 18:23:07.056255 [info] Permissions already set for '/config'
2024-07-26 18:23:07.090984 [info] Deleting files in /tmp (non recursive)...
2024-07-26 18:23:07.155096 [info] VPN_ENABLED defined as 'yes'
2024-07-26 18:23:07.188006 [info] VPN_CLIENT defined as 'openvpn'
2024-07-26 18:23:07.219861 [info] VPN_PROV defined as 'pia'
2024-07-26 18:23:07.263561 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/netherlands.ovpn
2024-07-26 18:23:07.329905 [info] VPN remote server(s) defined as 'nl-amsterdam.privacy.network,'
2024-07-26 18:23:07.357296 [info] VPN remote port(s) defined as '1198,'
2024-07-26 18:23:07.384697 [info] VPN remote protcol(s) defined as 'udp,'
2024-07-26 18:23:07.416425 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-07-26 18:23:07.447292 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-07-26 18:23:07.496056 [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'
modprobe: FATAL: Module ip6_tables not found in directory /lib/modules/6.1.0-18-amd64
ip6tables v1.8.10 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
2024-07-26 18:23:07.547694 [warn] ip6tables default policies not available, skipping ip6tables drops
2024-07-26 18:23:08.031769 [info] LAN_NETWORK defined as '192.168.5.0/24'
2024-07-26 18:23:08.074364 [info] LAN_NETWORK exported as '192.168.5.0/24'
2024-07-26 18:23:08.105503 [info] VPN_USER defined as 'XXX'
2024-07-26 18:23:08.137601 [info] VPN_PASS defined as 'XXX'
2024-07-26 18:23:08.168575 [info] STRICT_PORT_FORWARD defined as 'yes'
2024-07-26 18:23:08.203126 [info] VPN_INPUT_PORTS defined as '1234'
2024-07-26 18:23:08.235302 [info] VPN_OUTPUT_PORTS defined as '5678'
2024-07-26 18:23:08.266142 [info] ENABLE_STARTUP_SCRIPTS defined as 'yes'
2024-07-26 18:23:08.297414 [info] ENABLE_SOCKS defined as 'yes'
2024-07-26 18:23:08.328387 [info] ENABLE_PRIVOXY defined as 'yes'
2024-07-26 18:23:08.361315 [info] SOCKS_USER defined as 'admin'
2024-07-26 18:23:08.392168 [info] SOCKS_PASS defined as 'socks'
2024-07-26 18:23:08.423481 [info] WEBUI_PORT defined as '8080'
2024-07-26 18:23:08.463540 [info] Starting Supervisor...
2024-07-26 18:23:08,698 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2024-07-26 18:23:08,698 INFO Set uid to user 0 succeeded
2024-07-26 18:23:08,700 INFO supervisord started with pid 8
2024-07-26 18:23:09,702 INFO spawned: 'start-script' with pid 390
2024-07-26 18:23:09,704 INFO spawned: 'watchdog-script' with pid 391
2024-07-26 18:23:09,705 INFO reaped unknown pid 9 (exit status 0)
2024-07-26 18:23:09,712 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2024-07-26 18:23:09,712 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-07-26 18:23:09,712 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-07-26 18:23:09,781 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2024-07-26 18:23:09,783 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/6.1.0-18-amd64

2024-07-26 18:23:09,783 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2024-07-26 18:23:09,785 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2024-07-26 18:23:09,785 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2024-07-26 18:23:10,019 DEBG 'start-script' stdout output:
[info] Adding 192.168.5.0/24 as route via adapter eth0

2024-07-26 18:23:10,020 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2024-07-26 18:23:10,022 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.5.0/24 via 172.17.0.1 dev eth0
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

2024-07-26 18:23:10,022 DEBG 'start-script' stdout output:
local ::1 dev lo table local proto kernel metric 0 pref medium
--------------------

2024-07-26 18:23:10,150 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2024-07-26 18:23:10,152 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 143.244.41.187/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.120/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.162/32 -i eth0 -j ACCEPT
-A INPUT -s 172.64.151.73/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.36.183/32 -i eth0 -j ACCEPT
-A INPUT -s 104.19.240.167/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.159.201/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 143.244.41.187/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.120/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.162/32 -i eth0 -j ACCEPT
-A INPUT -s 172.64.151.73/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.36.183/32 -i eth0 -j ACCEPT
-A INPUT -s 104.19.240.167/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.159.201/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 -i eth0 -p tcp -m tcp --dport 1234 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 1234 -j ACCEPT
-A INPUT -s 192.168.5.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 9118 -j ACCEPT
-A INPUT -s 192.168.5.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -s 192.168.5.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --sport 5678 -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 143.244.41.187/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.120/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.162/32 -o eth0 -j ACCEPT
-A OUTPUT -d 172.64.151.73/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.36.183/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 143.244.41.187/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.120/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.162/32 -o eth0 -j ACCEPT
-A OUTPUT -d 172.64.151.73/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.36.183/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.159.201/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 -o eth0 -p tcp -m tcp --sport 1234 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 1234 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.5.0/24 -o eth0 -p tcp -m tcp --sport 9118 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.5.0/24 -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.5.0/24 -o eth0 -p tcp -m tcp --dport 5678 -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-07-26 18:23:10,154 DEBG 'start-script' stdout output:
--------------------

2024-07-26 18:23:10,155 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-07-26 18:23:10,168 DEBG 'start-script' stdout output:
2024-07-26 18:23:10 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.
2024-07-26 18:23:10 WARNING: file 'credentials.conf' is group or others accessible

2024-07-26 18:23:10,169 DEBG 'start-script' stdout output:
2024-07-26 18:23:10 OpenVPN 2.6.11 [git:makepkg/ddf6bf6d2a135835+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 20 2024
2024-07-26 18:23:10 library versions: OpenSSL 3.3.1 4 Jun 2024, LZO 2.10
2024-07-26 18:23:10 DCO version: N/A
2024-07-26 18:23:10 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2024-07-26 18:23:10,170 DEBG 'start-script' stdout output:
2024-07-26 18:23:10 TCP/UDP: Preserving recently used remote address: [AF_INET]143.244.41.187:1198
2024-07-26 18:23:10 UDPv4 link local: (not bound)
2024-07-26 18:23:10 UDPv4 link remote: [AF_INET]143.244.41.187:1198

2024-07-26 18:23:11,718 DEBG 'start-script' stdout output:
2024-07-26 18:23:11 [amsterdam442] Peer Connection Initiated with [AF_INET]143.244.41.187:1198

2024-07-26 18:23:11,730 DEBG 'start-script' stdout output:
2024-07-26 18:23:11 TUN/TAP device tun0 opened
2024-07-26 18:23:11 net_iface_mtu_set: mtu 1500 for tun0
2024-07-26 18:23:11 net_iface_up: set tun0 up

2024-07-26 18:23:11,731 DEBG 'start-script' stdout output:
2024-07-26 18:23:11 net_addr_v4_add: 10.1.112.214/24 dev tun0
2024-07-26 18:23:11 /root/openvpnup.sh tun0 1500 0 10.1.112.214 255.255.255.0 init

2024-07-26 18:23:11,734 DEBG 'start-script' stdout output:
2024-07-26 18:23:11 Initialization Sequence Completed

2024-07-26 18:23:18,796 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2024-07-26 18:23:18,912 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 143.244.41.187

2024-07-26 18:23:18,913 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port for 'pia'
[info] Port forwarding is enabled
[info] Checking endpoint 'nl-amsterdam.privacy.network' is port forward enabled...

2024-07-26 18:23:19,058 DEBG 'start-script' stdout output:
[info] PIA endpoint 'nl-amsterdam.privacy.network' is in the list of endpoints that support port forwarding shown below:-

2024-07-26 18:23:19,201 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2024-07-26 18:23:19,203 DEBG 'start-script' stdout output:
[info] in.privacy.network
[info] nz.privacy.network
[info] kr-south-korea-pf.privacy.network
[info] slovenia.privacy.network
[info] bo-bolivia-pf.privacy.network
[info] au-sydney.privacy.network
[info] liechtenstein.privacy.network
[info] aus-melbourne.privacy.network
[info] ae.privacy.network
[info] bangladesh.privacy.network
[info] hk.privacy.network
[info] ca-montreal.privacy.network
[info] srilanka.privacy.network
[info] macau.privacy.network
[info] gt-guatemala-pf.privacy.network
[info] sk.privacy.network
[info] cyprus.privacy.network
[info] ireland.privacy.network
[info] np-nepal-pf.privacy.network
[info] greenland.privacy.network
[info] italy.privacy.network
[info] no.privacy.network
[info] dz.privacy.network
[info] gr.privacy.network
[info] ar.privacy.network
[info] fi.privacy.network
[info] china.privacy.network
[info] jakarta.privacy.network
[info] ca-toronto.privacy.network
[info] sg.privacy.network
[info] sweden.privacy.network
[info] cambodia.privacy.network
[info] poland.privacy.network
[info] monaco.privacy.network
[info] tr.privacy.network
[info] venezuela.privacy.network
[info] au-brisbane-pf.privacy.network
[info] vietnam.privacy.network
[info] kualalumpur.privacy.network
[info] is.privacy.network
[info] ca-vancouver.privacy.network
[info] saudiarabia.privacy.network
[info] ad.privacy.network
[info] ec-ecuador-pf.privacy.network
[info] lv.privacy.network
[info] uk-london.privacy.network
[info] taiwan.privacy.network
[info] israel.privacy.network
[info] mongolia.privacy.network
[info] georgia.privacy.network
[info] uy-uruguay-pf.privacy.network
[info] sweden-2.privacy.network
[info] za.privacy.network
[info] de-frankfurt.privacy.network
[info] france.privacy.network
[info] uk-2.privacy.network
[info] nl-netherlands-so.privacy.network
[info] lu.privacy.network
[info] de-germany-so.privacy.network
[info] italy-2.privacy.network
[info] au-adelaide-pf.privacy.network
[info] santiago.privacy.network
[info] de-berlin.privacy.network
[info] es-valencia.privacy.network
[info] pt.privacy.network
[info] austria.privacy.network
[info] montenegro.privacy.network
[info] brussels.privacy.network
[info] malta.privacy.network
[info] mk.privacy.network
[info] au-australia-so.privacy.network
[info] yerevan.privacy.network
[info] hungary.privacy.network
[info] uk-manchester.privacy.network
[info] sanjose.privacy.network
[info] man.privacy.network
[info] qatar.privacy.network
[info] philippines.privacy.network
[info] nl-amsterdam.privacy.network
[info] ba.privacy.network
[info] bahamas.privacy.network
[info] sofia.privacy.network
[info] br.privacy.network
[info] mexico.privacy.network
[info] ca-ontario-so.privacy.network
[info] nigeria.privacy.network
[info] japan-2.privacy.network
[info] morocco.privacy.network
[info] ee.privacy.network
[info] czech.privacy.network
[info] uk-southampton.privacy.network
[info] aus-perth.privacy.network
[info] bogota.privacy.network
[info] denmark-2.privacy.network
[info] md.privacy.network
[info] egypt.privacy.network
[info] swiss.privacy.network
[info] rs.privacy.network
[info] ro.privacy.network
[info] kazakhstan.privacy.network
[info] spain.privacy.network
[info] al.privacy.network
[info] panama.privacy.network
[info] lt.privacy.network
[info] zagreb.privacy.network
[info] ca-ontario.privacy.network
[info] ua.privacy.network
[info] fi-2.privacy.network
[info] pe-peru-pf.privacy.network
[info] japan.privacy.network
[info] denmark.privacy.network

2024-07-26 18:23:24,341 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '23890'

2024-07-26 18:23:24,837 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.1.112.214 different, marking for reconfigure

2024-07-26 18:23:24,842 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2024-07-26 18:23:24,847 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2024-07-26 18:23:24,855 DEBG 'watchdog-script' stdout output:
[info] Restarting microsocks due to change in vpn ip...

2024-07-26 18:23:24,860 DEBG 'watchdog-script' stdout output:
[info] Attempting to start microsocks...

2024-07-26 18:23:24,862 DEBG 'watchdog-script' stdout output:
[info] microsocks process started
[info] qBittorrent incoming port 6881 and VPN incoming port 23890 different, marking for reconfigure
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2024-07-26 18:23:24,890 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2024-07-26 18:23:24,899 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2024-07-26 18:23:25,124 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2024-07-26 18:23:25,181 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2024-07-26 18:23:26,192 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2024-07-26 18:23:26,198 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2024-07-26 18:33:24,406 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '23890'

 

 

 

Here is Log´s from qBittorrent

(N) 2024-07-26T18:23:24 - qBittorrent v4.6.5 started
(N) 2024-07-26T18:23:24 - Using config directory: /config/qBittorrent/config
(N) 2024-07-26T18:23:24 - Trying to listen on the following list of IP addresses: "tun0:44852"
(I) 2024-07-26T18:23:24 - Peer ID: "-qB4650-"
(I) 2024-07-26T18:23:24 - HTTP User-Agent: "qBittorrent/4.6.5"
(I) 2024-07-26T18:23:24 - Distributed Hash Table (DHT) support: ON
(I) 2024-07-26T18:23:24 - Local Peer Discovery support: ON
(I) 2024-07-26T18:23:24 - Peer Exchange (PeX) support: ON
(I) 2024-07-26T18:23:24 - Anonymous mode: OFF
(I) 2024-07-26T18:23:24 - Encryption support: ON
(I) 2024-07-26T18:23:24 - Successfully listening on IP. IP: "10.1.112.214". Port: "TCP/44852"
(I) 2024-07-26T18:23:24 - Successfully listening on IP. IP: "10.1.112.214". Port: "UTP/44852"
(I) 2024-07-26T18:23:24 - Successfully listening on IP. IP: "fe80::e1c7:901d:51f1:76b0%tun0". Port: "TCP/44852"
(I) 2024-07-26T18:23:24 - Successfully listening on IP. IP: "fe80::e1c7:901d:51f1:76b0%tun0". Port: "UTP/44852"
(I) 2024-07-26T18:23:24 - UPnP/NAT-PMP support: ON
(I) 2024-07-26T18:23:24 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Mon Jul 1 02:34:52 2024.
(N) 2024-07-26T18:23:25 - Using built-in WebUI.
(N) 2024-07-26T18:23:25 - WebUI translation for selected locale (en) has been successfully loaded.
(N) 2024-07-26T18:23:25 - WebUI: Now listening on IP: *, port: 8080
(N) 2024-07-26T18:23:25 - Trying to listen on the following list of IP addresses: "tun0:23890"
(I) 2024-07-26T18:23:25 - Successfully listening on IP. IP: "10.1.112.214". Port: "TCP/23890"
(I) 2024-07-26T18:23:25 - Successfully listening on IP. IP: "10.1.112.214". Port: "UTP/23890"
(I) 2024-07-26T18:23:25 - Successfully listening on IP. IP: "fe80::e1c7:901d:51f1:76b0%tun0". Port: "TCP/23890"
(I) 2024-07-26T18:23:25 - Successfully listening on IP. IP: "fe80::e1c7:901d:51f1:76b0%tun0". Port: "UTP/23890"
(I) 2024-07-26T18:23:42 - Detected external IP. IP: "143.244.41.187"

 

[binhex]

23 hours ago, BUSTER said:

but i cannot receive WebGUI from qBittorrentvpn, 

what is the ip address of the machine running the web browser?

[Kwesty]

I've been trying to sort this issue for a few days now. It seems like privoxy is refusing to connect to pia, it just constantly keeps trying to establish the tcp connection with one of the pia servers. (I left this on for 24+ hours with no result). This is driving me a little nuts and I can't work out what is going wrong. Would really appreciate some help with this. Thanks! 

 

Edit: Thought I'd include what I've tried to do already:

• Regenerated the appdata configs
• Tried using both openvpn and wireguard
• Tried changing the default nameserver to my pihole container

logs.txt

Edited July 27 by Kwesty

[Kwesty]

1 hour ago, Kwesty said:

I've been trying to sort this issue for a few days now. It seems like privoxy is refusing to connect to pia, it just constantly keeps trying to establish the tcp connection with one of the pia servers. (I left this on for 24+ hours with no result). This is driving me a little nuts and I can't work out what is going wrong. Would really appreciate some help with this. Thanks! 

 

Edit: Thought I'd include what I've tried to do already:

• Regenerated the appdata configs
• Tried using both openvpn and wireguard
• Tried changing the default nameserver to my pihole container

logs.txt 30.04 kB · 1 download

 

 

Interestingly enough, giving the container its own ip address on br0 actually allows it to successfully connect and start the webui. However, I cannot access the UI as the container doesn't actually seem to use the ip. I've attached a new log file. Thanks!
 

logs.txt

[BUSTER]

3 hours ago, binhex said:

what is the ip address of the machine running the web browser?

http://192.168.5.25:8080

 

 

[binhex]

12 hours ago, BUSTER said:

http://192.168.5.25:8080

 

 

ok that all looks fine, your log shows nothing wrong and your LAN_NETWORK is defined correctly, try access from another browser, if not try another machine, there maybe anti virus or similar blocking access to port 8080 perhaps.

[DigitalLF]

@binhex

 

I'm doing my best to secure my network quite a bit and I have moved qBittorrent to VLAN 102 (192.168.102.2) and my computer is on VLAN 100 (192.168.100.2). My unRAID (Proxmox VM) use "macvlan". VLAN are created in unRAID, Switch, Router. Everything works fine except qBittorrent.

 

I changed "Network Type:" for qBittorrent to the "br0.102" and changed the docker setting "Key 10:"/"LAN_NETWORK" to "192.168.102.0/24" and i start qBittorent it does not tell me "Port Mappings (App to Host)" information.

 

Is there something else i need to fix or is it a limitation within your scripts?

[binhex]

37 minutes ago, DigitalLF said:

and my computer is on VLAN 100 (192.168.100.2).

 

37 minutes ago, DigitalLF said:

and changed the docker setting "Key 10:"/"LAN_NETWORK" to "192.168.102.0/24"

that's your problem, your pc is on a different network to your container, append your computers vlan to the list using a comma for LAN_NETWORK, so it ends up looking like:- '192.168.100.0/24,192.168.102.0/24'

[DigitalLF]

@binhex OH! i thought that could be it but i tried that about a year ago and i had a memory that was not possible! Stupid mistake! Thank you kindly!

[BUSTER]

8 hours ago, binhex said:

ok that all looks fine, your log shows nothing wrong and your LAN_NETWORK is defined correctly, try access from another browser, if not try another machine, there maybe anti virus or similar blocking access to port 8080 perhaps.

you right, i cant understand other web browser issue solved in my case thank you @binhex 

you are the best

 

cYa BUSTER

[OriginalFlavor]

Cannot reach webui on port 8083.

command_execution.txt

supervisord.log

[wgstarks]

6 hours ago, OriginalFlavor said:

Cannot reach webui on port 8083.

command_execution.txt 1.54 kB · 0 downloads

supervisord.log 29.55 kB · 0 downloads

Since you are running the webui on a custom port you also need to add a port mapping for it.

 

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

 

Scroll down to Q4.

[OriginalFlavor]

I think I already had done this.

Looking in my supervisor.log

 -p '8083:8083/tcp'

Does this look correct?

If it looks okay, what else should I check?