11 hours ago, wgstarks said:

What IP Address and Subnet Mask are you using for the calculation?

10.0.0.11 and 255.255.255.0

13 minutes ago, Matt0925 said:

10.0.0.11 and 255.255.255.0

When I enter those values into the calculator I get 10.0.0.0/24 which isn’t what you have set in your previous post.

Edited March 17Mar 17 by wgstarks
Added screenshot

3 hours ago, wgstarks said:

When I enter those values into the calculator I get 10.0.0.0/24 which isn’t what you have set in your previous post.

Sorry, I'd been messing with it to see if that could be the issue, however it wasn't. I've got it as 10.0.0.0/24 now and still no luck

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='XXXXX'
  -e 'VPN_PASS'='XXXXX'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'WEBUI_PORT'='8081'
  -e 'LAN_NETWORK'='10.0.0.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_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon=''
  -p '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8081:8080/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/data/torrents/':'/data/torrents/':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn:4.6.7-1-01'


00601d5808a97722f63453d0c95d194231ad897fe9fe116110e686ffbc55a740

7 hours ago, Matt0925 said:

Sorry, I'd been messing with it to see if that could be the issue, however it wasn't. I've got it as 10.0.0.0/24 now and still no luck

Looks like you changed your webui port perhaps? I see that you have a port mapping 8080:8081. I’m not sure why you have that unless it’s a mistake.

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

In Q4 the process to change the webui port is outlined. Step 5 adds the mapping for the new port. Container and host ports should both be 8081.

So I have no clue what changed, it had been working as it was supposed to, I'd switched to 8081 ages ago due to a conflict. But that solved it, thank you very much!

I see you have stopped releasing docker images for arm64. Any particular reason for this? It has stopped both on binhex/arch-qbittorrentvpn and on binhex/arch-sonarr but I can not find any announcements about it. It's a shame because it has been running solid on my Raspberry Pi 5

On 12/28/2025 at 11:50 PM, Olick said:

It's so weird.

Sonarr, Radarr, etc can access my binhex-qbittorrentvpn.

My whole machine is at my friends house, I access it through Tailscale, I have a route to 192.168.1.0/24 (his lan IP). I have access to ALL my dockers from my PC. Also, I just rebooted my server, but it was working before with qbit.

Now, I cant access my qbit webui, but it works from the VM I use as a jumpbox on my friends PC. Is there some place that I need to bind some Tailscale IP?

Solved: For peeps who might find this through Google ad your Tailscale subnet to LAN_NETWORK: x.x.x.x/24, x.x.x.x/24

I love you!! There must have been a recent change because everything worked fine before.

I just had to add my Tailscale subnet (/32 network because it's just me) to the LAN_NETWORK key and my web ui came back! Just did an ipconfig from cmd prompt to find my tailscale IP showing a 255.255.255.255 mask.

I've never had this set up and everything worked fine until a few weeks ago.. no idea what changed.

Hopefully others see this and it helps them :)

Hello, I'm running into an issue and I'm not sure how to solve it. I use ExpressVPN and it has worked well for years. I checked and my username and password etc. are still accurate. The logs push out the same message over and over again.

"2026-03-24 14:37:03,108 DEBG 'start-script' stdout output:

2026-03-24 14:37:03 TCP/UDP: Preserving recently used remote address: [AF_INET]149.19.196.141:1195

2026-03-24 14:37:03 Socket Buffers: R=[212992->1048576] S=[212992->1048576]

2026-03-24 14:37:03 UDPv4 link local: (not bound)

2026-03-24 14:37:03 UDPv4 link remote: [AF_INET]149.19.196.141:1195

2026-03-24 14:37:03,121 DEBG 'start-script' stdout output:

2026-03-24 14:37:03 TLS: Initial packet from [AF_INET]149.19.196.141:1195, sid=763fa9dd deb4e529

2026-03-24 14:37:03,135 DEBG 'start-script' stdout output:

2026-03-24 14:37:03 VERIFY ERROR: depth=0, error=unable to get local issuer certificate: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-11070-2a, [email protected], serial=1031975

2026-03-24 14:37:03 Sent fatal SSL alert: unknown CA

2026-03-24 14:37:03 OpenSSL: error:0A000086:SSL routines::certificate verify failed:

2026-03-24 14:37:03 TLS_ERROR: BIO read tls_read_plaintext error

2026-03-24 14:37:03 TLS Error: TLS object -> incoming plaintext read error

2026-03-24 14:37:03 TLS Error: TLS handshake failed

2026-03-24 14:37:03,135 DEBG 'start-script' stdout output:

2026-03-24 14:37:03 SIGHUP[soft,tls-error] received, process restarting"

1 hour ago, ElementBreaker said:

Hello, I'm running into an issue and I'm not sure how to solve it.

Seems to be an issue with ExpressVPN. I’ve seen several similar posts in other forums with the same verification error. You should probably contact their customer service.

6 hours ago, wgstarks said:

Seems to be an issue with ExpressVPN. I’ve seen several similar posts in other forums with the same verification error. You should probably contact their customer service.

Hmm, I was able to fix it myself. It seems the .ovpn file needed to have the new CA certificate for ExpressVPN added to it. Will binhex need to update the container so the file always gets made with the new CA certificate?

17 hours ago, ElementBreaker said:

Hello, I'm running into an issue and I'm not sure how to solve it. I use ExpressVPN and it has worked well for years. I checked and my username and password etc. are still accurate. The logs push out the same message over and over again.

"2026-03-24 14:37:03,108 DEBG 'start-script' stdout output:

2026-03-24 14:37:03 TCP/UDP: Preserving recently used remote address: [AF_INET]149.19.196.141:1195

2026-03-24 14:37:03 Socket Buffers: R=[212992->1048576] S=[212992->1048576]

2026-03-24 14:37:03 UDPv4 link local: (not bound)

2026-03-24 14:37:03 UDPv4 link remote: [AF_INET]149.19.196.141:1195

2026-03-24 14:37:03,121 DEBG 'start-script' stdout output:

2026-03-24 14:37:03 TLS: Initial packet from [AF_INET]149.19.196.141:1195, sid=763fa9dd deb4e529

2026-03-24 14:37:03,135 DEBG 'start-script' stdout output:

2026-03-24 14:37:03 VERIFY ERROR: depth=0, error=unable to get local issuer certificate: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-11070-2a, [email protected], serial=1031975

2026-03-24 14:37:03 Sent fatal SSL alert: unknown CA

2026-03-24 14:37:03 OpenSSL: error:0A000086:SSL routines::certificate verify failed:

2026-03-24 14:37:03 TLS_ERROR: BIO read tls_read_plaintext error

2026-03-24 14:37:03 TLS Error: TLS object -> incoming plaintext read error

2026-03-24 14:37:03 TLS Error: TLS handshake failed

2026-03-24 14:37:03,135 DEBG 'start-script' stdout output:

2026-03-24 14:37:03 SIGHUP[soft,tls-error] received, process restarting"

I fixed it by just downloading a new .ovpn file from ExpressVPN and replacing the old one with it.

On 2/16/2026 at 3:36 AM, semioniy said:

Howdy, partners.
Just set up Grafana after a couple rounds of OOM and the whole server locking up (48GB RAM, we balling yes) and noticed the constant rise of RAM usage by qBittorrentVPN

Never reported anything like this - what info can I provide to help?

I'm in the same boat as you.

My binhex-qbittorrentvpn has usually used an abnormal amount of RAM. Kind of hovers around 12GB usage. Always starts small, then grows to that and kind of stays there.

Been that way for over a year.

Around the same time you started your issue, I also started getting an issue where mine will just never stop growing, then crash my entire Unraid server.

Now I limit it to 16GB RAM and it still just keep growing and crashing throughout the day. (the container restarts, not that my server is crashing).

I have about 5500 seeds going. Others tell me they have WAAAAAAY more and their RAM usage is around 2GB.

At this point, it's restarting every couple of hours and is causing issues with my private trackers, creating ghost torrents and such.

I've changed all kinds of settings with forum and AI help.

Disabling caching, changing all kinds of numbers, etc.

Nothing is working and I have no idea what else to do unfortunately.

So, I'm right there in the same boat with you.

edit: Welp, today the problem is so bad, qbit won't even load any longer.

Edited March 31Mar 31 by DevanteWeary

On 2/16/2026 at 3:36 AM, semioniy said:

Howdy, partners.

I migrated to hotio's qbittorrent vpn and so far the RAM hasn't gone above 3GB.

pro-tip: Use Qui's backup/restore function to make migration easy.

QQ: A noob question, but where can I see what are the changes new releases that are published? In example for the latest one released, I cannot find that info somewhere.
The reason that I would like to be able to see that is in order to know whether there is a client incompatibility with the trackers that I am using.

Thanks in advance!

Anyone else on PIA having problems with this starting up properly? I'm not sure if PIA have changed the format of the response to what servers have port forwarding enabled. I can see the server I was using seems to be in the list but the name doesn't match now;

"[info] PIA endpoint 'uk-southampton.privacy.network' is NOT in the list of endpoints that support port forwarding shown below:"

2026-04-02 09:47:51,923 DEBG 'start-script' stdout output:

[info] singapore.pvt.site

[info] south-africa.pvt.site

[info] saudi-arabia.pvt.site

[info] uk-southampton.pvt.site

2 hours ago, upthetoon said:

I can see the server I was using seems to be in the list but the name doesn't match now

Looks like PIA has changed their DNS naming but you can edit your ovpn or wg0 file to reflect the new naming.

Going through initial setup and wondering why there are two variables set for the webui specifying 8080 Shouldn't there only be one? If not, and I need to change the port 8080 because it's already in use do these two need to match?

27 minutes ago, TestingUser said:

Shouldn't there only be one?

One is a variable the others is a port mapping. They are both needed in the event that you might want to change the webUI port to avoid conflicts with other containers.

31 minutes ago, TestingUser said:

change the port 8080 because it's already in use do these two need to match?

If you need to change the webUI port to 8081 (for example) you would set webUI to 8081 and set the port mapping to host=8081 and container=8081.

18 minutes ago, wgstarks said:

If you need to change the webUI port to 8081 (for example) you would set webUI to 8081 and set the port mapping to host=8081 and container=8081.

so now I am even more confused, in the pictures I posted there is only two but your saying if I change the webUI port I also have to change host and container. I Don't have host and container options in the setup, do I need to add those with the Add another Path, Port, Variable, Label or Device option at the bottom?

Or do I just update the two variables in the default setup to be the same? so if I changed one of them from 8080 to 8081 I would also change the other to 8081.

10 hours ago, TestingUser said:

Or do I just update the two variables in the default setup to be the same? so if I changed one of them from 8080 to 8081 I would also change the other to 8081

Those aren’t two variables. In your screenshot “Variable: WebUI_Port” is the only variable. “Port: Web Inteface;” is a port assignment. If you click edit for the variable you’ll see that it only has a single field for the port number. If you click edit fort the port assignment you’ll see a field for container port, a second for host port and a third for connection type (which should be tcp). There are also optional sections for naming and description.

You probably already know this but just in case, which docker the qbit app is running inside a container. Giving a number to the webUI variable will set the app to use that port but its inside the container so can’t be reached by anyone outside the container. The port assignment connects the host port (outside the container) to the container port (inside the container).

These should only need to be changed if you want to change from the default and 8081 was just an example. You could use any available port.

Hope this makes sense now.

2 hours ago, wgstarks said:

Those aren’t two variables. In your screenshot “Variable: WebUI_Port” is the only variable. “Port: Web Inteface;” is a port assignment. If you click edit for the variable you’ll see that it only has a single field for the port number. If you click edit fort the port assignment you’ll see a field for container port, a second for host port and a third for connection type (which should be tcp). There are also optional sections for naming and description.

You probably already know this but just in case, which docker the qbit app is running inside a container. Giving a number to the webUI variable will set the app to use that port but its inside the container so can’t be reached by anyone outside the container. The port assignment connects the host port (outside the container) to the container port (inside the container).

These should only need to be changed if you want to change from the default and 8081 was just an example. You could use any available port.

Hope this makes sense now.

I think I understand, sorry for my ignorance still new to docker and learning how it works. If I understand correctly WebUI_Port is the only one I need to make sure isn't already in use by another docker container because Web Inteface is the port the container assigns so I could make them different numbers if I wanted.

I don't want to change the port number, I have to change it since 8080 is already in use by another docker container. All I am trying to figure is if those numbers have to match or of they can be different.

45 minutes ago, TestingUser said:

I think I understand, sorry for my ignorance still new to docker and learning how it works. If I understand correctly WebUI_Port is the only one I need to make sure isn't already in use by another docker container because Web Inteface is the port the container assigns so I could make them different numbers if I wanted.

I don't want to change the port number, I have to change it since 8080 is already in use by another docker container. All I am trying to figure is if those numbers have to match or of they can be different.

If you’re not changing anything you can leave them all as default 8080. If you want to change it from the default you’ll need to change all of them to still have access to the webUI.

So I went and updated the two values, (Port: Web Interface and Variable: WEBUI_PORT) but once the container starts up I can't access the webui, just spins forever. So I went to the FAQ in the docs for qbittorrent and saw that Q4 was going over what I am trying to do so I followed the answer there, but step 3 says to remove `Container Port:` which isn't present at all so I skipped step 3. Continued on setting up as outlined and added the ports. Now the container won't start because the port is already in use.

At this point I don't know what to do other than delete the other docker container that is using 8080 because I can't get this qbit container to work with other ports.

@binhex It seems like the FAQ step 4 needs to be updated or at least clarified because with the current release of the container step 3 doesn't make sense and just skipping it leads to a container that won't start.

Edited April 6Apr 6 by TestingUser
cleaning up typos, adding binhex @

The template you have for this container is newer than the instructions in the FAQ. You didn’t need to add any port mappings since they already exist in the template. You just need to edit the existing mapping. WebUI port just needs to match the host and container port numbers in Port: Web Interface.

If it’s still not working attach your docker run command and supervisord log to your next post. Be sure to redact users/passwords.