is anyone encountering issues connecting to wg after a server restart?

When i have to reboot my unraid serer, delugevpn does not work and throws this error in logs:

[debug] Having issues resolving name 'sg.privacy.network', sleeping before retry...

only named server is 1.1.1.1

even with 1.0.0.1 doesnt work. it tends to work when i restart the container but only after a while (like an hour or so).

Hello, after emby full all my cache drive with logs (160GB) my binhex-delugevpn and sabnzbdvpn spot working. Now when I clean cache drive and restart unraid still cannot launch them.
```
docker restart binhex-delugevpn

Error response from daemon: Cannot restart container binhex-delugevpn: driver failed programming external connectivity on endpoint binhex-delugevpn (56b6867d2a18f49d579d8a956fab672d8172c133f51ac6a9625cd60da5a9793b): failed to bind port 0.0.0.0:58946/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:58946: bind: address already in use
```
Do I need to change port? That port is used only for delugevpn for Host Port 3 and Host Port 4.

Regards.

On 9/7/2025 at 2:46 AM, MarianKoniuszko said:

Hello, after emby full all my cache drive with logs (160GB) my binhex-delugevpn and sabnzbdvpn spot working. Now when I clean cache drive and restart unraid still cannot launch them.
```
docker restart binhex-delugevpn

Error response from daemon: Cannot restart container binhex-delugevpn: driver failed programming external connectivity on endpoint binhex-delugevpn (56b6867d2a18f49d579d8a956fab672d8172c133f51ac6a9625cd60da5a9793b): failed to bind port 0.0.0.0:58946/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:58946: bind: address already in use
```
Do I need to change port? That port is used only for delugevpn for Host Port 3 and Host Port 4.

Regards.

i had the same issue - postgres was using that same port even though i couldnt find out how so i just changed the port on deluge and it worked.

you can run in terminal on unraid -

netstat -tulpn | grep 58846

lsof -i :58846

it should tell you what is using that port. mine was - postgresql (ESTABLISHED)

So after years of working just fine it stopped working a week or so ago. Logs copied below. No idea what the issue could be.

2025-09-19 05:43:22.768851 [info] Host is running unRAID

2025-09-19 05:43:22.785044 [info] System information: Linux 7fec531bc0f2 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 GNU/Linux

2025-09-19 05:43:22.801919 [info] Application name: 'delugevpn'

2025-09-19 05:43:22.817708 [info] Base image release tag: '2025072801'

2025-09-19 05:43:22.834349 [info] Output image release tag: '2.2.0-1-04'

2025-09-19 05:43:22.854666 [info] PUID defined as '99'

2025-09-19 05:43:22.877814 [info] PGID defined as '100'

2025-09-19 05:43:22.912750 [info] UMASK defined as '000'

2025-09-19 05:43:22.930289 [info] Permissions already set for '/config'

2025-09-19 05:43:22.955131 [info] Deleting files in /tmp (non recursive)...

2025-09-19 05:43:22.982733 [info] VPN_ENABLED defined as 'yes'

2025-09-19 05:43:23.001274 [info] VPN_CLIENT defined as 'openvpn'

2025-09-19 05:43:23.018941 [info] VPN_PROV defined as 'custom'

2025-09-19 05:43:23.047575 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Windscribe-Amsterdam-RedLight-GCM.ovpn

2025-09-19 05:43:23.088719 [info] VPN remote server(s) defined as 'ams-289.whiskergalaxy.com,'

2025-09-19 05:43:23.104303 [info] VPN remote port(s) defined as '443,'

2025-09-19 05:43:23.120517 [info] VPN remote protcol(s) defined as 'udp,'

2025-09-19 05:43:23.137997 [info] VPN_DEVICE_TYPE defined as 'tun0'

2025-09-19 05:43:23.155870 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)

2025-09-19 05:43:23.173696 [info] NAME_SERVERS defined as '1.1.1.1, 8.8.8.8'

30 minutes ago, greyday said:

So after years of working just fine it stopped working a week or so ago. Logs copied below. No idea what the issue could be.

That log snippet is 99% useless; the 1% usable information here is the vpn remote server: ams-289.whiskergalaxy.com. So I'm just guessing here, as that variable isn't necessarily the server you're trying to connect to. But if this is indeed the server you're connecting to, you need to change the endpoint, as this endpoint is down. So download a new .ovpn file and try again. If this doesn't solve the issue, do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

On 9/19/2025 at 6:34 AM, strike said:

that variable isn't necessarily the server you're trying to connect to. But if this is indeed the server you're connecting to, you need to change the endpoint, as this endpoint is down. So download a new .ovpn file and try again.

This solved it, thank you!

after a long time of things running right i now cannot log into the webui the only error in the log i find that corresponds to this is

2025-09-28 13:59:23,469 DEBG 'start-script' stderr output:

insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

so any ideals? how to repair this issue?

found somthing saying to add this to the /boot/config/go file

"# force iptable mangle module to load (required for *vpn dockers)

/sbin/modprobe iptable_mangle"

tried it and it seemed to solve the issue

Edited September 28, 2025Sep 28 by bull
found potential solve

Hi, in need of a little help please.

I was having an issue connecting the the deluge gui, and other dockers could not see the vpn.

did this:

echo "# force iptable mangle module to load (required for *vpn dockers)" >> /boot/config/go echo "/sbin/modprobe iptable_mangle" >> /boot/config/go

from the VPN FAQ, rebooted and the server didn't come back up.

Connected monitor to the server and its showing Boot Error.

Put the usb in my pc and chkdisk all fine, edited the go file to remove the 2 new lines but still the same.

Not sure if my problem is related to the commands I ran, but never had this happen before

Any ideas? I'm very lost and have little unraid experience :(

Thanks

I have been using this container for awhile but suddnely somtime this week I have been unable to connect to the container like normal.

I get this error

I am not sure how to fix it? i tried reinstalling the container but still same errors and unable to connect

When i updated the contain to :test - I now get this far - but when i go to the webgui to the deluge i get the error "error connection timed out"

Edited October 4, 2025Oct 4 by Appok

Hi, I have been using binhex vpn dockers for a long time.

Recently, it has stopped working. I tried reconfiguring, reinstalling, redownloading the open vpn config and cert files but no luck.

The VPN seems to get established, I can see the login on the VPN site, but there is an error (ERROR: Linux route add command failed) in the logs and the dns lookup for google.com does not work.

Here are parts of my logs. Let me know what other details I can provide to help you help me.

2025-10-11 18:35:15,837 DEBG 'start-script' stdout output:
iptable_mangle         16384  1
ip_tables              28672  5 iptable_filter,iptable_nat,iptable_mangle
x_tables               45056  12 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_nat,ip6_tables,ip_tables,iptable_nat,xt_MASQUERADE,iptable_mangle,xt_mark

2025-10-11 18:35:15,837 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2025-10-11 18:35:15,896 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2025-10-11 18:35:15,898 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 80.254.79.100/32 -i eth0 -j ACCEPT
-A INPUT -s 192.168.2.0/24 -d 192.168.2.0/24 -j ACCEPT
-A INPUT -s 80.254.79.100/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -s 192.168.2.0/24 -d 192.168.2.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -d 80.254.79.100/32 -o eth0 -j ACCEPT
-A OUTPUT -s 192.168.2.0/24 -d 192.168.2.0/24 -j ACCEPT
-A OUTPUT -d 80.254.79.100/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -s 192.168.2.0/24 -d 192.168.2.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2025-10-11 18:35:15,900 DEBG 'start-script' stdout output:
--------------------

2025-10-11 18:35:15,900 DEBG 'start-script' stdout output:
[debug] VPN remote configuration options as follows...
[debug] VPN remote server is defined as 'connect.swissvpn.net'
[debug] VPN remote port is defined as '1194'

2025-10-11 18:35:15,901 DEBG 'start-script' stdout output:
[debug] VPN remote protocol is defined as 'tcp-client'
[debug] VPN remote ip is defined as '80.254.79.100'
[debug] OpenVPN command line:- /usr/bin/openvpn --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'custom' --setenv VPN_CLIENT 'openvpn' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_ENABLED 'yes' --setenv VPN_REMOTE_SERVER 'connect.swissvpn.net' --setenv APPLICATION 'deluge' --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'dhcp-option DNS6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --up /root/openvpnup.sh --up-delay --up-restart --keepalive 10 60 --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/swissvpn.ovpn' --remote 80.254.79.100 1194 tcp-client --remote-random
[info] Starting OpenVPN (non daemonised)...

2025-10-11 18:35:15,912 DEBG 'start-script' stdout output:
2025-10-11 18:35:15 WARNING: file 'credentials.conf' is group or others accessible
2025-10-11 18:35:15 OpenVPN 2.6.14 [git:makepkg/f588592ee6c6323b+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Apr  2 2025
2025-10-11 18:35:15 library versions: OpenSSL 3.5.2 5 Aug 2025, LZO 2.10
2025-10-11 18:35:15 DCO version: N/A

2025-10-11 18:35:15,913 DEBG 'start-script' stdout output:
2025-10-11 18:35:15 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2025-10-11 18:35:15,915 DEBG 'start-script' stdout output:
2025-10-11 18:35:15 TCP/UDP: Preserving recently used remote address: [AF_INET]80.254.79.100:1194
2025-10-11 18:35:15 Attempting to establish TCP connection with [AF_INET]80.254.79.100:1194

2025-10-11 18:35:16,315 DEBG 'start-script' stdout output:
2025-10-11 18:35:16 TCP connection established with [AF_INET]80.254.79.100:1194
2025-10-11 18:35:16 TCPv4_CLIENT link local: (not bound)
2025-10-11 18:35:16 TCPv4_CLIENT link remote: [AF_INET]80.254.79.100:1194

2025-10-11 18:35:23,425 DEBG 'start-script' stdout output:
2025-10-11 18:35:23 [connect.swissvpn.net] Peer Connection Initiated with [AF_INET]80.254.79.100:1194

2025-10-11 18:35:25,176 DEBG 'start-script' stdout output:
2025-10-11 18:35:25 TUN/TAP device tun0 opened
2025-10-11 18:35:25 net_iface_mtu_set: mtu 1500 for tun0

2025-10-11 18:35:25,176 DEBG 'start-script' stdout output:
2025-10-11 18:35:25 net_iface_up: set tun0 up
2025-10-11 18:35:25 net_addr_v4_add: 172.30.0.16/23 dev tun0
2025-10-11 18:35:25 /root/openvpnup.sh tun0 1500 0 172.30.0.16 255.255.254.0 init

2025-10-11 18:35:25,180 DEBG 'start-script' stdout output:
2025-10-11 18:35:25 sitnl_send: rtnl: generic error (-101): Network is unreachable
2025-10-11 18:35:25 ERROR: Linux route add command failed
2025-10-11 18:35:25 sitnl_send: rtnl: generic error (-101): Network is unreachable
2025-10-11 18:35:25 ERROR: Linux route add command failed

2025-10-11 18:35:25,180 DEBG 'start-script' stdout output:
2025-10-11 18:35:25 Initialization Sequence Completed

2025-10-11 18:35:25,184 DEBG 'start-script' stdout output:
[debug] Waiting for valid VPN gateway IP addresses from tunnel...
[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2025-10-11 18:35:26,192 DEBG 'start-script' stdout output:
[debug] Valid VPN adapter IP from tunnel acquired '172.30.0.16'

2025-10-11 18:35:26,192 DEBG 'start-script' stdout output:
[debug] Valid VPN gateway IP address from tunnel acquired ''
[debug] Checking we can resolve name 'www.google.com' to address...

2025-10-11 18:35:26,199 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left

9 hours ago, roland said:

Hi, I have been using binhex vpn dockers for a long time.

Recently, it has stopped working. I tried reconfiguring, reinstalling, redownloading the open vpn config and cert files but no luck.

Have you recently installed tailscale or done any changes in tailscale releated to dns?

3 hours ago, strike said:

Have you recently installed tailscale or done any changes in tailscale releated to dns?

No, I am not using tailscale at all.

Using pihole but haven't changed it in a long time.

13 hours ago, roland said:

No, I am not using tailscale at all.

Using pihole but haven't changed it in a long time.

Which firewall are you using? I recently had a similar issue with pfSense and Snort. Turns out there was a new snort rule blocking. Also, do this so we can get a full log: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

On 10/12/2025 at 8:56 PM, strike said:

Which firewall are you using? I recently had a similar issue with pfSense and Snort. Turns out there was a new snort rule blocking. Also, do this so we can get a full log: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Thank you for trying to help, and sorry for my tardiness.

I use Unify UDR as my firewall, but have not found any blocked entries in the logs for the Unraid host or the DelugeVPN Container.

Please find attached the 2 logs you requested.

supervisord.log CommandExecution.txt

edit: after I had the files attached I let it run longer and there seems to be some randomness involved.

2025-10-15 14:17:29,148 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 6 retries left

2025-10-15 14:17:29,204 DEBG 'start-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2025-10-15 14:17:29,215 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, trying next URL...

2025-10-15 14:17:29,224 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, trying next URL...

2025-10-15 14:17:29,233 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, trying next URL...

2025-10-15 14:17:29,242 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, trying next URL...
[warn] Cannot determine external IP address, performing tests before setting to '127.0.0.1'...
[info] Show name servers defined for container

2025-10-15 14:17:29,243 DEBG 'start-script' stdout output:
nameserver 1.1.1.1
nameserver 1.0.0.1

2025-10-15 14:17:29,243 DEBG 'start-script' stdout output:
[info] Show contents of hosts file

2025-10-15 14:17:29,244 DEBG 'start-script' stdout output:
127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
192.168.2.150	1d90ef322925
80.254.79.100	connect.swissvpn.net

2025-10-15 14:17:29,246 DEBG 'start-script' stdout output:
[info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment

2025-10-15 14:17:30,093 DEBG 'start-script' stdout output:
2025-10-15 14:17:30 [connect.swissvpn.net] Peer Connection Initiated with [AF_INET]80.254.79.100:1194

2025-10-15 14:17:32,150 DEBG 'start-script' stdout output:
2025-10-15 14:17:32 TUN/TAP device tun0 opened
2025-10-15 14:17:32 net_iface_mtu_set: mtu 1500 for tun0

2025-10-15 14:17:32,150 DEBG 'start-script' stdout output:
2025-10-15 14:17:32 net_iface_up: set tun0 up
2025-10-15 14:17:32 net_addr_v4_add: 93.94.241.22/23 dev tun0
2025-10-15 14:17:32 /root/openvpnup.sh tun0 1500 0 93.94.241.22 255.255.254.0 init

2025-10-15 14:17:32,154 DEBG 'start-script' stdout output:
2025-10-15 14:17:32 Initialization Sequence Completed

2025-10-15 14:17:32,157 DEBG 'start-script' stdout output:
[debug] Waiting for valid VPN gateway IP addresses from tunnel...
[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2025-10-15 14:17:33,166 DEBG 'start-script' stdout output:
[debug] Valid VPN adapter IP from tunnel acquired '93.94.241.22'

2025-10-15 14:17:33,166 DEBG 'start-script' stdout output:
[debug] Valid VPN gateway IP address from tunnel acquired ''
[debug] Checking we can resolve name 'www.google.com' to address...

2025-10-15 14:17:33,586 DEBG 'start-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.168.36'

and now it just works.
I will try again soon the restart and capture a full set of command and logs again.

Edited October 15, 2025Oct 15 by roland

I need some help w/ this container. Ed just did a remote session w/ me, the server had a bad cache drive so he switched it to another drive that was already in the server.. Every other container works except deluge. and my time w/ him expired...

please help..

these are the logs:
text error warn system array login

2025-10-17 11:14:33,427 DEBG 'start-script' stdout output:

[info] Successfully generated PIA token for wireguard

2025-10-17 11:14:34,897 DEBG 'watchdog-script' stdout output:

[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.2.112.81 different, marking for reconfigure

2025-10-17 11:14:34,910 DEBG 'watchdog-script' stdout output:

[info] Deluge not running

2025-10-17 11:14:34,913 DEBG 'watchdog-script' stdout output:

[info] Deluge Web UI not running

2025-10-17 11:14:34,913 DEBG 'watchdog-script' stdout output:

[info] Deluge incoming port 6890 and VPN incoming port 31956 different, marking for reconfigure

2025-10-17 11:14:34,915 DEBG 'watchdog-script' stdout output:

[info] Attempting to start Deluge...

[info] Removing deluge pid file (if it exists)...

2025-10-17 11:14:35,067 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2025-10-17 11:14:35,271 DEBG 'watchdog-script' stdout output:

[info] Deluge key 'listen_interface' currently has a value of '10.39.112.60'

[info] Deluge key 'listen_interface' will have a new value '10.2.112.81'

[info] Writing changes to Deluge config file '/config/core.conf'...

2025-10-17 11:14:35,410 DEBG 'watchdog-script' stdout output:

[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'

[info] Deluge key 'outgoing_interface' will have a new value 'tun0'

[info] Writing changes to Deluge config file '/config/core.conf'...

2025-10-17 11:14:35,572 DEBG 'watchdog-script' stdout output:

[info] Deluge key 'default_daemon' currently has a value of 'dc2c8e5176f7d9878e48b94348f93110cf686fc2'

[info] Deluge key 'default_daemon' will have a new value 'dc2c8e5176f7d9878e48b94348f93110cf686fc2'

[info] Writing changes to Deluge config file '/config/web.conf'...

2025-10-17 11:14:35,600 DEBG 'watchdog-script' stdout output:

[info] Deluge process started

[info] Waiting for Deluge process to start listening on port 58846...

2025-10-17 11:14:35,919 DEBG 'watchdog-script' stderr output:

/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

2025-10-17 11:14:36,044 DEBG 'watchdog-script' stdout output:

[info] Deluge process listening on port 58846

2025-10-17 11:14:36,298 DEBG 'watchdog-script' stderr output:

/usr/lib/python3.13/site-packages/deluge/ui/ui_entry.py:20: 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

2025-10-17 11:14:37,357 DEBG 'watchdog-script' stdout output:

Setting "random_port" to: False

Configuration value successfully updated.

2025-10-17 11:14:37,622 DEBG 'watchdog-script' stderr output:

/usr/lib/python3.13/site-packages/deluge/ui/ui_entry.py:20: 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

2025-10-17 11:14:38,661 DEBG 'watchdog-script' stdout output:

Setting "listen_ports" to: (31956, 31956)

Configuration value successfully updated.

2025-10-17 11:14:38,936 DEBG 'watchdog-script' stderr output:

/usr/lib/python3.13/site-packages/deluge/ui/ui_entry.py:20: 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

2025-10-17 11:14:40,015 DEBG 'watchdog-script' stdout output:

[info] No torrents with state 'Error' found

2025-10-17 11:14:40,016 DEBG 'watchdog-script' stdout output:

[info] Starting Deluge Web UI...

2025-10-17 11:14:40,016 DEBG 'watchdog-script' stdout output:

[info] Deluge Web UI started

2025-10-17 11:14:40,339 DEBG 'watchdog-script' stderr output:

/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

2025-10-17 11:24:35,505 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2025-10-17 11:34:35,923 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

2025-10-17 11:44:36,339 DEBG 'start-script' stdout output:

[info] Successfully assigned and bound incoming port

@roland It's not clear to me if you solved the issue or not. I had the exact same issue with "randomness" as you describe. But it was due to snort (IDS/IPS) adding a new rule, which blocked. Your unify also has IDS/IPS, I think, and if it's like pfSense, the logs for that may be different place than the regular firewall log.

56 minutes ago, boianski said:

I need some help w/ this container.

What is the issue? Please also do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

6 minutes ago, boianski said:

The issue is that I am not able to run/open/operate DelugeVPN.

First, remove the deluge run.txt attachment as you forgot to remove your username and password. Then change your password asap. You also uploaded the supervisord.log from krusader and not delugevpn. Please attach the log from delugevpn instead, and REMOVE your user/pw from it before uploading.

What is the IP of the machine you're trying to access deluge from?

Edited October 17, 2025Oct 17 by strike

About 1 1/2 months ago my web UI stopped working on my Deluge as well as back end connections from my downloaders. I'm just now getting around to looking into it. VPN appears to connect fine, can ping the docker IP from my Unraid console, but no other connections are allowed. It's as if the firewall rules on the container aren't fully taking.

My internal IP subnet is 192.168.12.0/24 and I've tried multiple hosts. My main host being 192.168.12.7. Is there anyone that sees anything wrong? I've attached my execution and supervisor logs. Thank you!

supervisor.txt executionCommand.txt

50 minutes ago, xalten said:

About 1 1/2 months ago my web UI stopped working on my Deluge as well as back end connections from my downloaders. I'm just now getting around to looking into it. VPN appears to connect fine, can ping the docker IP from my Unraid console, but no other connections are allowed. It's as if the firewall rules on the container aren't fully taking.

My internal IP subnet is 192.168.12.0/24 and I've tried multiple hosts. My main host being 192.168.12.7. Is there anyone that sees anything wrong? I've attached my execution and supervisor logs. Thank you!

supervisor.txt executionCommand.txt

If you set STRICT_PORT_FORWARD to no can you reach the webui then? It looks like you have an old template, so you need to add the variable yourself to the template. Add a new variable, set the key to: STRICT_PORT_FORWARD and value to no

I am following AlienTech42 Updated! 2025 DelugeVPN: Get It Installed and Setup in Unraid video

The plugins are missing, no check box, just a blank screen. My python version is 3.11.13, so I chose ExtractorPlus-1.7.0-py3.11.egg

to add manually to \appdata\binhex-delugevpn\plugins . The other files in the folder are [object FileList], deluge-mover.py .

None show up in the Preferences -- plugins.

After completing all Preferences and applying them, I restarted DelugeVPN and all entries were reset to their default value.

Where is the Label plugin?

Any help will be appreciated, Thank you.

Command_execution.txt supervisord.log

Edited October 22, 2025Oct 22 by socbutter

44 minutes ago, strike said:

If you set STRICT_PORT_FORWARD to no can you reach the webui then? It looks like you have an old template, so you need to add the variable yourself to the template. Add a new variable, set the key to: STRICT_PORT_FORWARD and value to no

That was it! Thank you so much. Yeah I've had this running since maybe 2016? It just always has worked so I rarely have to tinker with it lol.

6 minutes ago, socbutter said:

I am following AlienTech42 Updated! 2025 DelugeVPN: Get It Installed and Setup in Unraid video

The plugins are missing, no check box, just a blank screen. My python version is 3.11.13, so I chose ExtractorPlus-1.7.0-py3.11.egg

to add manually to \appdata\binhex-delugevpn\plugins . The other files in the folder are [object FileList], deluge-mover.py .

None show up in the Preferences -- plugins.

After completing all Preferences and applying them, I restarted DelugeVPN and all entries were reset to their default value.

Where is the Label plugin?

Any help will be appreciated, Thank you.

Command_execution.txt supervisord.log

Maybe Q4 can help? https://github.com/binhex/documentation/blob/master/docker/faq/delugevpn.md

Just now, xalten said:

That was it! Thank you so much. Yeah I've had this running since maybe 2016? It just always has worked so I rarely have to tinker with it lol.

Great, then we know what the issue is, and it's related to port forwarding. For port forwarding to work, STRICT_PORT_FORWARD should be set yes. But since your webui won't load when set to yes, it means either the endpoint is not supporting port forwarding anymore, or more likely, it could be because you're running an old version of delugevpn, which maybe has an old link for fetching the port forwarding supported endpoints. I noticed in your log a warning that the url was down. It may be down, but I don't think it has been down for 1 1/2 months..

And without port forwarding, your speed will suffer, so you should definitely fix it. Start by updating the container to the latest version. Set STRICT_PORT_FORWARD to yes again and see if you have the same issue. If it works, then it's fixed. If it won't load again, you could try to download a new ovpn file and pem file. The Netherlands is a good choice.

7 minutes ago, strike said:

Great, then we know what the issue is, and it's related to port forwarding. For port forwarding to work, STRICT_PORT_FORWARD should be set yes. But since your webui won't load when set to yes, it means either the endpoint is not supporting port forwarding anymore, or more likely, it could be because you're running an old version of delugevpn, which maybe has an old link for fetching the port forwarding supported endpoints. I noticed in your log a warning that the url was down. It may be down, but I don't think it has been down for 1 1/2 months..

And without port forwarding, your speed will suffer, so you should definitely fix it. Start by updating the container to the latest version. Set STRICT_PORT_FORWARD to yes again and see if you have the same issue. If it works, then it's fixed. If it won't load again, you could try to download a new ovpn file and pem file. The Netherlands is a good choice.

As far as the container, it automatically updates daily so I think that should take care of the request to make sure it's the latest version. From the web UI I see it's 2.2.0 which looks like it's the latest client

As far as the URL, that's an interesting story. The URL works from my Unraid console as can be seen here:

But it looks like when I'm connected to the VPN it doesn't work:

I had tried a few different servers as trouble shooting and chose servers that were listed within that list and had the port_forward: True setting (I had remembered that being a thing a long time ago). I'll try scratching my vpn file and going with a new one and will swap out to your suggested server as well and see if I can get it to work with port forwarding.