[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

June 13, 20251 yr

On 6/12/2025 at 12:47 PM, vast said:
For a while now I've been having issues with the client using excessive CPU resources. All of my cores are running on 100% which only leaves me with hyper-threads. I'm not sure what's going on. The torrent client isn't even downloading anything. The logs don't seem to indicate anything special either:
2025-06-12 17:47:44,059 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32775'
2025-06-12 17:57:44,127 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32775'
2025-06-12 18:07:44,167 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32775'
2025-06-12 18:17:44,208 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32775'
2025-06-12 18:27:44,248 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32775'
2025-06-12 18:37:44,290 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32775'
I have looked into the other supervisord files as well and I'm not sure what to look for, it all seems relatively normal for me. Any input would really help!

So i had a similar issue and it was due to me setting the MAX HTTP announce way to high (set it to 50), check and see if that setting under the advanced settings (in the webUI) towards the bottom is > 50.

Edited June 13, 20251 yr by Kognac

Quote

Replies 5.2k
Views 1.1m
Created 7 yr7 yr
Last Reply 3 days3 days

Popular Days

Posted Images

June 14, 20251 yr

8 hours ago, Kognac said:
So something odd I have noticed is that it seems the port assigned via the VPN (proton) isnt updating on the qbit container correctly, I was having a weird tracker connectivity issue where I had to manually set the Incoming port on the configuration in unraid, and after I did that everything started connecting correctly. Thankfully with proton the Port assigned doesnt normally change if you do a quick disconnect and reconnect (IE restarting the container)
There wasn't really any logs about it, qbit seemed to think it had correctly assigned the port:

2025-06-13 13:39:59,562 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port for 'protonvpn'
2025-06-13 13:39:59,566 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'
2025-06-13 13:40:01,629 DEBG 'start-script' stdout output:
initnatpmp() returned 0 (SUCCESS)
using gateway : 10.0.0.0
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned 0 (OK)
Public IP address : *.*0.0
epoch = 000000
closenatpmp() returned 0 (SUCCESS)
2025-06-13 13:40:02,490 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.0.0.0 different, marking for reconfigure
2025-06-13 13:40:02,502 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running
2025-06-13 13:40:02,503 DEBG 'watchdog-script' stdout output:
[info] qBittorrent incoming port 6881 and VPN incoming port 33333 different, marking for reconfigure
2025-06-13 13:40:02,505 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...
2025-06-13 13:40:02,577 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...
2025-06-13 13:40:02,586 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...
2025-06-13 13:40:55,637 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

But in the logs on the Web UI i see this before I manually assigned the port in the unraid qbit config on the webportal: [CRITICAL] Failed to listen on IP. IP: "10.0.0.0". Port: "TCP/33333". Reason: "Address already in use"

also was unable to manually assign the Port in the Qbit Web UI for the incoming port, it still was displaying the old port from when my internet reconnected last night. Even though according to the old logs it had gone though the same steps of reconnecting and reassigning the new port.

Another thing I have noticed aswell is that it is somehow using two IPs over the VPN, I dont know how that is possible but I see it using two different IPs on a website.

2025-06-13 22:35:14,172 DEBG 'start-script' stdout output:

[info] Successfully retrieved external IP address 10.10.10.40

2025-06-13 22:35:14,173 DEBG 'start-script' stdout output:

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

2025-06-13 22:35:14,176 DEBG 'start-script' stdout output:

[info] WireGuard interface 'up'

2025-06-13 22:35:16,233 DEBG 'start-script' stdout output:

initnatpmp() returned 0 (SUCCESS)

using gateway : 10.0.0.1

sendpublicaddressrequest returned 2 (SUCCESS)

readnatpmpresponseorretry returned 0 (OK)

Public IP address : 10.10.10.52

epoch = 796801

closenatpmp() returned 0 (SUCCESS)

2025-06-13 22:35:17,115 DEBG 'watchdog-script' stdout output:

[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.0.0.2 different, marking for reconfigure

2025-06-13 22:35:17,128 DEBG 'watchdog-script' stdout output:

[info] qBittorrent not running

2025-06-13 22:35:17,128 DEBG 'watchdog-script' stdout output:

[info] qBittorrent incoming port 6881 and VPN incoming port 33000 different, marking for reconfigure

so i don't know why but the script is not updating the public ip

Quote

June 15, 20251 yr

for whatever reason default password is screwed up,

adding below to qbit config reset it to admin/adminadmin

WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)"

Quote

June 20, 20251 yr

So it seems like my instance has gotten screwed up somehow, over the last 2 days, the RAM usage has shot WAY up (+16G) and I can't seem to find any real troubleshooting tips. Logs seem clear (not constant noise), but anyone have any tips for hunting down the culprit(s)?

Quote

June 21, 20251 yr

hello all. new to binhex-qbittorentvpn docker.

Using binhex-qbittorrentvpn. With no VPN enabled. Just for now.

Docker keeps going down after like 17 hours of up time. Just using this as a temp seedbox for trial till i get my VPN swapped over.

I am seeding only like 20 torrents atm. Shouldn't be taxing the system? I check my unraid dashboard and nothing is being taxed. this is my only Docker running. No VMs.

my docker is running on an old M4 Cruical. lots of older tech in this built.

I checked the logs.

Jun 20 22:11:46 JONSBON3 kernel: bash[245188]: segfault at 40 ip 000014e54d967e50 sp 00007fffb9835468 error 4 in libc.so.6[b8e50,14e54d8d3000+171000] likely on CPU 1 (core 1, socket 0)
Jun 20 22:11:46 JONSBON3 kernel: Code: c0 48 d3 fa 48 85 d2 74 11 48 0f bc c2 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 66 0f ef c9 66 0f ef d2 66 0f ef db 0f 1f 40 00 <66> 0f 6f 40 40 66 0f da 40 50 66 0f da 40 60 66 0f da 40 70 66 0f
Jun 20 22:11:46 JONSBON3 kernel: supervisord[244988]: segfault at 40 ip 0000155224ec6e50 sp 00007ffec197b818 error 4 in libc.so.6[b8e50,155224e32000+171000] likely on CPU 1 (core 1, socket 0)
Jun 20 22:11:46 JONSBON3 kernel: Code: c0 48 d3 fa 48 85 d2 74 11 48 0f bc c2 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 66 0f ef c9 66 0f ef d2 66 0f ef db 0f 1f 40 00 <66> 0f 6f 40 40 66 0f da 40 50 66 0f da 40 60 66 0f da 40 70 66 0f
Jun 20 22:11:46 JONSBON3 kernel: docker0: port 1(vethc7cef81) entered disabled state
Jun 20 22:11:46 JONSBON3 kernel: veth4bcc78e: renamed from eth0
Jun 20 22:11:46 JONSBON3 kernel: docker0: port 1(vethc7cef81) entered disabled state
Jun 20 22:11:46 JONSBON3 kernel: vethc7cef81 (unregistering): left allmulticast mode
Jun 20 22:11:46 JONSBON3 kernel: vethc7cef81 (unregistering): left promiscuous mode
Jun 20 22:11:46 JONSBON3 kernel: docker0: port 1(vethc7cef81) entered disabled state

two segfaults from kernel on bash and supervisord

error 4 in libc.so.6

Is it bad ram? bad cpu? i have plenty of RAM. I ran a full memtest on these sticks of RAM before running unraid. 4 of 4 full pass over 18 hours.

Running Intel® Core™ i5-3450 CPU. ASRock H77M-ITX. 16GB DDR3 1600Mhz Corsair RAM. Using a generic ebay LSI 9300-8i, with 40mm fan. Unraid has been generally flawless except for this docker going down. Doing test run with another docker app (chrome) to see if it dies after 17 hr.

Any ideas?

Edited June 21, 20251 yr by milkmandan

Quote

June 22, 20251 yr

@milkmandan That would normally be due to CPU issues, at least those errors but normally those dont cause the docker to crash and burn unless you have it limited to that one core. It is a really old CPU though to be fair.

Quote

June 24, 20251 yr

I'm getting horrible memory leakage with one of my qbittorrent instances. I'm currently on the latest binhex container, unraid 6.12.15. I currently have the memory limit at 10G so once the leak gets to that point, the container crashes and restarts. If I don't have that limit, it will use up 100% of the memory eventually and crash the whole server.

I have tried the following so far based on my own search but none of them works

-WebUI memory leakage when more than 2 instance WebUI tabs are open at the same time.

-Disk read type to default or simple read/write or POSIX compliant

-physical ram limit to 512 mb

-most other advanced settings are all default

-tried lib torrent 1.2.x and 2.0

-tried lsio qbit container and still had the same problem

I'm at my wits ends in terms of trying to find a fix. Im doubtful there's ever a solution maybe side from switching to a totally different client but I figure I post here just in case someone might know.

Edited June 24, 20251 yr by tlou

Quote

June 24, 20251 yr

I am looking for support for binhex - qBittorrent no VPN. I do not see a forum for it. I have a VPN - VLAN with a kill switch.

This was working fine, but the Docker on UnRaid updated and it fails. Looking for a VPN. Any thoughts would be helpful

text error warn system array login

/usr/lib/python3.13/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.

import pkg_resources

Created by...

___. .__ .__

\_ |__ |__| ____ | |__ ____ ___ ___

| __ \| |/ \| | \_/ __ \\ \/ /

| \_\ \ | | \ Y \ ___/ > <

|___ /__|___| /___| /\___ >__/\_ \

\/ \/ \/ \/ \/

https://hub.docker.com/u/binhex/

2025-06-23 20:42:55.369756 [info] Host is running unRAID

2025-06-23 20:42:55.389246 [info] System information: Linux 88a3b956e33a 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 GNU/Linux

2025-06-23 20:42:55.409175 [info] Image tags: BASE_RELEASE_TAG=2025061403,IMAGE_RELEASE_TAG=5.1.0-1-01

2025-06-23 20:42:55.430582 [info] PUID defined as '99'

2025-06-23 20:42:55.603342 [info] PGID defined as '100'

2025-06-23 20:42:55.806259 [info] UMASK defined as '000'

2025-06-23 20:42:55.829506 [info] Permissions already set for '/config'

2025-06-23 20:42:55.852692 [info] Deleting files in /tmp (non recursive)...

2025-06-23 20:42:55.875543 [warn] WEBUI_PORT not defined (via -e WEBUI_PORT), defaulting to '8080'

2025-06-23 20:42:55.899062 [info] Starting Supervisor...

2025-06-23 20:42:56,061 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing

2025-06-23 20:42:56,061 INFO Set uid to user 0 succeeded

2025-06-23 20:42:56,067 INFO RPC interface 'supervisor' initialized

2025-06-23 20:42:56,067 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2025-06-23 20:42:56,067 INFO supervisord started with pid 7

2025-06-23 20:42:57,073 INFO spawned: 'start-script' with pid 59

2025-06-23 20:42:57,074 INFO reaped unknown pid 8 (exit status 0)

2025-06-23 20:42:57,082 DEBG 'start-script' stdout output:

[INFO] Downloading portset.sh from Github to '/usr/local/bin/portset.sh'...

2025-06-23 20:42:57,082 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2025-06-23 20:42:57,083 DEBG 'start-script' stdout output:

[INFO] Download attempt 1/10...

2025-06-23 20:42:57,428 DEBG 'start-script' stdout output:

[INFO] Download complete. Executing portset.sh with arguments provided...

2025-06-23 20:42:57,436 DEBG 'start-script' stdout output:

[INFO] Configuration of VPN incoming port is enabled, starting incoming port watchdog...

2025-06-23 20:42:57,436 DEBG 'start-script' stdout output:

[INFO] Running portset.sh v1.0.0 - created by binhex.

2025-06-23 20:42:57,464 DEBG 'start-script' stdout output:

[ERROR] Unable to determine VPN adapter name, please check your gluetun configuration and ensure the VPN is connected.

2025-06-23 20:42:57,465 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23121265121936 for <Subprocess at 23121266467440 with name start-script in state RUNNING> (stdout)>

2025-06-23 20:42:57,465 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23121264762128 for <Subprocess at 23121266467440 with name start-script in state RUNNING> (stderr)>

2025-06-23 20:42:57,465 WARN exited: start-script (exit status 1; not expected)

2025-06-23 20:42:57,465 DEBG received SIGCHLD indicating a child quit

Quote

June 24, 20251 yr

With update over the last day, I now have two instances of binhexqbit that, when you click "Save" in Settings, nothing happens.

Can view everything, but cannot change Speed settings, Seeding Limits... pretty much stuck with current settings on both.

Can toggle between Global and Alternative Rate Limits on the webUI, and it otherwise seems to be operating well, just can't change settings.

Both downgraded to 5.0.4-3-01 ,which seems to be working fine. I'll just leave them here for a little while before checking for updates again...

Edited June 27, 20251 yr by It's just J.
Added post-downgrade status

Quote

June 24, 20251 yr

Hi,

A couple of days ago, my container started failing even if I didn't change anything from a configuration point of you (the container has been updated but I didn't change anything).

My container has been working without any issues for more than a year now and rolling back to a previous version doesn't seem to change anything.

I'm running this container in Truenas scale which I'm aware isn't unraid but they should work in a similar fashion anyway. Were there any changes in the variables or configuration?

Now the container won't start and I get this error:

2025-06-24 15:58:27.176268+00:00[info] Attempting to bring WireGuard interface 'up'...
2025-06-24 15:58:27.176288+00:002025-06-24T15:58:27.176288823Z
2025-06-24 15:58:27.176802+00:002025-06-24 11:58:27,176 DEBG 'start-script' stderr output:
2025-06-24 15:58:27.176842+00:00error: Found argument 'wg-quick' which wasn't expected, or isn't valid in this context
2025-06-24 15:58:27.176847+00:002025-06-24T15:58:27.176847716Z
2025-06-24 15:58:27.176851+00:00USAGE:
2025-06-24 15:58:27.176900+00:00boringtun-cli [OPTIONS] <INTERFACE_NAME>
2025-06-24 15:58:27.176907+00:002025-06-24T15:58:27.176907735Z
2025-06-24 15:58:27.176928+00:00For more information try --help
2025-06-24 15:58:27.176932+00:002025-06-24T15:58:27.176932277Z
2025-06-24 15:58:27.176936+00:002025-06-24 11:58:27,176 DEBG 'start-script' stdout output:
2025-06-24 15:58:27.176961+00:00[warn] Failed to bring 'up' WireGuard userspace implementation 'boringtun-cli'
2025-06-24 15:58:27.176979+00:002025-06-24T15:58:27.176979823Z

Any idea what could cause that? I'm using Wireguard with Mullvad.

Thank you for the help!

Quote

June 24, 20251 yr

3 hours ago, It's just J. said:
With update over the last day, I now have two instances of binhexqbit that, when you click "Save" in Settings, nothing happens.
Can view everything, but cannot change Speed settings, Seeding Limits... pretty much stuck with current settings on both.
Can toggle between Global and Alternative Rate Limits on the webUI, and it otherwise seems to be operating well, just can't change settings.

I'm in the same boat here - just so happens i've been doing some upgrades on my server and I thought I may have broken config file access or something -- but I've restored appdata from backups, reinstalled the docker, etc. Nothing seems to fix this "save" button not working.

It's driving me insane because I need to modify some qbittorrent settings from WebUI but unfortunately, I cannot.

Quote

June 24, 20251 yr

58 minutes ago, thegimp_ said:
I'm in the same boat here - just so happens i've been doing some upgrades on my server and I thought I may have broken config file access or something -- but I've restored appdata from backups, reinstalled the docker, etc. Nothing seems to fix this "save" button not working.
It's driving me insane because I need to modify some qbittorrent settings from WebUI but unfortunately, I cannot.

You are not the only one. It is driving me nuts

Quote

June 24, 20251 yr

Try switching to the previous release's tag https://hub.docker.com/r/binhex/arch-qbittorrentvpn/tags

Quote

June 24, 20251 yr

16 minutes ago, Kilrah said:
Try switching to the previous release's tag https://hub.docker.com/r/binhex/arch-qbittorrentvpn/tags

That fixed it for me! Thank you!

Quote

June 25, 20251 yr

4 hours ago, Kilrah said:
Try switching to the previous release's tag https://hub.docker.com/r/binhex/arch-qbittorrentvpn/tags

Same problem, but this did not work for me. I went from 5.1.1 and went back to 5.1 as well as 5.0. How far back do I have to go?

Quote

June 25, 20251 yr

5.1.0-1-01 works for me. Have to specify the full tag, if you look at digests/dates 5.1 is a rolling tag so currently points to just the same broken one.

Edited June 25, 20251 yr by Kilrah

Quote

June 26, 20251 yr

Hi all,

I'm having an issue where I can't click save in the settings window. Everything else is functional, I just can't click save to adjust any settings.

I have tried it through multiple different browsers etc. but it doesn't matter, whenever I click save the button just doesn't work, nothing changes, the window stays open and no changes are made. The only thing I have been able to find is this error in the web inspector console every time I click save.

Uncaught TypeError: can't access property "checked", document.getElementById(...) is null

applyPreferences http://192.168.0.10:8080/ line 5 > injectedScript:1154

onclick http://192.168.0.10:8080/:1

2 line 5 > injectedScript:1154:26

applyPreferences http://192.168.0.10:8080/ line 5 > injectedScript:1154

onclick http://192.168.0.10:8080/:1

Quote

June 26, 20251 yr

6 hours ago, ImpactVolly said:
Hi all,

I'm having an issue where I can't click save in the settings window. Everything else is functional, I just can't click save to adjust any settings.

Read the posts right above yours...

Quote

June 26, 20251 yr

9 hours ago, Kilrah said:
Read the posts right above yours...

🤦‍♂️What a face palm moment... Thank you, that fixed the problem

Quote

June 26, 20251 yr

im getting this error on my console when i try to save any settings i change

VM97:1154 Uncaught TypeError: Cannot read properties of null (reading 'checked') at Object.applyPreferences (<anonymous>:1154:60) at HTMLInputElement.onclick ((index):1:25)

	applyPreferences	@	VM97:1154
	onclick	@	(index):1

Quote

June 26, 20251 yr

On 6/25/2025 at 2:12 AM, Kilrah said:
5.1.0-1-01 works for me. Have to specify the full tag, if you look at digests/dates 5.1 is a rolling tag so currently points to just the same broken one.

Can you paste which tag you used because none are working for me as i cant save anything

@Kilrah

Edited June 26, 20251 yr by animeking1987

Quote

June 26, 20251 yr

Following what others posted, this worked for me

Repository: ghcr.io/binhex/arch-qbittorrentvpn:5.1.0-1-01

Quote

June 26, 20251 yr

That worked. when will the latest release be back to normal lol

Quote

June 26, 20251 yr

Author

18 minutes ago, animeking1987 said:
That worked. when will the latest release be back to normal lol

When the qbittorrent dev's fix it (not me) and release a new version

Quote

June 27, 20251 yr

On 6/24/2025 at 3:51 PM, Taipan603 said:
I am looking for support for binhex - qBittorrent no VPN. I do not see a forum for it. I have a VPN - VLAN with a kill switch.
This was working fine, but the Docker on UnRaid updated and it fails. Looking for a VPN. Any thoughts would be helpful
text error warn system array login
/usr/lib/python3.13/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
import pkg_resources
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/
2025-06-23 20:42:55.369756 [info] Host is running unRAID
2025-06-23 20:42:55.389246 [info] System information: Linux 88a3b956e33a 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 GNU/Linux
2025-06-23 20:42:55.409175 [info] Image tags: BASE_RELEASE_TAG=2025061403,IMAGE_RELEASE_TAG=5.1.0-1-01
2025-06-23 20:42:55.430582 [info] PUID defined as '99'
2025-06-23 20:42:55.603342 [info] PGID defined as '100'
2025-06-23 20:42:55.806259 [info] UMASK defined as '000'
2025-06-23 20:42:55.829506 [info] Permissions already set for '/config'
2025-06-23 20:42:55.852692 [info] Deleting files in /tmp (non recursive)...
2025-06-23 20:42:55.875543 [warn] WEBUI_PORT not defined (via -e WEBUI_PORT), defaulting to '8080'
2025-06-23 20:42:55.899062 [info] Starting Supervisor...
2025-06-23 20:42:56,061 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2025-06-23 20:42:56,061 INFO Set uid to user 0 succeeded
2025-06-23 20:42:56,067 INFO RPC interface 'supervisor' initialized
2025-06-23 20:42:56,067 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-06-23 20:42:56,067 INFO supervisord started with pid 7
2025-06-23 20:42:57,073 INFO spawned: 'start-script' with pid 59
2025-06-23 20:42:57,074 INFO reaped unknown pid 8 (exit status 0)
2025-06-23 20:42:57,082 DEBG 'start-script' stdout output:
[INFO] Downloading portset.sh from Github to '/usr/local/bin/portset.sh'...
2025-06-23 20:42:57,082 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-06-23 20:42:57,083 DEBG 'start-script' stdout output:
[INFO] Download attempt 1/10...
2025-06-23 20:42:57,428 DEBG 'start-script' stdout output:
[INFO] Download complete. Executing portset.sh with arguments provided...
2025-06-23 20:42:57,436 DEBG 'start-script' stdout output:
[INFO] Configuration of VPN incoming port is enabled, starting incoming port watchdog...
2025-06-23 20:42:57,436 DEBG 'start-script' stdout output:
[INFO] Running portset.sh v1.0.0 - created by binhex.
2025-06-23 20:42:57,464 DEBG 'start-script' stdout output:
[ERROR] Unable to determine VPN adapter name, please check your gluetun configuration and ensure the VPN is connected.
2025-06-23 20:42:57,465 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23121265121936 for <Subprocess at 23121266467440 with name start-script in state RUNNING> (stdout)>
2025-06-23 20:42:57,465 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23121264762128 for <Subprocess at 23121266467440 with name start-script in state RUNNING> (stderr)>
2025-06-23 20:42:57,465 WARN exited: start-script (exit status 1; not expected)
2025-06-23 20:42:57,465 DEBG received SIGCHLD indicating a child quit

I had the same issue as you.

Fixed by changing the repository to: linuxserver/qbittorrent:5.0.3-libtorrentv1

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 3 days3 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)