19 hours ago, Jannik_ said:

Hi Binhex,

 

can you please tell me if those settings are correct for port forwarding? Currently deluge runs fine without port forwarding (just not that fast).

But I would like to ask prior before I enable it.

 

1. Deluge internal settings:

 

 

2. VPN open port settings (not PIA):

that looks good to me!, it really is fairly simple, define incoming port at vpn provider end, configure deluge to use defined port, job done :-), obviously its more tricky for dynamic port vpn providers such as PIA and ProtonVPN, which is why i do it for ya :-).

Hello All,

 

I'm stuck with the binhex-delugevpn docker.  Somehow I changed the password to the webgui and I cannot login.  I've tried:

-stopping the docker

-removing the docker

-running app data cleanup (and removing the container)

And then re-installing.  Same issue.   I'm unsure where the password is kept and exactly how to re-install and reset the webui password.

 

Also tried removing the line in ~/.config/deluge/web.conf starting with the "pwd_sha1". 

I did find a python script that is supposed to allow changing the password but don't quite know how to run it.  (can't find python or python3)

 

Any help would be appreciated.

 

Thanks,

Clayton

On 12/21/2023 at 4:14 AM, binhex said:

that looks good to me!, it really is fairly simple, define incoming port at vpn provider end, configure deluge to use defined port, job done :-), obviously its more tricky for dynamic port vpn providers such as PIA and ProtonVPN, which is why i do it for ya :-).

I got Deluge running and ProtonVPN WG config setup. WG tunnel comes up, and DNS resolution works. I also followed the FAQ to get the right Proton VPN port forwarding file. However, zero torrents are downloading. It is showing seeds and peers are online, but 0 bytes are downloaded. Not sure where to go from here to debug? The Docker container is running on a plain vanilla Ubuntu VM. 

 

version: '3.7'
services:
  delugevpn:
    image: binhex/arch-delugevpn
    container_name: delugevpn
    privileged: true
    ports:
      - 8112:8112
      - 8118:8118
      - 58846:58846
      - 58946:58946
    volumes:
      - /apps/docker/deluge/data:/data
      - /apps/docker/deluge/config:/config
      - /etc/localtime:/etc/localtime:ro
    environment:
      - VPN_ENABLED=yes
      - VPN_PROV=protonvpn
      - VPN_USER=user+pmp
      - VPN_CLIENT=wireguard
      - VPN_DEVICE_TYPE=wg0
      - STRICT_PORT_FORWARD=yes
      - ENABLE_PRIVOXY=yes
      - LAN_NETWORK=10.13.2.1/24,10.189.177.0/24
      - NAME_SERVERS=1.1.1.1
      - DELUGE_DAEMON_LOG_LEVEL=debug
      - DELUGE_WEB_LOG_LEVEL=debug
      - DELUGE_ENABLE_WEBUI_PASSWORD=yes
      - VPN_INPUT_PORTS=50004
      - VPN_OUTPUT_PORTS=56780
      - DEBUG=true
      - UMASK=000
      - PUID=1000
      - PGID=1000
 

Edited December 22, 20232 yr by Globe89

9 minutes ago, Globe89 said:

However, zero torrents are downloading. It is showing seeds and peers are online, but 0 bytes are downloaded. Not sure where to go from here to debug?

What path do you have in the downloads section in the deluge settings?

1 minute ago, strike said:

What path do you have in the downloads section in the deluge settings?

download to: /data/incomplete

 

I haven't changed any default Deluge settings. 

3 minutes ago, Globe89 said:

download to: /data/incomplete

 

I haven't changed any default Deluge settings. 

Looks ok. Due you see any permissions error in the log? If you bash into the container and cd to that dir are you able to write to it?

4 minutes ago, strike said:

Looks ok. Due you see any permissions error in the log? If you bash into the container and cd to that dir are you able to write to it?

yes I went into the container console into /data. There were no files/directories. But I created 'incomplete' successfully. I also touched a file, and that worked. I then went to my Ubuntu host and that directory and touched file were on the host. 

Then I don't really know what your issue is. The symptom you're seeing is usually due to misconfigured volume mapping or a permissions error. But looks like that's not it in your case.

I made a big mistake and accidentally deleted binhex-delugevpn when I was trying to delete another container instead.  I reinstalled binhex-delugevpn with protonvpn as the client with wireguard and I confirmed that I could get into the container and because appdat wasn't deleted all my settings were there.  

 

However, I'm trying to route containers through delugevpn per the Spaceinvader One video, which was working great before this  accidental deletion.  When I used to set the extra parameter to --net=container:binhex-delugevpn and make network 'none',I'd see something like :5800/TCP <--> :5800 next to the container name, and when I would dropdown on the container, and the webui selection would disappear.  I tried to fix old containers (stuff like radarr, lidarr etc.) and even tried a container from scratch, but I'm still seeing the image below where the column under port mappings is blank and I can still see webui (which obviously doesn't work.)  I've tried to go all the way through to adding the port to delugevpn but it still doesn't work.

 

Any ideas why I can't just restore this?  Do I have to delete something else in appdata?

 

Thanks.

 

I use both Wireguard (via my Firewalla) and Tailscale for remote access to my home network. I added my Wireguard IP range to the LAN_NETWORK, and it works great. However, for the life of me I can't get my Tailscale range to work. For example, in the tailscale console all my IPs are 100.20.30.xxx. So for the LAN_NETWORK I added 100.20.30.0/24 but that doesn't work. My home exit node is on primary LAN address space, which is already listed in LAN_NETWORK.

Edited December 23, 20232 yr by Globe89

Hm, are your private trackers or port checker sites https://www.yougetsignal.com/tools/open-ports/ report that you are connectable?

 

Dont know why but I'm not here yet. Are there any follow-up steps required after telling the VPN which port to open and putting that port in deluge?

 

 

 

 

edit:

I got PIA for 1 month to test if port forwarding works. It does.

 

Issue with fastestvpn:

In the supervisord.log file I can see the following error when I connected to the port forwarding enabled fastestvpn server:

 

2023-12-26 00:36:09,987 DEBG 'start-script' stdout output:
2023-12-26 00:36:09 Options error: Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:4: block-outside-dns (2.6.7)
2023-12-26 00:36:09 NOTE: setsockopt TCP_NODELAY=1 failed

Edited December 26, 20232 yr by Jannik_

Hi, I am trying to set up delugevpn using openvpn and purvpn. Using the purvpn client I can setuo and connect a vpn with my client credentials and all appears to work fine

 

to configure the the docker delugevpn on  UNRAID  I edited the docker container configuration and stipulated the the vpn would be openvpn and rebuilt, that's the only change I made from switching from torguard/wireguard configuration to purvpn/openvpn. I edited the credentials.conf file and subtituted the two lines for my userid and password, but no matter what format of the file I use i keep on getting 

 

2024-01-02 20:13:09,229 DEBG 'start-script' stdout output:
2024-01-02 20:13:09 AUTH: Received control message: AUTH_FAILED
2024-01-02 20:13:09 SIGTERM received, sending exit notification to peer

 

and in addition to the credentials file being reset to 

 

vpn username

vpn password

 

looping through the log file,

 

During the setup of openvpn, i set the permissions on the tun0.opvn and the credentials.conf 400  but it doesn't matter what permissions  i choose they are always reset to 775 and I always get the following message in the log

 

2024-01-02 20:24:37,309 DEBG 'start-script' stdout output:
2024-01-02 20:24:37 WARNING: file 'credentials.conf' is group or others accessible
2024-01-02 20:24:37 OpenVPN 2.6.7 [git:makepkg/53c9033317b3b8fd+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Nov  9 2023
2024-01-02 20:24:37 library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2024-01-02 20:24:37 DCO version: N/A

 

Any insight on either of these problems would be much appreciated, especially the authentication one.

 

Thank you

5 hours ago, infinate-unraid said:

I edited the credentials.conf file and subtituted the two lines for my userid and password

dont do that, instead specify vpn username and password using the env vars VPN_USER and VPN_PASS

 

just to confirm AUTH_FAILED is exactly what you would suspect - a failure to authenticate with the vpn prvider, do the above and it should work.

19 hours ago, binhex said:

dont do that, instead specify vpn username and password using the env vars VPN_USER and VPN_PASS

 

just to confirm AUTH_FAILED is exactly what you would suspect - a failure to authenticate with the vpn prvider, do the above and it should work.

 

I'm sorry but where do i set these environment variables if they don't go in the credentials.conf file. How do I set them in the docker or are that set in the UNRAID environment but how.

 

is there some documentation that tells you how to do this?

30 minutes ago, infinate-unraid said:

I'm sorry but where do i set these environment variables if they don't go in the credentials.conf file.

They are in the docker container template.  Edit the container and add the appropriate information to the variables.

 

So i've been using this docker for years along with Sonarr. Recently, I noticed downloads from Deluge were not being picked up by Sonarr in my tv categories folder. I think I've narrowed down the issue to permissions on the actual files inside the download folders. I'm using a UMASK setting of 100 in the config so I'm expecting to see a rwxrwxrwx file permission but instead see rw-rw-rw-. When I checked NZBget or SABnzbd downloaded files with the same UMASK setting they show rwxrwxrwx and are imported correctly. Is this the correct diagnosis and if so, how do I fix it? Thanks in advance.

46 minutes ago, betaman said:

I'm using a UMASK setting of 100 in the config so I'm expecting to see a rwxrwxrwx file permission

umask 001 = 776 which equates to rwxrwxrw- actually but in any case umask does not set the executable bit, so umask 000 = rw-rw-rw- you have to manually set the executable bit.

 

can i ask why you want to set your videos to executable?

21 minutes ago, binhex said:

umask 001 = 776 which equates to rwxrwxrw- actually but in any case umask does not set the executable bit, so umask 000 = rw-rw-rw- you have to manually set the executable bit.

 

can i ask why you want to set your videos to executable?

I don’t know that I want too! I’m just trying to figure out why all of the sudden Deluge downloads aren’t being picked up by Sonarr? When I check Sonarr the downloads are gone from the queue and I (personally) can’t see anything in the logs indicating what happened? The only difference I could find between Deluge and the other download clients is the file permissions.

Edited January 4, 20242 yr by betaman

8 minutes ago, betaman said:

I don’t know that I want too! I’m just trying to figure out why all of the sudden Deluge downloads aren’t being picked up by Sonarr? When I check Sonarr the downloads are gone from the queue and I (personally) can’t see anything in the logs indicating what happened? The only difference I could find between Deluge and the other download clients is the file permissions.

you may have a mismatched downloads folder, see Q4 for my attempt at explaining this:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md 

2 hours ago, binhex said:

you may have a mismatched downloads folder, see Q4 for my attempt at explaining this:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md 

Ok, so first thing is I'm using all of your dockers (*arr, deluge, nzbget, sabnzbd etc). All of the containers are setup with /data and they all point to my downloads folder (/mnt/user/appdata/downloads) in the respective container setup.  I've been using categories to keep movies and tv separate so the categories are setup as /mnt/user/appdata/downloads/movies and /mnt/user/appdata/downloads/tv).  I was remote mapping the category directories in the *arr containers within each program under the download client setting (/mnt/user/appdata/downloads/tv to /data/tv) but I think this step was unnecessary. Having said that, Radarr currently has this setup and is working correctly with imports while Sonarr is not and I "think" I have them setup the same (i.e. remote mapping in both). I removed remote mapping in Sonarr but still same behavior. Haven't tried Radarr yet.

Edited January 4, 20242 yr by betaman

Starting a new post since I haven't seen a response to my initial post from December 1st. Still dead in the water with torrenting. Looking at moving to another torrent client or going with a torrenting VPN service to offload this from my environment altogether.

 

After years of use, I can't pull up the web UI for Deluge ("This site can’t be reached" initiating this from within the UNRAID GUI under the Docker page for this docker; IP and port are the same as before when it worked) and it appears to not be seeding (have HNR with my trackers). I've attempted to restore it as before, but still can't get this docker to work. Here's the log below. Any suggestions? Hoping this is a quick fix as moving to another torrent client or offloading this to a VPN torrent service is looking like a PITA to me. I'd rather stay the course if possible. 🤞

 

*****************************************************************************

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

2024-01-01 11:33:40,056 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2024-01-02 04:00:03,291 WARN received SIGTERM indicating exit request
2024-01-02 04:00:03,292 DEBG killing watchdog-script (pid 73) with signal SIGTERM
2024-01-02 04:00:03,293 INFO waiting for watchdog-script to die
2024-01-02 04:00:03,295 DEBG 'watchdog-script' stderr output:
Terminated

2024-01-02 04:00:03,296 DEBG 'watchdog-script' stdout output:
[info] Waiting for child processes to exit...
[info] All child processes exited, exiting while loop...
[info] All child processes exited, exiting 'watchdog.sh' script...

2024-01-02 04:00:03,297 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23181582822672 for <Subprocess at 23181582976912 with name watchdog-script in state STOPPING> (stdout)>
2024-01-02 04:00:03,297 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23181580600976 for <Subprocess at 23181582976912 with name watchdog-script in state STOPPING> (stderr)>
2024-01-02 04:00:03,298 INFO stopped: watchdog-script (exit status 0)
2024-01-02 04:00:03,298 DEBG received SIGCHLD indicating a child quit
Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
  https://hub.docker.com/u/binhex/

2024-01-02 04:00:10.758877 [info] Host is running unRAID
2024-01-02 04:00:10.778928 [info] System information Linux 5bce46582aa0 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 GNU/Linux
2024-01-02 04:00:10.806147 [info] PUID defined as '0'
2024-01-02 04:00:10.852687 [info] PGID defined as '0'
2024-01-02 04:00:10.952580 [info] UMASK defined as '000'
2024-01-02 04:00:10.977080 [info] Permissions already set for '/config'
2024-01-02 04:00:11.004748 [info] Deleting files in /tmp (non recursive)...
2024-01-02 04:00:11.038421 [info] VPN_ENABLED defined as 'no'
2024-01-02 04:00:11.060972 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2024-01-02 04:00:11.084717 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2024-01-02 04:00:11.107469 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2024-01-02 04:00:11.131829 [info] DELUGE_ENABLE_WEBUI_PASSWORD not defined,(via -e DELUGE_ENABLE_WEBUI_PASSWORD), defaulting to 'yes'
2024-01-02 04:00:11.155585 [info] Starting Supervisor...
2024-01-02 04:00:11,545 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2024-01-02 04:00:11,545 INFO Set uid to user 0 succeeded
2024-01-02 04:00:11,549 INFO supervisord started with pid 7
2024-01-02 04:00:12,550 INFO spawned: 'start-script' with pid 71
2024-01-02 04:00:12,551 INFO spawned: 'watchdog-script' with pid 72
2024-01-02 04:00:12,552 INFO reaped unknown pid 8 (exit status 0)
2024-01-02 04:00:12,557 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2024-01-02 04:00:12,557 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-01-02 04:00:12,557 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-01-02 04:00:12,557 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22421319608976 for <Subprocess at 22421319731280 with name start-script in state RUNNING> (stdout)>
2024-01-02 04:00:12,557 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22421330322384 for <Subprocess at 22421319731280 with name start-script in state RUNNING> (stderr)>
2024-01-02 04:00:12,557 INFO exited: start-script (exit status 0; expected)
2024-01-02 04:00:12,558 DEBG received SIGCHLD indicating a child quit
2024-01-02 04:00:12,593 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2024-01-02 04:00:12,596 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2024-01-02 04:00:12,598 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2024-01-02 04:00:12,970 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has an undefined value
[info] Deluge key 'listen_interface' will have a new value ''
[info] Writing changes to Deluge config file '/config/core.conf'...

2024-01-02 04:00:13,209 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has an undefined value
[info] Deluge key 'outgoing_interface' will have a new value ''
[info] Writing changes to Deluge config file '/config/core.conf'...

2024-01-02 04:00:13,444 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'ed245fa046284bd999b98097404968b9'
[info] Deluge key 'default_daemon' will have a new value 'ed245fa046284bd999b98097404968b9'
[info] Writing changes to Deluge config file '/config/web.conf'...

2024-01-02 04:00:13,489 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2024-01-02 04:00:14,141 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

Edited January 5, 20242 yr by realdiel

Installed and configured this with ProtonVPN using wireguard and port forwarding. everything worked according to the logs and deluge could download with decent speeds.  Started having massive problems on my network and finally had to call ISP as the service kept going down.  They pinpointed it all to my unraid server which is only running this docker image.  Shut it down and all went back to normal.  I don't dare start it back up as it took down my bitcoin node, LN and some other essential services.  What can I share to try and ts? 

Edited January 5, 20242 yr by CALMSURF
typos

3 hours ago, realdiel said:

Starting a new post since I haven't seen a response to my initial post from December 1st. Still dead in the water with torrenting. Looking at moving to another torrent client or going with a torrenting VPN service to offload this from my environment altogether.

 

After years of use, I can't pull up the web UI for Deluge ("This site can’t be reached" initiating this from within the UNRAID GUI under the Docker page for this docker; IP and port are the same as before when it worked) and it appears to not be seeding (have HNR with my trackers). I've attempted to restore it as before, but still can't get this docker to work. Here's the log below. Any suggestions? Hoping this is a quick fix as moving to another torrent client or offloading this to a VPN torrent service is looking like a PITA to me. I'd rather stay the course if possible. 🤞

I switched to qbittorrent (vpn, binhex image) and torrents are working again for me. Can't explain it...

Edited January 5, 20242 yr by betaman

53 minutes ago, betaman said:

I switched to qbittorrent (vpn, binhex image) and torrents are working again for me. Can't explain it...

Doh! Ok. I may do the switch then if I can't figure out what's going on here.

Hi All!

 

I'm struggling with slow speeds with DelugeVPN. I watched spaceinvaderone's tutorial, set it up for wireguard using PureVPN. Have specified the port that I forwarded within the PureVPN configuration page and am getting super slow down speeds. I saw the note in the FAQ related to "Strict_port_forward" and PIA users potential for slow speeds, but since I'm using PureVPN it seems that won't apply.

 

If I use deluge as a thick client on my Linux desktop I'll get 6MB down with the same VPN service/server, so my Internet connection and the server I'm using shouldn't be the bottleneck. Any help is appreciated!