[Support] binhex - qBittorrentVPN

Need further help?, please >click< here and follow the instructions.

Further help

Recommended by binhex

November 30, 20232 yr

This also looks like a neat and fast solution, but PLEASE for the love of god change the password from adminadmin after doing this:- https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1330952

qBittorrent password workaround

Recommended by binhex

binhex

May 1, 20242 yr

Looks like a PIA issue with the CRL inline in the ovpn files being malformed, see here:- https://github.com/binhex/arch-qbittorrentvpn/issues/233#issuecomment-2088192316

PIA OpenVPN CRL issue

Recommended by binhex

wgstarks

October 25, 20241 yr

qBittorrent deletion mode change

Recommended by binhex

August 26, 20241 yr

Hello, I'm currently using your docker, it seems to work but I have three small points that I can't figure out.

1. The server is not the one specified in configuration

I'm using ProtonVPN with portforwarding but the server address used is not the one specified in the configuration. I can see it setting the one from the configuration but the public address is nether this one.

2. The port forward does'nt see to work, When I check on https://portchecker.co/check-it it shows as closed.

3. I'm using a unifi router, a wireguard vpn is configured on it so I can remote on the lan from anywhere. It works great for everything except for this docker. I searched and find the point two in https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md But it didn't solve my issue.

Here is my logs, thanks for anyone that can help me

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

2024-08-26 20:31:15.848763 [info] Host is running unRAID
2024-08-26 20:31:15.860957 [info] System information: Linux 1928800438cf 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux
2024-08-26 20:31:15.872977 [info] Image tags: INT_RELEASE_TAG=2024073001,IMAGE_RELEASE_TAG=4.6.6-1-01
2024-08-26 20:31:15.892451 [info] PUID defined as '99'
2024-08-26 20:31:15.935093 [info] PGID defined as '100'
2024-08-26 20:31:16.211946 [info] UMASK defined as '000'
2024-08-26 20:31:16.224841 [info] Permissions already set for '/config'
2024-08-26 20:31:16.281403 [info] Deleting files in /tmp (non recursive)...
2024-08-26 20:31:16.299023 [info] VPN_ENABLED defined as 'yes'
2024-08-26 20:31:16.317607 [info] VPN_CLIENT defined as 'wireguard'
2024-08-26 20:31:16.330413 [info] VPN_PROV defined as 'protonvpn'
2024-08-26 20:31:16.382466 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2024-08-26 20:31:16.401221 [info] VPN_REMOTE_SERVER defined as '185.246.211.193'
2024-08-26 20:31:16.414246 [info] VPN_REMOTE_PORT defined as '51820'
2024-08-26 20:31:16.426209 [info] VPN_DEVICE_TYPE defined as 'wg0'
2024-08-26 20:31:16.438164 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2024-08-26 20:31:16.451014 [info] USERSPACE_WIREGUARD defined as 'no'
2024-08-26 20:31:16.463913 [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-08-26 20:31:16.684150 [info] LAN_NETWORK defined as '192.168.1.0/24'
2024-08-26 20:31:16.700068 [info] LAN_NETWORK exported as '192.168.1.0/24'
2024-08-26 20:31:16.712995 [info] VPN_USER defined as '[email protected]+pmp'
2024-08-26 20:31:16.725831 [info] VPN_PASS defined as 'my_super_secret_password'
2024-08-26 20:31:16.739505 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2024-08-26 20:31:16.752338 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2024-08-26 20:31:16.765317 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2024-08-26 20:31:16.778320 [info] ENABLE_SOCKS defined as 'no'
2024-08-26 20:31:16.791425 [info] ENABLE_PRIVOXY defined as 'no'
2024-08-26 20:31:16.804424 [info] WEBUI_PORT defined as '8080'
2024-08-26 20:31:16.819141 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-08-26 20:31:16.831663 [info] Starting Supervisor...
2024-08-26 20:31:17,731 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2024-08-26 20:31:17,731 INFO Set uid to user 0 succeeded
2024-08-26 20:31:17,748 INFO supervisord started with pid 7
2024-08-26 20:31:18,749 INFO spawned: 'start-script' with pid 271
2024-08-26 20:31:18,750 INFO spawned: 'watchdog-script' with pid 272
2024-08-26 20:31:18,751 INFO reaped unknown pid 8 (exit status 0)
2024-08-26 20:31:18,774 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2024-08-26 20:31:18,774 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-08-26 20:31:18,774 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-08-26 20:31:18,889 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via adapter eth0

2024-08-26 20:31:18,890 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2024-08-26 20:31:18,891 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.1.0/24 via 172.17.0.1 dev eth0 

2024-08-26 20:31:18,891 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 

2024-08-26 20:31:18,891 DEBG 'start-script' stdout output:
--------------------

2024-08-26 20:31:18,893 DEBG 'start-script' stdout output:
iptable_mangle         16384  0
ip_tables              28672  4 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables               45056  15 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_nat,xt_comment,ip6_tables,xt_connmark,iptable_raw,ip_tables,iptable_nat,xt_MASQUERADE,iptable_mangle,xt_mark

2024-08-26 20:31:18,893 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2024-08-26 20:31:18,918 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2024-08-26 20:31:18,918 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 185.246.211.193/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 185.246.211.193/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 wg0 -j ACCEPT
-A OUTPUT -d 185.246.211.193/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 185.246.211.193/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 wg0 -j ACCEPT

2024-08-26 20:31:18,919 DEBG 'start-script' stdout output:
--------------------

2024-08-26 20:31:18,920 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2024-08-26 20:31:18,923 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2024-08-26 20:31:18,946 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2024-08-26 20:31:18,949 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2024-08-26 20:31:18,950 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2024-08-26 20:31:18,951 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.2.0.2/32 dev wg0

2024-08-26 20:31:18,954 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2024-08-26 20:31:18,956 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2024-08-26 20:31:18,982 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2024-08-26 20:31:18,983 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2024-08-26 20:31:18,983 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2024-08-26 20:31:18,984 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2024-08-26 20:31:18,986 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2024-08-26 20:31:18,987 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2024-08-26 20:31:18,989 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2024-08-26 20:31:26,023 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2024-08-26 20:31:26,354 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 185.246.211.202

2024-08-26 20:31:26,355 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port for 'protonvpn'

2024-08-26 20:31:26,355 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2024-08-26 20:31:28,391 DEBG 'start-script' stdout output:
initnatpmp() returned 0 (SUCCESS)
using gateway : 10.2.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned 0 (OK)
Public IP address : 185.246.211.202
epoch = 10233304
closenatpmp() returned 0 (SUCCESS)

2024-08-26 20:31:29,119 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.2.0.2 different, marking for reconfigure

2024-08-26 20:31:29,120 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2024-08-26 20:31:29,120 DEBG 'watchdog-script' stdout output:
[info] qBittorrent incoming port 6881 and VPN incoming port 53758 different, marking for reconfigure

2024-08-26 20:31:29,145 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2024-08-26 20:31:29,155 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2024-08-26 20:31:29,157 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2024-08-26 20:31:29,991 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

EDIT :

Point 3 solved by using the Q32 of https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Point 2 didn't exist, I appear connectable on torrent sites, I was testing the wrong port

Edited August 27, 20241 yr by Powablocks

Quote

Replies 5.2k
Views 1.1m
Created 7 yr7 yr
Last Reply 2 days2 days

Popular Days

Posted Images

August 28, 20241 yr

Author

On 8/26/2024 at 7:49 PM, Powablocks said:

1. The server is not the one specified in configuration

What makes you think that?, remember your external ip address as seen once a vpn tunnel is established and the ip address of the vpn endpoint are NOT the same thing.

Quote

August 28, 20241 yr

9 hours ago, binhex said:

What makes you think that?, remember your external ip address as seen once a vpn tunnel is established and the ip address of the vpn endpoint are NOT the same thing.

Yes you were right I didn't understand it correctly so in final I don't have problem anymore.

Quote

August 29, 20241 yr

i have been using qbittorrentVPN with NordVPN.

i have changed to ProtonVPN with Wireguard. went through the VPN FAQ to change my qbittorentVPN set up from openVPN to wireguard.

Now i can't get to Unraid WebUI

Please help.

supervisor log attached.

supervisord.log

Quote

August 29, 20241 yr

Hi all,

I am new to unraid. i set up multiple dockers using binhex repos ( arr's and qbittorrent). all of them worked great the first time. but due to some problems i had to reformat my disk so i had to install all the dockers again. I did this by reinstall from previous apps. All of them work except qbittorrent-vpn. did a new install for qbittorrentvpn multiple times aswell (get the same problem). If i look at the log i dont see any errors. It says qbittorrent is started and listening on port 8080, but the web ui is not loading. I tried delugevpn aswell but get the same issue. i tried to look for a solution online but can't seem to find any. See attached command execution and supervisord. Any help is apreciated, thanks!!!

command execution.txt supervisord.log

Quote

August 29, 20241 yr

Author

18 minutes ago, bibek108 said:

Hi all,

I am new to unraid. i set up multiple dockers using binhex repos ( arr's and qbittorrent). all of them worked great the first time. but due to some problems i had to reformat my disk so i had to install all the dockers again. I did this by reinstall from previous apps. All of them work except qbittorrent-vpn. did a new install for qbittorrentvpn multiple times aswell (get the same problem). If i look at the log i dont see any errors. It says qbittorrent is started and listening on port 8080, but the web ui is not loading. I tried delugevpn aswell but get the same issue. i tried to look for a solution online but can't seem to find any. See attached command execution and supervisord. Any help is apreciated, thanks!!!

command execution.txt 1.41 kB · 0 downloads supervisord.log 36.18 kB · 0 downloads

The log shows a successful start so nothing obviously wrong, please see Q4 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md and ensure this is not the issue (commonly is).

Quote

August 29, 20241 yr

this was it!! Thank you!

Quote

August 30, 20241 yr

Edit: is it correct that the Wbeui doesn't work if a vpn connectiopn cannot be established? Currentlu i am only able to connect to the Webui if i set VPN_ENABLED to no.

Despite changing the WEBUI_PORT from 8080 to 8090 multiple times, and adding a port mapping 8090:8090, and the log stating "[info] qBittorrent process listening on port 8090" , the damn container isn't listening on 8090. Please note that the line -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' stays at 8080 no matter what you do.

Update log:

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Sufferd"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='no'
  -e 'VPN_USER'='a'
  -e 'VPN_PASS'='a'
  -e 'VPN_PROV'='custom'
  -e 'VPN_CLIENT'='openvpn'
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'LAN_NETWORK'='10.0.0.0/24'
  -e 'WEBUI_PORT'='8090'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'VPN_OPTIONS'=''
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'USERSPACE_WIREGUARD'='no'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='000'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '8118:8118/tcp'
  -p '9118:9118/tcp'
  -p '8090:8090/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  -v '/mnt/user/Familie/Onze downloads/':'/data':'rw'
  -v 'binhex-shared':'/shared':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

b05e3279008f9ac9ee1bf06ee52bc79ce751c119437df827db4a7e723b860eb2

The command finished successfully!

Edited August 30, 20241 yr by peewee67

Quote

August 30, 20241 yr

Author

1 hour ago, peewee67 said:

the damn container isn't listening on 8090. Please note that the line -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' stays at 8080 no matter what you do.

i think the container is listening on 8090, the issue you are seeing is that the template has not been changed to reflect the change in port, so either ignore the web ui link and simply go to http://<your nserver ip>:8090 and then bookmark it in your web browser, or left click the container, select 'edit' click on 'advanced view' top right and change the port for 'WebUI:' to 8090

Quote

August 31, 20241 yr

THANKS! This resolved the porting issue for me - I also needed to free up 8080.... but somehow I've corrupted my log in - I've removed, deleted the appdata entry, and reinstalled the container; but still cannot log in using my old, or the default credentials. Please help..

Quote

August 31, 20241 yr

2 minutes ago, Kev600 said:

THANKS! This resolved the porting issue for me - I also needed to free up 8080.... but somehow I've corrupted my log in - I've removed, deleted the appdata entry, and reinstalled the container; but still cannot log in using my old, or the default credentials. Please help..

Check near the end of the log and you may see temp credentials which are being generated by the app.

Quote

August 31, 20241 yr

@wgstarks thank you for the suggestion - but unfortunately, there's nothing being logged for credentials - and even with default port, VPN=NO, Privoxy=NO - admin/adminadmin is not working.

Quote

August 31, 20241 yr

2 minutes ago, Kev600 said:

@wgstarks thank you for the suggestion - but unfortunately, there's nothing being logged for credentials - and even with default port, VPN=NO, Privoxy=NO - admin/adminadmin is not working.

Attach the contents of supervisord log and your docker run command to your next post. Be sure to redact users and passwords.

Quote

August 31, 20241 yr

OK I removed binhex qbittorrentvpn - Then installed the container from markusmcnugen's repo.

NO issues with logging in with admin/adminadmin.

I then removed that container and reinstalled from binhex's repo.

This then created this issue - again..

docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/binhex-qbittorrentvpn': mkdir /mnt/user: file exists.

I've logged this here:

BUG?

Quote

August 31, 20241 yr

The qbittorrent devs decided a few months back that admin/adminadmin would no longer be allowed so that’s expected not to work with the current version of the app. As for the file already exists error I suspect that you don’t delete the previous appdata folder when you deleted the previous docker. You’ll need to rename the old appdata folder if you want to have a completely clean install but you’ll be starting all over from scratch. Might be better to try and troubleshoot the current install.

Quote

August 31, 20241 yr

Thanks for the quick response - But, I've already conceded to starting over, and removed, deleted the entire 'appdata\binhex qbittorrentvpn' folder - and reinstalled.. several times now.

Something isn't being cleaned up - Because the Apps page shows 'Actions' instead of just 'Install', for the container, when reinstalling it.

As per my last message, the container from a different repo, logs in fine with admin/adminadmin.

Now... after another reboot of my UNRaid server, due to the shfs errors screwing up the access to /mnt - I'm back to using the default ports and not being able to log into the binhex qbittorrentvpn webui.. with anything. No credentials listed in the binhex-qbittorrentvpn.log.

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="KBNAS"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='*********'
  -e 'VPN_PASS'='**********'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='yes'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'LAN_NETWORK'='192.168.0.0/24'
  -e 'WEBUI_PORT'='8080'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='true'
  -e 'VPN_OPTIONS'=''
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'USERSPACE_WIREGUARD'='no'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='000'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '8080:8080/tcp'
  -p '8118:8118/tcp'
  -p '9118:9118/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  -v '/mnt/user/data/media/':'/data':'rw'
  -v 'binhex-shared':'/shared':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

acb3e7fd8a5c5f1d5cfbbcc29827ae7acdab5f0faf98d02fef56f44b8dbb59aa

Quote

August 31, 20241 yr

What about the supervisord log?

Quote

August 31, 20241 yr

7 minutes ago, Kev600 said:

per my last message, the container from a different repo, logs in fine with admin/adminadmin.

Probably using an older version of the app.

Quote

August 31, 20241 yr

20 minutes ago, Kev600 said:

Something isn't being cleaned up - Because the Apps page shows 'Actions' instead of just 'Install', for the container, when reinstalling it.

You would also need to delete the associated file from boot/config/plugins/dockerMan/templates-user/

These are the files that show CA that you had this docker previously installed and preserve your current port and path settings. Delete them and you will have to re-enter all the container settings.

Quote

August 31, 20241 yr

@wgstarks Thank you for your help and quick replies - I found the temp password you were referring to in the supervisord log file - and logged into the WebUI successfully!!

I was previously expecting to find this in the container log!

Thanks again mate!

Quote

August 31, 20241 yr

2 minutes ago, Kev600 said:

was previously expecting to find this in the container log

The container is just a package containing the qbittorrent app. Credentials and settings are a part of the app. All those files and logs will be in appdata. This will apply for most of the dockers.

Quote

September 1, 20241 yr

My qBittorrent for the last year or so has had an issue where every so often, like every couple of days or less, suddenly stops downloading and seeding. Everything becomes stalled. I can't restart the downloads to fix it. I can't add new torrents as they'll just start with no metadata. It's as if the container loses the ability to connect to the internet, but clearly nothing is configured wrong as it works until it doesn't.

However, all I have to do is just restart the container and it goes back to working perfectly fine again until it randomly happens again later.

Does anyone know what could be causing this? I don't see any errors in the logs, just an endless need to restart the container when I notice nothing is downloading.

Quote

September 1, 20241 yr

i have removed my binhex-qbittorrentVPN and reinstalled.

Changed the LAN_NETWORK as per Q4 of the FAQ. i am using wireguard to get my ipconfig as i am remote from my unraid at the moment.

still can't access to WEBUI even though it is listening at port 4445.

Can someone please help?

Thank you

supervisord.log

Edited September 1, 20241 yr by tonnyhii

Quote

September 1, 20241 yr

3 hours ago, tonnyhii said:

i have removed my binhex-qbittorrentVPN and reinstalled.

Changed the LAN_NETWORK as per Q4 of the FAQ. i am using wireguard to get my ipconfig as i am remote from my unraid at the moment.

still can't access to WEBUI even though it is listening at port 4445.

Can someone please help?

Thank you

supervisord.log 9.56 kB · 1 download

Are you using the temp password shown in supervisord.log?

Edited September 1, 20241 yr by wgstarks

Quote

September 1, 20241 yr

1 hour ago, wgstarks said:

Are you using the temp password shown in supervisord.log?

i can't even get to WEBUI, haven't get to key in password yet

Quote

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.

Followers

Go to topic listing

Replies 5.2k
Views 1.1m
Created 7 yr7 yr
Last Reply 2 days2 days

[Support] binhex - qBittorrentVPN

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

ulkesh

nraygun

gustyScanner

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

ulkesh

nraygun

gustyScanner

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)