4 minutes ago, wgstarks said:

If you open the wg0.conf file

If you scroll back a bit, you'll see that this is part of my problem. I have no such file.
My installation isn't creating/downloading/(whatever is supposed to be happening) the WG configuration.

I've tried deleting the entire container and starting over, and it does the same thing.

23 minutes ago, Elmojo said:

If you scroll back a bit, you'll see that this is part of my problem. I have no such file.
My installation isn't creating/downloading/(whatever is supposed to be happening) the WG configuration.

I've tried deleting the entire container and starting over, and it does the same thing.

Just to be sure, did you follow these instructions when you setup WireGuard-

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

Scroll down to Q21.

22 hours ago, wgstarks said:

did you follow these instructions when you setup WireGuard-

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

Scroll down to Q21.

I did not, because the setup guide didn't say anything about doing that, and also because the new template looks different, and doesn't have those options.

I figured that FAQ entry was OBE, and @binhex just hadn't had a chance to update/remove it yet. For example, the FAQ says to "Change Docker parameter from --cap-add=NET_ADMIN to --privileged=true". There is no such parameter any more. It now has a toggle for running the docker as privileged.
Also, the next line in the FAQ talks about adding an "environment variable" with key "VPN_CLIENT". This appears to now be handled by the existing template variable of the same name, and WG is a drop-down option. My understanding was that simply selecting 'wireguard' (vs OpenVPN) in that variable selector was all that was required to enable WG, and that it should then auto-gen the wg0.conf file, which mine is not doing.
If I'm incorrect about that, someone please let me know, because I sure don't see a way to do it as outlined in Q21 of the FAQ...

Does anybody else have random DNS issues where you have to switch PIA endpoints 50000 times to find one that works? I am using PIA VPN with port forwarding. Is there any fix to this? What could be causing these DNS issues where it cannot find the PIA IP? Log attachedsupervisord.log

On 1/13/2025 at 11:05 AM, binhex said:

i will take a look, im in the middle of some changes at the moment amongst other things so it might be delayed, can i ask why you need libtorrent v1?

Is there anything in the works for this? Libtorrentv2 has a lot of issues, especially for systems like Unraid, but it's complicated enough to understand that most people have no idea and just assume the newer version is better, without realizing that performance is often worse. V2 was when libtorrent switched to memory mapped files which is part of why qbittorrent uses so much RAM. Libtorrent v2 has been out for 5 years now without fixing these core issues, and the developer has acknowledged them but still doesn't know how to fix them. There are posts for years on the libtorrent github and the qbittorrent github about this debate, and I'm not an expert so I won't try to understand all the complications involved, but it's very clear there's a lot of problems with v2 and that v1 should at least be an option. The qbittorrent team releases a v1 and v2 version of the program for every release, it would be very helpful to have this option since v2 does cause problems for Unraid users, whether we know it or not.

Is this something that could be implemented with a simple environment variable that users can modify for v1 or v2, or would it require a fully separate branch? I know you already have a libtorrentv1 image, but it's extremely outdated and I can't tell if it was actually intended to be used by many people.

Hi,

I'm looking for some help to solve my binhex-qbittorrentvpn setup.

I've been trying around for hours now but I'm totally unable to connect to the webinterface.

To be clear: To start with, I have no VPN enabled (yet). (I want to see it fully operational before spending money). Privoxy is not enabled either.

What I've tried so far:

• go into the docker console

• tested pinging one docker container to another (works)

• uninstall the binhex-qbittorrentvpn and reinstall

• using Finder (macos) went into the //unraid/appdata/binhex-qbittorrentvpn/qBittorrent/config/ folder and edited the qBittorrent.conf file to add the famous WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)" line

There is no way I can connect to the webinterface of qBittorrent.

I'm under the impression that the container is running but that the error is somewhere in the port configuration, however I followed AlienTech42's excellent youtube instructions to check my setup.

Whatever I do, I keep getting "The 192.168.231 site refused to connect"

Here are some screenshots of my system:

From the log:

2025-06-05 10:58:08,904 DEBG 'watchdog-script' stdout output:

[info] Attempting to start qBittorrent...

2025-06-05 10:58:08,912 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process started

[info] Waiting for qBittorrent process to start listening on port 8080...

2025-06-05 10:58:09,153 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process listening on port 8080

What I noticed is that changing the 8080 port seems not to be taken into account when doing a right-click > WebUI. So e.g. when I set the UI port to 9090, the right-click > WebUI keeps going to IP:8080.

That's also why I have not changed that port setting, just to avoid any problem there.

I've tried using several browsers: Safari, Brave but nothing helps.

I keep getting the refused to connect error.

If you need any more information, please let me know.

Thanks for helping out!

P.S. I also have binhex-krusader running and that docker container runs fine.

40 minutes ago, panini said:

What I noticed is that changing the 8080 port seems not to be taken into account when doing a right-click > WebUI. So e.g. when I set the UI port to 9090, the right-click > WebUI keeps going to IP:8080.

That's also why I have not changed that port setting, just to avoid any problem there.

well according to your screenshots i see no sign of port 8080 at all, so looks like you have deleted the port, or changed it to something else



If you want to change the port to something other than 8080 then follow Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Thanks for answering!

Well, I agree with what you point out. But I have / and am really trying out all ports, but apparently I can not remotely connect.

Just to clarify a bit:

• first did an install months ago, but could not connect. Due to time constraints abandoned.

• Then, yesterday, tried to get it working, to no avail.

• Then, today, removed the docker container and started out afresh.

  

• Can't reach the unraid server on any of these ports 58946 / 8118 / 8585 / 9118

• To be 100% complete, here's a full screenshot of the current settings:

  

===========================================================================

This was the previous install & test (can be discarded)

2 minutes ago, panini said:

Then, today, removed the docker container and started out afresh.

You probably reinstalled from Previous Apps, carrying over your bad config instead of starting with a fresh template.

You've changed WEBUI_PORT, there should be no reason to change it from the default 8080.

You've changed both sides of the webui port map, only the editable one should be changed, the container port must match the WEBUI_PORT.

Edited June 5, 20251 yr by Kilrah

Ok, thanks.

I was / am totally unsure about all the various port addresses available. Also, I had no need to change any default port, so I just tried to follow instructions.

What I find odd: (or do I misunderstand?) In general UI you have default settings and then you have the "set" value. This would then lead to e.g. a default value of 8080 and a set value of 8585, but it would not allow you to "change" the default value (since then it would not be a default anymore)

Anyway, I've set both the ones that Kilrah highlighted to the same (8585) and now at least I can remotely log on using the webinterface!!

Thanks a ton!

2 minutes ago, panini said:

This would then lead to e.g. a default value of 8080 and a set value of 8585, but it would not allow you to "change" the default value (since then it would not be a default anymore)

Assuming you're talking of the template system, the default value just becomes the set value on a fresh template install if nothing else is specified and isn't used again afterwards.

Ok, now that I have access, let's try to solve the next issue:

• Following AlienTech42's example I've looked up a couple of torrents and added them to qBittorrent.

• It seems as if they start downloading, but after a couple of seconds, half a minute, they error out?

• Looking at the detail: error: Permission denied => so that applies to my downloads folder

Question:

• How to set a Docker instances read /write acces to a shared folder?

• As what user does the qBittorrentvpn docker instance operate? (viewed from the shared folders of unraid)

5 minutes ago, panini said:

Ok, now that I have access, let's try to solve the next issue:

• Following AlienTech42's example I've looked up a couple of torrents and added them to qBittorrent.

• It seems as if they start downloading, but after a couple of seconds, half a minute, they error out?

• Looking at the detail: error: Permission denied => so that applies to my downloads folder

Question:

• How to set a Docker instances read /write acces to a shared folder?

• As what user does the qBittorrentvpn docker instance operate? (viewed from the shared folders of unraid)

Should be 99|100 "user|nobody"

H20King,

Thanks for replying.

That's what the values are in qBittorrentvpn config.

Should the Variable: UMASK be set differently to allow for the Docker container to write to the share location?

Use ls -l on the dir and file to see what they are set at

Edited June 5, 20251 yr by H2OKing

Ok, seems logic, but:

• I suppose you want to know this information when ssh'ed into the unraid server?

• As far as "me" as a share user, (macOS) I have full read / write authority on the (Public) shares.

They seem to be set to user: nobody?

How to proceed from here?

drwxrwxr-x 1 nobody users    163 Jun  4 19:25 ./

drwxrwxrwx 1 nobody users    197 Jun  4 18:59 ../

drwxrwxr-x 1 nobody users      6 Jun  4 19:00 completed/

drwxrwxr-x 1 nobody users      6 Jun  4 19:00 incomplete/

-rw-r--r-- 1 root   root     164 Jun  4 19:25 perms.txt

drwxrwxrwx 1 nobody users    246 Jun  4 19:25 privoxy/

drwxrwxrwx 1 nobody users     61 Jun  4 19:25 qBittorrent/

-rw-rw-rw- 1 nobody users 109915 Jun  5 17:19 supervisord.log

drwxrwxr-x 1 nobody users      6 Jun  4 19:00 unzipped/

root@Tower:/mnt/user/downloads# 

Edited June 5, 20251 yr by panini

incomplete/

-rw-r--r-- 1 root root

Id

20 minutes ago, panini said:

Ok, seems logic, but:

• I suppose you want to know this information when ssh'ed into the unraid server?

• As far as "me" as a share user, (macOS) I have full read / write authority on the (Public) shares.

They seem to be set to user: nobody?

How to proceed from here?

drwxrwxr-x 1 nobody users    163 Jun  4 19:25 ./

drwxrwxrwx 1 nobody users    197 Jun  4 18:59 ../

drwxrwxr-x 1 nobody users      6 Jun  4 19:00 completed/

drwxrwxr-x 1 nobody users      6 Jun  4 19:00 incomplete/

-rw-r--r-- 1 root   root     164 Jun  4 19:25 perms.txt

drwxrwxrwx 1 nobody users    246 Jun  4 19:25 privoxy/

drwxrwxrwx 1 nobody users     61 Jun  4 19:25 qBittorrent/

-rw-rw-rw- 1 nobody users 109915 Jun  5 17:19 supervisord.log

drwxrwxr-x 1 nobody users      6 Jun  4 19:00 unzipped/

root@Tower:/mnt/user/downloads# 

Cat this perms.txt

Share docker compose

Share the directory settings in qBittorrent

Thanks for sticking with me! 😅

root@Tower:/mnt/user/downloads# cat perms.txt

This file prevents permissions from being applied/re-applied to '/config', if you want to reset permissions then please delete this file and restart the container.

root@Tower:/mnt/user/downloads# clear

How do I share docker compose? (I tried running docker compose in the docker terminal but that issued a command not found)

• I assume this is the plugin: Docker Compose Manager?

  I've installed it but I don't immediately see how to use it?
  It's added a compose stack?

• where to run this command? How to specifically run it? (tried in the docker terminal + while ssh'ed into the unraid machine.

Directory settings in qBittorrentvpn:

• Nothing specified, only the standard settings:
  Path: /config: /mnt/user/downloads
  Other folders like completed / incomplete are within the /mnt/user/downloads folder

• Or do you mean this?

• 
  
  

Hope this gives sufficient information?

Edited June 5, 20251 yr by panini

Change a setting in the template then click apply and then copy the compose that pops up

I assume you expected / wanted the compose plugin to be triggered?

I've set the Variable:DEBUG to true

but nothing happened?

Edited June 5, 20251 yr by panini

Like this

Update Container

Stopping container: qbittorrent

Successfully stopped container 'qbittorrent'

Removing container: qbittorrent

Successfully removed container 'qbittorrent'

Command execution

docker run

-d

--name='qbittorrent'

--net='proxynet'

--pids-limit 2048

--privileged=true

-e TZ="America/Chicago"

-e HOST_OS="Unraid"

-e HOST_HOSTNAME="UNRAID"

-e HOST_CONTAINERNAME="qbittorrent"

-e 'VPN_ENABLED'='no'

-e 'VPN_USER'=''

-e 'VPN_PASS'='passwoed'

-e 'VPN_PROV'='airvpn'

-e 'VPN_CLIENT'='wireguard'

-e 'VPN_OPTIONS'=''

-e 'STRICT_PORT_FORWARD'='yes'

-e 'ENABLE_PRIVOXY'='yes'

-e 'WEBUI_PORT'='8083'

-e 'LAN_NETWORK'='10.1.60.0/24'

-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 'VPN_OUTPUT_PORTS'=''

-e 'DEBUG'='false'

-e 'UMASK'='000'

-e 'PUID'='99'

-e 'PGID'='100'

-e 'VPN_INPUT_PORTS'='2468'

-l net.unraid.docker.managed=dockerman

-l net.unraid.docker.webui='http://[IP]:[PORT:8083]/'

-l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'

-p '6881:6881/tcp'

-p '6881:6881/udp'

-p '8118:8118/tcp'

-p '8083:8083/tcp'

-p '33253:33253/tcp'

-v '/mnt/user/data/':'/data':'rw'

-v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'

--sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn:latest'

126fb778a5ce11c3ce8b2574ed96da1d8f646dfe47edce2de46316e09719515e

The command finished successfully!

Sorry to be so obnoxious, but where do you enter that command?

The Docker console?

Think I got it:

Pulling image: binhex/arch-qbittorrentvpn:latestIMAGE ID [1998209513]: Pulling from binhex/arch-qbittorrentvpn.
Status: Image is up to date for binhex/arch-qbittorrentvpn:latest

TOTAL DATA PULLED: 0 B

Stopping container: binhex-qbittorrentvpn

Successfully stopped container: binhex-qbittorrentvpn

Removing container: binhex-qbittorrentvpn

Successfully removed container: binhex-qbittorrentvpn

Command executiondocker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/Paris"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='no'
  -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.1.0/24'
  -e 'WEBUI_PORT'='8585'
  -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'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]'
  -l net.unraid.docker.icon=''
  -p '8585:8585/tcp'
  -p '8118:8118/tcp'
  -p '9118:9118/tcp'
  -p '58946:99/tcp'
  -p '58946:100/udp'
  -v '/mnt/user/downloads/':'/config':'rw'
  -v 'binhex-shared':'/shared':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

f99be7356669b4e01ed2fa0c865a89828f3b8e5b03b407169753b626ef64b223

The command finished successfully!

Allthough I'm not sure I properly understand you..

I did this by clicking on force update

But the file permission issue is still there..

I seem to have got it working:

Added a Path variable, like this.