Hello binhex and everyone,

I've deployed "binhex-delugevpn" container for Unraid and wanted to use the AirVPN wireguard tunnel. I've followed the instructions and the WG tunnel seems to be up (verifed from the AirVPN site). However, all of the torrents do not seem to use the tunnel.

I've consoled into the container and while I have an IP on the WG interface, I do not see any route for it.

ip route

default via 10.69.55.1 dev eth0

10.69.0.0/16 via 10.69.55.1 dev eth0

10.69.55.0/24 dev eth0 proto kernel scope link src 10.69.55.135

What is the proper way to use put in a default route for the WG interface for this container that won't break during updates?

38 minutes ago, djgizmo said:

Hello binhex and everyone,

I've deployed "binhex-delugevpn" container for Unraid and wanted to use the AirVPN wireguard tunnel. I've followed the instructions and the WG tunnel seems to be up (verifed from the AirVPN site). However, all of the torrents do not seem to use the tunnel.

I've consoled into the container and while I have an IP on the WG interface, I do not see any route for it.

ip route

default via 10.69.55.1 dev eth0

10.69.0.0/16 via 10.69.55.1 dev eth0

10.69.55.0/24 dev eth0 proto kernel scope link src 10.69.55.135

What is the proper way to use put in a default route for the WG interface for this container that won't break during updates?

ok, nm. Looks like with wg, when one has AllowedIPs = 0.0.0.0/0 is set in wg config so all traffic gets tunneled.

The IP tables seem to be overally allowed though.

Chain INPUT (policy DROP)

target prot opt source destination

ACCEPT all -- 99.42.179.99 anywhere (vpn server, IP sanitized)

ACCEPT all -- 10.69.55.0/24 10.69.55.0/24

ACCEPT all -- 99.42.179.99 anywhere

ACCEPT tcp -- anywhere anywhere tcp dpt:8112

ACCEPT udp -- anywhere anywhere udp dpt:8112

ACCEPT tcp -- 10.69.0.0/16 10.69.55.0/24 tcp dpt:58846

ACCEPT icmp -- anywhere anywhere icmp echo-reply

ACCEPT all -- anywhere anywhere

ACCEPT all -- anywhere anywhere

Chain FORWARD (policy DROP)

target prot opt source destination

Chain OUTPUT (policy DROP)

target prot opt source destination

ACCEPT all -- anywhere 99.42.179.99

ACCEPT all -- 10.69.55.0/24 10.69.55.0/24

ACCEPT all -- anywhere 99.42.179.99

ACCEPT tcp -- anywhere anywhere tcp spt:8112

ACCEPT udp -- anywhere anywhere udp spt:8112

ACCEPT tcp -- 10.69.55.0/24 10.69.0.0/16 tcp spt:58846

ACCEPT icmp -- anywhere anywhere icmp echo-request

ACCEPT all -- anywhere anywhere

ACCEPT all -- anywhere anywhere

The last 2 lines seem to allow all things to get to all places, which could be a problem if the wg tunnel dropped.

I'm unsure how to properly outside of blocking it at my router level.

Edited July 31, 2025Jul 31 by djgizmo

1 hour ago, djgizmo said:

The last 2 lines seem to allow all things to get to all places, which could be a problem if the wg tunnel dropped.

You are listing the rules using iptables -L try printing the rules instead iptables -S you will then see that the last two rules are actually tied to specific adapters, in this case loopback and the tunnel adapter.

2 hours ago, djgizmo said:

However, all of the torrents do not seem to use the tunnel.

So going back to your original problem, what exactly do you mean by this?, no download?

I just switched VPN providers from Nord to Proton (using OpenVPN for both), and my Deluge gui won't show my IP anymore. On Nord it used to show the IP, but on Proton it just shows N/A. Is there any way to fix this, I like seeing that IP there for piece of mind that the VPN is working.

Hi All, not sure if I'm meant to be posting some logs or more info please let me know so I can try and resolve this issue. Happy to try some more processes to see if this can be resolved but I believe I have tried a few steps and just the lack of connection not sure if the VPN or a setting as no VPN it does work fine.

Or is having some of these style of dockers not running over the VPN container supported? If they arnt I can just remove them but I was hoping to route a few of them over it but if they arnt supported Ill revert back and run them all direct if thats best use-case.

Currently its just prowlarr and flaresolverr for validating the tracker but they both are having the connection issues (As posted above)

Edited August 1, 2025Aug 1 by brent3000

18 hours ago, brent3000 said:

Hi All, not sure if I'm meant to be posting some logs or more info please let me know so I can try and resolve this issue. Happy to try some more processes to see if this can be resolved but I believe I have tried a few steps and just the lack of connection not sure if the VPN or a setting as no VPN it does work fine.

Or is having some of these style of dockers not running over the VPN container supported? If they arnt I can just remove them but I was hoping to route a few of them over it but if they arnt supported Ill revert back and run them all direct if thats best use-case.

Currently its just prowlarr and flaresolverr for validating the tracker but they both are having the connection issues (As posted above)

verify you have set things up correctly, please see Q24 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

if this does not fix it then I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

A quick gift - I have setup a GitHub re-occuring action to generate the list of PIA port forward enabled endpoints, the output is to a public Gist in markdown format, feel free to reference if you want to switch endpoint and you can't be arsed to go searching through your supervisord.log: https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

Note: The URL is NOT expected to change, if it does i will edit the post here.

Friend is babysitting my unraid server for a few months. I have tailscale set up for unraid and am able to access other docker apps fine from outside the network. However I am unable to access my deluge web ui. Can someone please see what has gone wrong please?

2025-08-04 185923,957 INFO reaped u.txt

22 minutes ago, TheRaven117 said:

Friend is babysitting my unraid server for a few months. I have tailscale set up for unraid and am able to access other docker apps fine from outside the network. However I am unable to access my deluge web ui. Can someone please see what has gone wrong please?

2025-08-04 185923,957 INFO reaped u.txt

Resolved,

Q30. I can view the application's Web UI from my home LAN, but whenever I connect to my home LAN using a remote connection (such as Tailscale, Cloudflare, OpenVPN or WireGuard) I can no longer view the application Web UI. I can view all other Docker container Web UIs but not the VPN ones. Why is this and how can I fix it?

A30. This is due to strict iptables rules. You need to add the VPN network to the LAN_NETWORK value using a comma as a separator, e.g. LAN_NETWORK=192.168.1.0/24,192.168.2.0/24. If you are having difficulty calculating the CIDR mask (digits after the forward slash) or figuring out the network then see Q4 above.

I assumed the CIDR instead of using the calculator

as specified in Q4

Q4. I'm struggling to configure LAN_NETWORK correctly. Can you give some examples?

A4. Sure! A common misconception when defining this is to set the IP address to the value of your router or host (server); this is NOT correct. What you need to do is set the value to encapsulate all host IP addresses for your home network, NOT for a particular host on the network. Below are examples of how to identify the correct IP address and CIDR notation (digit(s) after the /):

If you type "ipconfig /all" on a Windows host on your LAN, you will get something similar to this:

Ethernet adapter Ethernet:

  Connection-specific DNS Suffix  . : home.gateway
  Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter
  Physical Address. . . . . . . . . : 11-22-33-44-55-66
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe00::1111:2222:3333:4444%4(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : 17 February 2016 21:10:32
  Lease Expires . . . . . . . . . . : 27 February 2016 11:10:13
  Default Gateway . . . . . . . . . : 192.168.1.1
  DHCP Server . . . . . . . . . . . : 192.168.1.1
  DHCPv6 IAID . . . . . . . . . . . : 55727104
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-4A-97-73-52-54-00-32-3F-43
  DNS Servers . . . . . . . . . . . : 193.1.2.3
  NetBIOS over Tcpip. . . . . . . . : Enabled

or "ifconfig" on Linux/Mac:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.10  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 68:05:ca:0b:fe:25  txqueuelen 0  (Ethernet)
        RX packets 28203743  bytes 36171326044 (33.6 GiB)
        RX errors 0  dropped 19925  overruns 0  frame 0
        TX packets 26710466  bytes 165269242671 (153.9 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

From the above you can see the IP address is 192.168.1.10 and the Subnet Mask (or netmask) is 255.255.255.0, so armed with the IP Address and Subnet Mask, the easiest way to work out the correct values is to use an online calculator, go to: http://www.subnet-calculator.com/cidr.php

1. Enter the host IP address into the 'IP Address' field, in this example '192.168.1.10'.

2. On the dropdown 'CIDR Netmask' select your subnet mask, in this example 255.255.255.0.

3. Copy the value from 'Net: CIDR Notation', which in this example would be 192.168.1.0/24.

4. Paste it into the value for env var 'LAN_NETWORK'.

If you need to be able to access the Web UI from multiple networks, then please use a comma to separate values, e.g.:

LAN_NETWORK=192.168.1.0/24,192.168.2.0/24

I can't get binhex-delugevpn to work at all on my UnRAID system. Please help!

Trying to configure PIA, which I've been using for years on my Windows box and never had any issues. I followed this guide, and my browser currently gives me "ERR_CONNECTION_REFUSED" when attempting to launch the webGUI.

SETTINGS:

Network Type: "Custom : thehog"

Port: Web Interface: 8112

Port: Privoxy: 8118

Port: microsocks: 9118

Port: Deluge daemon: 58846

Variable: VPN_ENABLED: yes

Variable: VPN_USER: (my PIA username)

Variable: VPN_PASS: (my PIA password)
Variable: VPN_PROV: pia

Variable: VPN_CLIENT: wireguard
Variable: STRICT_PORT_FORWARD: yes

Variable: ENABLE_PRIVOXY: yes

The .conf file is edited to connect to Sweden, which allows port forwarding. I enabled debug logging and have linked the logs for the most recent session here: https://pastebin.com/2yPdiDSC.

Also, I don't know if this is relevant, but I have assigned a static IP to my UnRAID server in my router. The server itself is connected via Ethernet to a wireless range extender, which in turn connects to my router. All my other Docker containers work fine, although I have not fully tested my *.arr applications since I have yet to get a VPN/torrenting client working. Any help would be very much appreciated!

Hello,

I changed my ISP and I am having an issue with binhex-delugevpn starting. I cannot access the web UI. There is activity within the container because it is showing CPU and memory usage constant.

I have attached the command execution and supervisor logs.

@binhex any suggestions?

container log supervisord.log

Edited August 17, 2025Aug 17 by Raven6

@binhex

I'm not sure if you remember talking to me on Discord long ago, but we spoke about libtorrentv1 and the deluge containers, I'm ambipro from the deluge dev/support team.

I'm now running a geoip.dat legacy maxmind mirror - it updates every 3 days and you can find it at https://geo.el0.org in both .gz and .dat format, in my LSIO container I am currently testing I have it set to check if the .dat is over a week old on startup, and if so snatch the new one. lsio was using mailfud.org for updates only during the build in githubactions, and these can change. I've included code below that checks the age and pulls the update. This does require changing core.conf to set the geoip.dat to /config/GeoIP.dat though, but you can modify it I suppose. I think its better persistent though.

Also, we still recommend using libtorrentv1 with Deluge 2.2.0, caching settings in the preferences are removed in libtorrentv2 (they don't work at all due to memory mapping) and the performance is better when tweaks are applied.

For anyone looking for tweaks to speed up libtorrent/Deluge you can see my thread (I'm the moderator ambipro posting) where I explain the settings for both Deluge's ltConfig and translate them to qbit's units as well. They can produce DRASTIC improvements, but are not a one size fits all so please read the post carefully.

I also forked my good friend @mhertz ltConfig plugin he is taken over maintaining (although it requires no real work except updating presets) and added my settings I recommend for a "fast gbit server" that I explain the specs of there. You can simply apply them like any other preset in ltConfig.

Finally, Stats was previously disabled in your image, I'm not sure if it still is, but mhertz fixed this and you can include his 0.4.1 version of Stats located in this post https://forum.deluge-torrent.org/viewtopic.php?p=236443#p236443 if you would like to have it (you can include my ltConfig, but that is somewhat an advanced and power user plugin, not sure its appropriate as Stats).

Building libtorrentv1 off fork of your container is rather painful, and I seem to have repeated problems with different things, especially when boost and sandbox were acting up, but I'm no arch users.

We previously spoke on Discord, and I would very much like to go over some of the things I think would improve your container over all others and take care of both delugevpn and standard deluge.

If you could find time, I've sent you messages already and you should be able to recognize who I am. Otherwise you can visit Deluge's discord at https://discord.gg/X6yhJE6ZTr and find me as ambipro

# downlad latest GeoIP.dat after aged a week

geoip_dat_path="/config/GeoIP.dat"

echo "[info] Checking GeoIP.dat ($geoip_dat_path)..."

if [ -e "$geoip_dat_path" ]; then

    current_time=$(date +%s)

    # file's modification and creation times in seconds since epoch

    modification_time=$(stat -c %Y "$geoip_dat_path")

    week_seconds=$((7 24 60 * 60))

    if (((current_time - modification_time) > week_seconds)); then

        echo "[info] Found outdated GeoIP.dat...updating (timeout 10s)"

        curl -s -L --retry 2 --retry-max-time 10 --retry-all-errors \

            "https://geo.el0.org/GeoIP.dat.gz" |

            gunzip >$geoip_dat_path

        chmod 777 $geoip_dat_path

    else

        echo "[info] GeoIP.dat is up to date (downloaded in the last week)"

    fi

else

    echo "[info] No GeoIP.dat found...updating (timeout 10s)"

    curl -s -L --retry 2 --retry-max-time 10 --retry-all-errors \

        "https://geo.el0.org/GeoIP.dat.gz" |

        gunzip >$geoip_dat_path

    chmod 777 $geoip_dat_path

fi

Edited August 22, 2025Aug 22 by ambipro

On 8/13/2025 at 9:21 AM, ambipro said:

I'm not sure if you remember talking to me on Discord long ago, but we spoke about libtorrentv1 and the deluge containers, I'm ambipro from the deluge dev/support team.

I do remember, sorry for the delay in getting back to you i have been floating around on a very large boat for 2 weeks :-), I shall take a lookover the changes and suggestions and get back to you.

binhex, sorry for the confusion if there was any, I do run that mirror - previously my post had autocorrected now to "not" on "I am not running" vs "I am now running"

Please feel free to look over the changes, and if you have any questions let me know.

Discord and PMs here are always open to you if you need.

Has anything changed over the last week or two? Both binhex-delugevpn and binhex-jackett are showing up as version not available in the docker tab on Unraid. Using 7.1.4 if it matters.

@binhex would it be possible for you to push a updated (packages and stuff) release of DelugeVPN and native Deluge on both the libtorrent 2 (master) and libtorrentv1 (libtorrentv1 branch) tags, I noticed they are out of date, particularly the libtorrentv1, and that is the official libtorrent version that we recommend at Deluge.

If possible, can you setup a GHA that triggers both the main and the libtorrentv1 branches when you trigger a build? That way we aren't left behind in features and version/bug fix/etc when a new image is made?

Please let me know if this is possible and when you do it so that I can fork and work on potentially getting a PR for the features and functionality I had in the post I made, if nothing else I would like to have it for my local builds and several of the Deluge community from our forums uses my images (I also maintain a linuxserver fork, but am having some issues right now with it and the host system kernel)

Your deluge based off arch would be highly appreciated, since I can't do it entirely by myself. I still am not super familiar with your base image.

Also ( Off Topic ) - is it possible to run just your arch-base image and get a bare-bones arch docker running where I can get a shell inside the container and treat it like a VM?

Given that there are features in Deluge that ONLY works on libtorrentv1 (referring to the cache preferences and many of the libtorrent settings you can tweak in the plugin I maintain ltConfig (https://github.com/zakkarry/deluge-ltconfig) - it seems more in line that you have libtorrentv1 be the default "master" image and libtorrentv2 be a tag you can use. lt2.0 has quite a few downsides and problems associated with it and v1 also appears more performant when utilizing things like my preset profile in ltConfig.

Edited August 26, 2025Aug 26 by ambipro

hi! so i updated the docker container today on my synology nas and after the update the container automatically stops

the only error i get is

/bin/bash: /usr/local/bin/init.sh: No such file or directory

i tried to duplicate the container and remove the entrypoint and execution command but same issue happens.

any idea how to fix this?

duplicated the container, went to previous version and it works ok.

Edited August 28, 2025Aug 28 by humble-relocation2501

Hello, I recently upgraded from Unraid 7.0.0 to 7.1.4 and my delugevpn UI shows no torrents. I tried to deep dive the issue with the help of AI, but no luck. What i noticed from the folders that the \appdata\binhex-delugevpn\core.conf file always resets to blank state after container restart. But there is a core.conf.bak file with all the data inside. I tried to replace the .bak file contents to regular conf, but still deleted itself on start.

It also forgot my old UI password and always reverts back to the default one. Even all changes that i make in web client don't show up after restart (that one is probably okay, the primary settings should be from the conf file).

Does anyone have an idea what could be wrong?

Edited September 3, 2025Sep 3 by staynoir

Why does checking for port forwarding with PIA take so long sometimes?

2025-09-04 09:34:02,652 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'georgia.privacy.network' is port forward enabled...

2025-09-04 09:42:03,692 DEBG 'start-script' stdout output:
[warn] Json query '.regions | .[] | select(.port_forward==true) | .dns' returns empty result for port forward enabled servers, skipping endpoint port forward check
[info] Script finished to assign incoming port

Using the PIA Mac desktop app, I can connect directly to that endpoint in a matter of seconds.

This took eight minutes and, even then, the line afterwards looks like it timed out and just assumed there was no port forwarding. Is there a variable I can change to reduce the timeout to something a bit more sensible, like 30 seconds?

(And now, after it's printed that line, it's sat there for another four minutes, with no VPN connection and no proxy server — meaning that it's now 16 minutes since I started the container at 09:31 and it still isn't up. It never used to take this long — and, as I said, I can connect from my desktop machine using the PIA app in just a few seconds, so it doesn't seem to be PIA at fault…)

Further update: it seems to be something with the Georgia endpoint; startup was back to the usual speeds when I switched to a different country. It's a pain to have to do this, though, as some services require you to tell them if you're using a VPN, and which country you're using, so you have to go and edit your profile in all of them…

Edited September 4, 2025Sep 4 by ElectricBadger

Ever since the 29th when i restarted the docker i stopped getting access to the webui. I've tried reinstalling the docker with the same credentials etc and still have no access to the webui, same issue with the qbittorrent docker, i've tried installing the base deluge image and it works fine. any binhex-"VPN" docker webui will not work for me. Im curious if it is a PIA VPN issue, because i have not updated anything or changed any settings.

4 hours ago, Deltym said:

Ever since the 29th when i restarted the docker i stopped getting access to the webui. I've tried reinstalling the docker with the same credentials etc and still have no access to the webui, same issue with the qbittorrent docker, i've tried installing the base deluge image and it works fine. any binhex-"VPN" docker webui will not work for me. Im curious if it is a PIA VPN issue, because i have not updated anything or changed any settings.

in my experience, this is usually due to an unsuccessful vpn connection.
I've found PIA endpoints go down from time to time for extended periods, try switching to a different PIA endpoint.

7 hours ago, tjb_altf4 said:

in my experience, this is usually due to an unsuccessful vpn connection.
I've found PIA endpoints go down from time to time for extended periods, try switching to a different PIA endpoint.

Thing is I've tried multiple different servers (Netherlands, Greenland, Switzerland) and still can't get it to work. I get this warning everytime. which i assume having STRICT_PORT_FORWARD set to yes is causing it not to connect?

"[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check"

43 minutes ago, Deltym said:

Thing is I've tried multiple different servers (Netherlands, Greenland, Switzerland) and still can't get it to work. I get this warning everytime. which i assume having STRICT_PORT_FORWARD set to yes is causing it not to connect?

"[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check"

I've went through this forum looking for recent endpoint issues and saw that i could downgrade to test release. fixed my problem. i can now connect to the endpoint api using the same opvpn file.

Gday Binhex, no issue. Deluge-VPN working very well and been stable for a long time now.

Just notices some warnings on repeat in my logs for deluge-vpn.

/usr/lib/python3.13/site-packages/deluge/pluginmanagerbase.py:16: 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

Just wanted to flag it with you.

Edited September 6, 2025Sep 6 by markh