October 19, 2025Oct 19

1 hour ago, ryry said:
At some point (due to an update?) my binhex-qbittorrentvpn started giving ERR_CONNECTION_REFUSED when trying to navigate to it. Would anyone be so kind as to point me in the right direction?

Here’s a good place to start.

https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

Quote

October 22, 2025Oct 22

Hello everyone. First of I want to say that I love this docker app. I have the port forwarding working and in qbittorrent I get the green earth symbol that lets me know that I have a good connection. It is awesome.

My problem is the speed. The most I can get at any time total seems to be around 6mb/s. If I connect to the same VPN with my laptop I can get 30+mb/s from the same torrent. Is there a setting in particular I can check?

Thanks!

Quote

October 22, 2025Oct 22

Author

7 hours ago, Prawcess said:
Hello everyone. First of I want to say that I love this docker app. I have the port forwarding working and in qbittorrent I get the green earth symbol that lets me know that I have a good connection. It is awesome.
My problem is the speed. The most I can get at any time total seems to be around 6mb/s. If I connect to the same VPN with my laptop I can get 30+mb/s from the same torrent. Is there a setting in particular I can check?
Thanks!

Please see Q6 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Quote

October 23, 2025Oct 23

19 hours ago, binhex said:
Please see Q6 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thank you for your response, I appreciate it!

Quote

October 23, 2025Oct 23

Unable to connect

Firefox can’t establish a connection to the server at 192.168.0.126:8085.

I followed the instructions in 4th question of the qBittorrentVPN Docker FAQ

Please help!

Command_execution.txt supervisord.log

Edited October 23, 2025Oct 23 by socbutter
revised Command_execution

Quote

October 23, 2025Oct 23

15 minutes ago, socbutter said:
Unable to connect
Firefox can’t establish a connection to the server at 192.168.0.126:8085.
I followed the instructions in 4th question of the qBittorrentVPN Docker FAQ
Please help!
supervisord.qbittorent Command_execution.txt

Check Q4 sections 4 and 5 again. I don’t think you created port 8085:8085 tcp. I don’t see it in the run command.

Quote

October 23, 2025Oct 23

22 minutes ago, wgstarks said:
Check Q4 sections 4 and 5 again. I don’t think you created port 8085:8085 tcp. I don’t see it in the run command.

Please review the updated files.

supervisord.log Command_execution.txt

Quote

October 23, 2025Oct 23

2 minutes ago, socbutter said:
Please review the updated files

Is your browser connecting to the webUI now?

Quote

October 23, 2025Oct 23

Just now, wgstarks said:
Is your browser connecting to the webUI now?

The connection has timed out

The server at 192.168.0.126 is taking too long to respond.

Quote

October 23, 2025Oct 23

25 minutes ago, socbutter said:
The connection has timed out
The server at 192.168.0.126 is taking too long to respond.

And you are connecting from another machine on the same LAN?

Quote

October 23, 2025Oct 23

2 minutes ago, wgstarks said:
And you are connecting from another machine on the same LAN?

My UNRAID ip is 192.168.0.126

My desktop ip is 192.168.0.105

Is this what you ask?

Quote

October 24, 2025Oct 24

On 10/23/2025 at 6:25 PM, socbutter said:
My UNRAID ip is 192.168.0.126
My desktop ip is 192.168.0.105
Is this what you ask?

Sorry, I missed your reply. Looking through the supervisord log a little closer it looks like qbittorrent may not be starting. At least I don’t see it in the log. You might try a different endpoint if you’re still having this issue.

Quote

October 24, 2025Oct 24

1 hour ago, wgstarks said:
Sorry, I missed your reply. Looking through the supervisord log a little closer it looks like qbittorrent may not be starting. At least I don’t see it in the log. You might try a different endpoint if you’re still having this issue.

I tried all the following Private Internet Access VPN Endpoints with Port Forwarding without success. I first stopped the container and modify the wg0.conf file, start container and click webgui. Just timed out. Upon editing wg0.conf the endpoints were modified to append the port number, e.g., Endpoint = ca-ontario.privacy.network:1337

CA Vancouver ca-vancouver.privacy.network

CA Montreal ca-montreal.privacy.network

CA Ontario Streaming Optimized ca-ontario-so.privacy.network

CA Toronto ca-toronto.privacy.network

CA Ontario ca-ontario.privacy.network

Do I manually set up port forwarding port triggering in my router?

Edited October 24, 2025Oct 24 by socbutter
added question

Quote

October 24, 2025Oct 24

9 minutes ago, socbutter said:
Do I manually set up port forwarding port triggering in my router?

No

Sorry. Afraid I’m out of ideas.

Quote

October 25, 2025Oct 25

1 minute ago, wgstarks said:
No
Sorry. Afraid I’m out of ideas.

Thank you for taking the time to help me.

I tried binhex-delugevpn and posted on their forum had similar problem Preferences values were not persistent, returned to default values. Plugins were none existent even after adding them manually.

Radarr, Sonarr and Sabnzb are working.

Thanks again!

Edited October 25, 2025Oct 25 by socbutter
added more info

Quote

October 26, 2025Oct 26

I am using the arch-qbittorrentvpn in docker on my Linux server with PIA VPN/Wireguard, and everything works fine.

However, I want to run a script to run curl against another docker container on the same Linux machine when a torrent is finished, and I'm having problems understanding how to get the traffic to be allowed, and not go through the PIA VPN tunnel for local traffic.

Any help or pointer to documentation (which I have read) would be great.

Quote

October 27, 2025Oct 27

Anyone else having connectibility problems with ProtonVPN? Everything was fine for the longest time but now:

Some time after the container starts, connectibility goes away ('firewalled')
WebUI remains accessible
Proxy remains functional (tested, e.g. Sonarr can fetch data via the proxy)

CanYouSeeMe.org and Test-NetConnection (Powershell) give me a negative response on the IP and TCP port from the logs.

Logs themselves seem to be in order, so I'm not sure what's up.

QB log

2025-10-27 08:51:45,850 DEBG 'watchdog-script' stdout output:

[info] qbittorrent incoming port closed, marking for reconfigure

2025-10-27 08:52:12,954 DEBG 'start-script' stdout output:

[info] Sending 'down' command to WireGuard due to port closed...

2025-10-27 08:52:12,973 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'down'...

2025-10-27 08:52:12,991 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2025-10-27 08:52:13,002 DEBG 'start-script' stderr output:

[#] ip -4 rule delete table 51820

2025-10-27 08:52:13,009 DEBG 'start-script' stderr output:

[#] ip -4 rule delete table main suppress_prefixlength 0

2025-10-27 08:52:13,017 DEBG 'start-script' stderr output:

[#] ip link delete dev wg0

2025-10-27 08:52:13,111 DEBG 'start-script' stderr output:

[#] iptables-restore -n

2025-10-27 08:52:13,128 DEBG 'start-script' stderr output:

[#] '/root/wireguarddown.sh'

2025-10-27 08:52:13,147 DEBG 'start-script' stdout output:

[info] Successfully brought Wireguard interface 'down'

2025-10-27 08:52:13,147 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2025-10-27 08:52:13,169 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

2025-10-27 08:52:13,178 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2025-10-27 08:52:13,186 DEBG 'start-script' stderr output:

[#] ip link add dev wg0 type wireguard

2025-10-27 08:52:13,188 DEBG 'start-script' stderr output:

[#] wg setconf wg0 /dev/fd/63

2025-10-27 08:52:13,190 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.2.0.2/32 dev wg0

2025-10-27 08:52:13,196 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0

2025-10-27 08:52:13,206 DEBG 'start-script' stderr output:

[#] wg set wg0 fwmark 51820

2025-10-27 08:52:13,207 DEBG 'start-script' stderr output:

[#] ip -4 rule add not fwmark 51820 table 51820

2025-10-27 08:52:13,209 DEBG 'start-script' stderr output:

[#] ip -4 rule add table main suppress_prefixlength 0

2025-10-27 08:52:13,210 DEBG 'start-script' stderr output:

[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2025-10-27 08:52:13,214 DEBG 'start-script' stderr output:

[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2025-10-27 08:52:13,216 DEBG 'start-script' stderr output:

[#] iptables-restore -n

2025-10-27 08:52:13,218 DEBG 'start-script' stderr output:

[#] '/root/wireguardup.sh'

2025-10-27 08:52:53,552 DEBG 'start-script' stdout output:

[info] Successfully retrieved external IP address VPNIP from URL 'http://checkip.amazonaws.com'

2025-10-27 08:52:53,555 DEBG 'start-script' stdout output:

[info] Script started to assign incoming port for 'protonvpn'

2025-10-27 08:52:53,562 DEBG 'start-script' stdout output:

[info] Successfully brought Wireguard interface 'up'

2025-10-27 08:52:55,653 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 : VPNIP

epoch = 4200457

closenatpmp() returned 0 (SUCCESS)

I've already created a new .conf file for QB with no luck.

Curious to read anyone's thoughts. Thanks.

Edit: hol' up, this is the library used right? And it says 'To free all used resources, closenatpmp() can be called', which is what is at the end of my log. Why is this container closing up that PMP port at the end? You need it indefinitely. Very curious.

Edit2: restarted and had the logs open on monitor 2. This came by.

QB log 2

2025-10-27 09:48:07,317 DEBG 'start-script' stderr output:

readnatpmpresponseorretry() failed : the gateway does not support nat-pmp

errno=11 'Resource temporarily unavailable'

2025-10-27 09:48:07,318 DEBG 'start-script' stdout output:

[warn] Unable to assign an incoming port for protocol UDP, creating file '/tmp/portfailure' to indicate failure...

2025-10-27 09:48:07,321 DEBG 'start-script' stdout output:

[info] Script finished to assign incoming port

2025-10-27 09:48:11,986 DEBG 'start-script' stdout output:

[info] Sending 'down' command to WireGuard due to incoming port allocation failure...

2025-10-27 09:48:11,993 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'down'...

I'm highly puzzled. The gateway does support NAT-PMP, but still says it doesn't, sometimes?

Edited October 27, 2025Oct 27 by thatsthefrickenlightning

Quote

October 29, 2025Oct 29

Hey, hoping for some help, somehow manged to get proton wireguard working, after restart its broken again, it seems to briefly connect, complains about dns resolution, kills wireguard int and goes back to complaining about dns.

here's what I'm assuming I need config wise

	docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="UnRaid"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='RjIOxxxxxxxxHTQIz+pmp'
  -e 'VPN_PASS'='bDKoyxxxxxxxxxxxxxxxxxO4rhOl'
  -e 'VPN_PROV'='protonvpn'
  -e 'VPN_CLIENT'='wireguard'
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'LAN_NETWORK'='192.168.0.0/24'
  -e 'WEBUI_PORT'='9080'
  -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'='1.1.1.1,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:9080]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '9080:9080/tcp'
  -p '8118:8118/tcp'
  -p '9118:9118/tcp'
  -p '58947:58947/tcp'
  -p '58947:58947/udp'
-v paths obfuscated
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn'

51e472b9d747fbdaf094278f24cf33553094a3be293847300f98ed61c3c3968a

and container logs just look like this, after 12 failures it tries some backup, doesnt say which in debug, builds wireguard as expected and bring webgui up, but after few minutes goes back to failing dns resolutions;

any help would be appreciated, thanks for your work on this.

also like another person mentioned above mine also spits out

2025-10-29 16:46:47,660 DEBG 'start-script' stdout output:

initnatpmp() returned 0 (SUCCESS)

using gateway : 10.2.0.1

sendpublicaddressrequest returned 2 (SUCCESS)

readnatpmpresponseorretry returned -100 (TRY AGAIN)

readnatpmpresponseorretry returned -7 (FAILED)

2025-10-29 16:46:47,660 DEBG 'start-script' stderr output:

readnatpmpresponseorretry() failed : the gateway does not support nat-pmp

errno=11 'Resource temporarily unavailable'

edit;

I'm still confused why... but it works again, I have changed to a different proton vpn server for no real reason pretty sure it did nothing, and added in a ton of public resolvers, why is it always dns...

84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

Edited October 29, 2025Oct 29 by Mizerka

Quote

October 29, 2025Oct 29

@Mizerka I'll have to try that DNS thing.

Edit: problem has gone away on its own for the moment. I handn't troubleshot it any further yet, and already had my suspicions the trouble was on Proton's end. After all, they were claiming no NAT-PMP in the CLI while on servers that are advertised as the opposite.

Edited November 5, 2025Nov 5 by thatsthefrickenlightning

Quote

November 12, 2025Nov 12

Hey gang, I updated the docker earlier today, & since then, most of my torrents no longer show anything in the Content section? The other tabs (General, Tracker, etc.) all seem to be fine... but in almost all the torrents, Content is completely blank. I've tried different browsers & devices to view the Web UI, I restarted the docker, I restarted the full Unraid system, I've force rechecked, I've added brand new torrents... same deal. The ones showing Content are completely random. They're not from different sites or wildly different sizes or added at certain times... one of the new ones I added today shows, the rest don't.

Anyone else come across this, or anyone have any ideas?

Thanks :)

Quote

November 13, 2025Nov 13

22 hours ago, youngnapoleon said:
Hey gang, I updated the docker earlier today, & since then, most of my torrents no longer show anything in the Content section? The other tabs (General, Tracker, etc.) all seem to be fine... but in almost all the torrents, Content is completely blank. I've tried different browsers & devices to view the Web UI, I restarted the docker, I restarted the full Unraid system, I've force rechecked, I've added brand new torrents... same deal. The ones showing Content are completely random. They're not from different sites or wildly different sizes or added at certain times... one of the new ones I added today shows, the rest don't.
Anyone else come across this, or anyone have any ideas?
Thanks :)

Same for me. Just updated my qB docker container a bit earlier today and then I went to grab some torrents where I need to select only certain files and the Content tab is broken! I think it is something with the new version of qB and not just specific to this container or unRAID. Here's a reddit thread where they have the same problem on Proxmox. Also looks like there is a bug on github where they are running on Debian, etc.

May need to revert to a previous version for now until it is fixed.

edit: Reverted back to this release: "binhex/arch-qbittorrentvpn:5.1.2-2-01-" (I think the last 5.1.2 container binhex put on dockerhub). Confirmed the Content tab works again for me on that version. I'll have to remember to revert back to "latest" tag after the bug is fixed and container updated.

Edited November 13, 2025Nov 13 by deusxanime

Quote

November 14, 2025Nov 14

Hi, Is it normal for this docker to keep changing the VPN IP address when using it alongside the PIA OpenVPN Port Forwarding files from the github page?

I failed to find anything in my googling or search of this topic, but maybe I'm not looking for the key words..

Quote

November 18, 2025Nov 18

Hey! I've installed qbittorrent-vpn, and I can't reach the WebUI to even see if everything is configured properly.

Tried to disable the VPN, but no change. Logs looks okay, no particular warning, and the FAQ on Github didn't help.

Is there anything that I could try to have at least some insights on what I could try to get some informations on why I never can land on the WebUI? Thanks!

Quote

November 18, 2025Nov 18

7 hours ago, Lacouenne said:
Hey! I've installed qbittorrent-vpn, and I can't reach the WebUI to even see if everything is configured properly.
Tried to disable the VPN, but no change. Logs looks okay, no particular warning, and the FAQ on Github didn't help.
Is there anything that I could try to have at least some insights on what I could try to get some informations on why I never can land on the WebUI? Thanks!

You’re going to need to at least post your supervisord log and docker run command so others can see what you’ve got happening. Be sure to redact users/passwords.

Quote

November 18, 2025Nov 18

10 hours ago, wgstarks said:
You’re going to need to at least post your supervisord log and docker run command so others can see what you’ve got happening. Be sure to redact users/passwords.

Sure!

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="host"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='no'
  -e 'VPN_USER'='email@email+pmp'
  -e 'VPN_PASS'='password'
  -e 'VPN_PROV'='protonvpn'
  -e 'VPN_CLIENT'='wireguard'
  -e 'STRICT_PORT_FORWARD'='no'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'LAN_NETWORK'='192.168.4.0/22'
  -e 'WEBUI_PORT'='8180'
  -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'='1.1.1.1,1.0.0.1'
  -e 'HEALTHCHECK_COMMAND'=''
  -e 'HEALTHCHECK_ACTION'=''
  -e 'HEALTHCHECK_HOSTNAME'='google.com'
  -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 '8180:8080/tcp'
  -p '8118:8118/tcp'
  -p '9118:9118/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/cache/appdata/binhex-qbittorrentvpn':'/config':'rw'
  -v '/mnt/user/data/torrent/':'/data':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn'

8f4406c62fdfa9f33514c82228beec23f722d0357e70495c7db1a5741cbd09c7

The command finished successfully!

And the supervisord

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

2025-11-18 13:35:53.331919 [info] Host is running unRAID
2025-11-18 13:35:53.345324 [info] System information: Linux 8f4406c62fdf 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May  3 00:12:52 PDT 2025 x86_64 GNU/Linux
2025-11-18 13:35:53.358541 [info] Image architecture: 'amd64'
2025-11-18 13:35:53.371640 [info] Application name: 'qbittorrentvpn'
2025-11-18 13:35:53.384827 [info] Base image release tag: '2025110901'
2025-11-18 13:35:53.398009 [info] Application image release tag: '5.1.3-1-01'
2025-11-18 13:35:53.413152 [info] PUID defined as '99'
2025-11-18 13:35:53.681627 [info] PGID defined as '100'
2025-11-18 13:35:54.071428 [info] UMASK defined as '000'
2025-11-18 13:35:54.086193 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2025-11-18 13:35:54.102768 [info] Deleting files in /tmp (non recursive)...
2025-11-18 13:35:54.121255 [info] VPN_ENABLED defined as 'no'
2025-11-18 13:35:54.134290 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2025-11-18 13:35:54.150166 [info] ENABLE_SOCKS defined as 'no'
2025-11-18 13:35:54.166093 [info] ENABLE_PRIVOXY defined as 'no'
2025-11-18 13:35:54.182183 [info] WEBUI_PORT defined as '8180'
2025-11-18 13:35:54.199733 [info] Starting Supervisor...
2025-11-18 13:35:54,276 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2025-11-18 13:35:54,276 INFO Set uid to user 0 succeeded
2025-11-18 13:35:54,278 INFO RPC interface 'supervisor' initialized
2025-11-18 13:35:54,279 INFO supervisord started with pid 7
2025-11-18 13:35:55,280 INFO spawned: 'start-script' with pid 83
2025-11-18 13:35:55,281 INFO spawned: 'watchdog-script' with pid 84
2025-11-18 13:35:55,281 INFO reaped unknown pid 8 (exit status 0)
2025-11-18 13:35:55,284 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2025-11-18 13:35:55,284 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-11-18 13:35:55,284 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-11-18 13:35:55,284 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22796462580000 for <Subprocess at 22796462571936 with name start-script in state RUNNING> (stdout)>
2025-11-18 13:35:55,284 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22796462172560 for <Subprocess at 22796462571936 with name start-script in state RUNNING> (stderr)>
2025-11-18 13:35:55,284 INFO exited: start-script (exit status 0; expected)
2025-11-18 13:35:55,284 DEBG received SIGCHLD indicating a child quit
2025-11-18 13:35:55,288 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2025-11-18 13:35:55,288 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2025-11-18 13:35:55,304 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2025-11-18 13:35:55,306 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8180...


*** Legal Notice ***
qBittorrent is a file sharing program. When you run a torrent, its data will be made available to others by means of upload. Any content you share is your sole responsibility.

If you have read the legal notice, you can use command line option `--confirm-legal-notice` to suppress this message.

WebUI will be started shortly after internal preparations. Please wait...

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8180
The WebUI administrator username is: XXX
The WebUI administrator password was not set. A temporary password is provided for this session: XXX
You should set your own password in program preferences.
2025-11-18 13:35:55,414 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8180

Quote

[Support] binhex - qBittorrentVPN

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

ulkesh

nraygun

gustyScanner

Posted Images

Unable to connect

Unable to connect

The connection has timed out

The connection has timed out

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)