22 hours ago, binhex said:

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

Files attached. Let me know if that is correct.

Binhex-delugevpn-CommandEx.txt supervisord.log

Hey guys,

I wanted to create torrents so i tried setting up a thin client. I created a new entry in appdata/delugevpn/auth, which looks like delugethin:[pw]:10 and added a host in my thin client (my local ip as hostname, default port and the username and password i set in auth), but can't connect to the daemon running on my server. Remote connections are allowed.

What am i doing wrong?

Mine is doing that too, disconnecting and reconnecting every 10 minutes or so.

 

2025-02-27 06:23:46,795 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 06:33:46,880 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 06:43:46,976 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 06:53:47,073 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 07:03:47,167 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 07:13:47,256 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 07:23:47,349 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

On 1/25/2025 at 1:02 PM, downloadedskill said:

Files attached. Let me know if that is correct.

Binhex-delugevpn-CommandEx.txt 1.57 kB · 2 downloads supervisord.log 9.21 kB · 1 download

 

2 hours ago, SilentStray said:

Mine is doing that too, disconnecting and reconnecting every 10 minutes or so.

 

2025-02-27 06:23:46,795 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 06:33:46,880 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 06:43:46,976 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 06:53:47,073 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 07:03:47,167 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 07:13:47,256 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

2025-02-27 07:23:47,349 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '28952'

 

where in the above does it say its disconnecting?, that log is simply confirming what the current assigned incoming port is.

On 1/25/2025 at 6:02 PM, downloadedskill said:

Files attached. Let me know if that is correct.

Binhex-delugevpn-CommandEx.txt 1.57 kB · 2 downloads supervisord.log 9.21 kB · 3 downloads

attached log is for krusader, try again.

Hi all,

I have a problem with delugevpn docker in unraid, where it runs fine for a few days, then it'll 100% a CPU core or 2 constantly until it's restarted.
Opening the logs, there doesn't look like anything out of the ordinary (or different to the days where it runs just fine). Has anyone else come across this?

 

Hi All,

Trying to reset the webui password, but following the instructions here doesn't work. I've tried deleting the sha1 line and also deleting the web.conf file after stopping the container. Is there something specific to unraid? Do I also need to delete the web.conf.bak?

SO I understand that while I have tailscale vpn active on my laptop i am not able to access the delugeVPN docker container. WebUI. 

 

I am reading the Q36 from the Binhex - 

Q36. When enabling Tailscale I can no longer access the Web UI of any VPN enabled contains, why is this and how can I fix it?.

A36. Tailscale interferes with DNS and networking causing issues with VPN enabled images, here are the known workarounds:-

MagicDNS is enabled - Fix is to disable MagicDNS in Tailscale

TAILSCALE_USERSPACE_NETWORKING is set to false - Fix is to set this to true

Note If you are attempting to access the VPN enabled applications Web UI remotely over Tailscale then you will also need to ensure the Tailscale IP network is also added to LAN_NETWORK - See Q30. above for more details.

 

Although I have been doing unraid for a bit, I still consider myself as very new.    I am wonder how would I go about updating the TAILSCALE- Userspace-networking ? 

 

 

I tried to add the docker tailscale to deluge but found it did not work. so reverted this. Any ideas? much appreciated. 

Edited March 4, 20251 yr by Aceriz

Hi, how do i set the wireguard region? I tried a variable VPN_REMOTE_SERVER to jakarta.privacy.network in unraid docker config screen, but it seems to be ignored. So i tried editing the Endpoint in /mnt/user/appdata/binhex-delugevpn/wireguard/wg0.conf but when i do that the docker fails to boot, so i delete the file then of course it is recreated with nl-amsterdam.privacy.network as the endpoint.... So i tried deleting all the other lines in the file but the Endpoint but that also fails.

Surely it should be easy, surely i should only have to use the variable...? What am i missing here?

2 hours ago, dgwharrison said:

I tried a variable VPN_REMOTE_SERVER

Not sure where you got that env var from but it's not valid.

 

2 hours ago, dgwharrison said:

So i tried editing the Endpoint in /mnt/user/appdata/binhex-delugevpn/wireguard/wg0.conf but when i do that the docker fails to boot

This is the correct way to change the endpoint you want to connect to, my guess here (and it is a guess without any logs) is that the endpoint you want to connect to is not port forward enabled and you have 'STRICT_PORT_FORWARD' set to 'yes'

 

Please see Q10 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thanks @binhex, really appreciate your help, and the dockers. I was finding that it was stalling right at startup of the container, like a dozen lines after your logo, long before the port forwarding appears in the logs. I did check that page and see question 10, but it seemed to cover openvpn only and my issue is with wireguard.

I'm have a problem with my DNS in this docker.  It seems to be using Google's DNS instead of Cloudflare's.

If I run cat /etc/resolv.conf on my host I get this:

# Generated by rc.inet1
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.254

 

but if I run it from the console in the docker I get this:

nameserver 84.200.69.80
nameserver 37.235.1.174
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 1.1.1.1
nameserver 37.235.1.177
nameserver 84.200.70.40
nameserver 1.0.0.1

 

11 hours ago, dgwharrison said:

Thanks @binhex, really appreciate your help, and the dockers. I was finding that it was stalling right at startup of the container, like a dozen lines after your logo, long before the port forwarding appears in the logs. I did check that page and see question 10, but it seemed to cover openvpn only and my issue is with wireguard.

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

1 hour ago, InReasonNotFish said:

I'm have a problem with my DNS in this docker.  It seems to be using Google's DNS instead of Cloudflare's.

If I run cat /etc/resolv.conf on my host I get this:

# Generated by rc.inet1
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.254

 

but if I run it from the console in the docker I get this:

nameserver 84.200.69.80
nameserver 37.235.1.174
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 1.1.1.1
nameserver 37.235.1.177
nameserver 84.200.70.40
nameserver 1.0.0.1

 

whats the value of NAME_SERVERS?, i suspect it matches what you are seeing in the console of the container.

5 hours ago, binhex said:

whats the value of NAME_SERVERS?, i suspect it matches what you are seeing in the console of the container.

It's all of the servers I've shown.  I've edited the setting to prioritize the cloudflare DNS.  That seems to have resolved my issue... I think

Edited March 9, 20251 yr by InReasonNotFish
clarity

On 2/28/2025 at 11:43 PM, 4554551n said:

Hi all,

I have a problem with delugevpn docker in unraid, where it runs fine for a few days, then it'll 100% a CPU core or 2 constantly until it's restarted.
Opening the logs, there doesn't look like anything out of the ordinary (or different to the days where it runs just fine). Has anyone else come across this?

 

This is still giving me greif, has anyone else seen this?

Today my VPN Deluge page will not load.  Any ideas to try?

 

2025-03-14 07:01:25,610 DEBG 'start-script' stdout output:
2025-03-14 07:01:25 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2025-03-14 07:01:25,611 DEBG 'start-script' stdout output:
2025-03-14 07:01:25 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.214.114:80

2025-03-14 07:01:25,611 DEBG 'start-script' stdout output:
2025-03-14 07:01:25 UDPv4 link local: (not bound)
2025-03-14 07:01:25 UDPv4 link remote: [AF_INET]37.120.214.114:80

2025-03-14 07:02:26,084 DEBG 'start-script' stdout output:
2025-03-14 07:02:26 [UNDEF] Inactivity timeout (--ping-restart), restarting

2025-03-14 07:02:26,084 DEBG 'start-script' stdout output:
2025-03-14 07:02:26 SIGHUP[soft,ping-restart] received, process restarting

2025-03-14 07:02:26,085 DEBG 'start-script' stdout output:
2025-03-14 07:02:26 DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 

2025-03-14 07:02:26,085 DEBG 'start-script' stdout output:
2025-03-14 07:02:26 WARNING: file 'credentials.conf' is group or others accessible

2025-03-14 07:02:26,085 DEBG 'start-script' stdout output:
2025-03-14 07:02:26 OpenVPN 2.6.12 [git:makepkg/038a94bae57a446c+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Dec 16 2024
2025-03-14 07:02:26 library versions: OpenSSL 3.4.0 22 Oct 2024, LZO 2.10
2025-03-14 07:02:26 DCO version: N/A

2025-03-14 07:02:27,085 DEBG 'start-script' stdout output:
2025-03-14 07:02:27 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2025-03-14 07:02:27,086 DEBG 'start-script' stdout output:
2025-03-14 07:02:27 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.214.114:80
2025-03-14 07:02:27 UDPv4 link local: (not bound)
2025-03-14 07:02:27 UDPv4 link remote: [AF_INET]37.120.214.114:80

 

 

3 hours ago, rmilyard said:

Today my VPN Deluge page will not load.  Any ideas to try?

Do this please: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

My DelugeVPN docker does not start anymore, since a while, while is was working before.

 

2025-03-21 12:52:06,064 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

 

2025-03-21 12:53:36,380 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

The wg0.conf file is renewed with the latest VPN info from my provider. Docker is running in privileged mode.

 

Can you guide me into the right direction?

10 hours ago, TallMan206 said:

Can you guide me into the right direction?

https://github.com/binhex/documentation/blob/master/docker/faq/help.md#gather-supervisor-log

Hello,

 

I'm having issue using Deluge with my VPN.  I am able to connect when using OpenVPN GUI client, but it's not working with Deluge.

 

Someone can help?

 

Thank you.

Command execution.txt supervisord.log

35 minutes ago, frcouture said:

Hello,

 

I'm having issue using Deluge with my VPN.  I am able to connect when using OpenVPN GUI client, but it's not working with Deluge.

 

Someone can help?

 

Thank you.

Command execution.txt 1.41 kB · 0 downloads supervisord.log 1.96 kB · 0 downloads

Which unraid version are you running? Have you changed permission on you appdata folder recently, maybe ran the new (non safe docker) permission tool lately? There's some permission issues with iptables causing deluge not to abe to start. If you've not changed permissions on your appdata folder recently I suggest remove the deluge container, delete the appdata for it and install it again. If you're on an old unraid version maybe try to update. 

13 hours ago, strike said:

Which unraid version are you running? Have you changed permission on you appdata folder recently, maybe ran the new (non safe docker) permission tool lately? There's some permission issues with iptables causing deluge not to abe to start. If you've not changed permissions on your appdata folder recently I suggest remove the deluge container, delete the appdata for it and install it again. If you're on an old unraid version maybe try to update. 

Hi! I''m running Unraid 7.0.0 and removed the binhex appdata folder as well as the deluge container. I recently rolled back to 7.0.0 after an unsuccessful update to 7.0.1. Plex and Krusader still work, but deluge and my arrs no longer work.

Reinstalling Deluge doesn't produce a wireguard wgo.conf file anymore. Does anyone have any tips I can try?

 

I've been following AlienTech's guides, and they worked for my setup a couple of months ago

 

 

5 hours ago, mixx said:

Reinstalling Deluge doesn't produce a wireguard wgo.conf file anymore. Does anyone have any tips I can try?

Have you tried the steps listed in the faq Q21?

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

Hello, @binhex

 

I wanted to know how i can fix this issue - chown: cannot access '/home/nobody': No such file or directory

 

now i have everything being mounted in the container in /home for all my apps and i want to do it in this on as well and not in the /downloads 

 

Notes: 

 

Im using the newest version of Unraid and the everything else if that helps