[Support] binhex - DelugeVPN


8753 posts in this topic Last Reply

Recommended Posts

  • Replies 8.8k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A n

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

Posted Images

Does anyone know why in my case this docker only works if using root privileges e.g if both PUID & PGID are set to 0? If I set my user (1026 and 100) then docker keeps restarting in an endless loop.

 

Docker runs on Synology NAS. This is excerpt from the log file when I set PUID to 1026:

 

2019-10-14 10:45:18,901 WARN received SIGTERM indicating exit request
2019-10-14 10:45:18,901 DEBG killing watchdog-script (pid 150) with signal SIGTERM
2019-10-14 10:45:18,901 INFO waiting for start-script, watchdog-script to die
2019-10-14 10:45:19,904 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 139908803456720 for <Subprocess at 139908803414864 with name watchdog-script in state STOPPING> (stdout)>
2019-10-14 10:45:19,904 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 139908802859344 for <Subprocess at 139908803414864 with name watchdog-script in state STOPPING> (stderr)>
2019-10-14 10:45:19,904 INFO stopped: watchdog-script (terminated by SIGTERM)
2019-10-14 10:45:19,905 DEBG received SIGCHLD indicating a child quit
2019-10-14 10:45:19,906 DEBG killing start-script (pid 149) with signal SIGTERM
2019-10-14 10:45:19,907 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139908803414992 for <Subprocess at 139908803313488 with name start-script in state STOPPING> (stdout)>
2019-10-14 10:45:19,907 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139908803456784 for <Subprocess at 139908803313488 with name start-script in state STOPPING> (stderr)>
2019-10-14 10:45:19,907 INFO stopped: start-script (terminated by SIGTERM)
2019-10-14 10:45:19,907 DEBG received SIGCHLD indicating a child quit
Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

After the first crash, the last bit with logo is repeating every time docker restarts e.g:

 

Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/
2019-10-14 10:46:46.583010 [info] System information Linux DelugeVPN 4.4.59+ #24922 SMP PREEMPT Mon Aug 19 12:13:37 CST 2019 x86_64 GNU/Linux
2019-10-14 10:46:46.648330 [info] PUID defined as '1026'

 

Cheers.

Link to post

I know nothing when it comes to CSS and styling for webpages and I'm trying to figure out how to apply a dark theme for the Web UI. qBittorrent has a couple pre-made ones on Userstyles that work with the Stylus add on for Chrome but I can't find any for Deluge. Does anyone have any experience making dark themes or have found and used one for Deluge?

 

One of the developers on their forum linked this in an old thread (https://forum.deluge-torrent.org/viewtopic.php?t=55047) and said to apply them and change the web.conf file but I have no idea what to do with the files inside or if it's even possible here:

https://git.deluge-torrent.org/deluge/tree/deluge/ui/web/themes

 

Any help would be appreciated.

Link to post
On 8/29/2019 at 9:04 PM, Lipora said:

Hello BixHex,

 

I just updated to the latest version a few days ago and I cannot get it running on my Synology.  I've been using the previous versions for some time but this one has started giving me grief.  When I start the docker container I get the error:

 

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

 

It's as though it's trying to run the inital run script to see that all the previous config files are in place etc. but not being able to do so as it cannot locate that /root/init.shaving the same problemh location on the synology.  I know Synology Docker is a bit different than others with its file locations but most containers I've been able to get working.  This one I'm struggling with.  Any advise would be helpful.

 

Added: Found a reference to the fact that /bin/bash might not be available in Synology Docker?!

It’s because bash is not part of the image. Launching shell with /bin/sh would work. However, I don’t know if it’s possible to configure that on Synology...

 

Any help would be great.

I am  the having the same problem re: /bin/bash: /root/init.sh: No such file or directory

Link to post
9 hours ago, karka said:

Does anyone know why in my case this docker only works if using root privileges e.g if both PUID & PGID are set to 0? If I set my user (1026 and 100) then docker keeps restarting in an endless loop.

 

Docker runs on Synology NAS. This is excerpt from the log file when I set PUID to 1026:

 


2019-10-14 10:45:18,901 WARN received SIGTERM indicating exit request
2019-10-14 10:45:18,901 DEBG killing watchdog-script (pid 150) with signal SIGTERM
2019-10-14 10:45:18,901 INFO waiting for start-script, watchdog-script to die
2019-10-14 10:45:19,904 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 139908803456720 for <Subprocess at 139908803414864 with name watchdog-script in state STOPPING> (stdout)>
2019-10-14 10:45:19,904 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 139908802859344 for <Subprocess at 139908803414864 with name watchdog-script in state STOPPING> (stderr)>
2019-10-14 10:45:19,904 INFO stopped: watchdog-script (terminated by SIGTERM)
2019-10-14 10:45:19,905 DEBG received SIGCHLD indicating a child quit
2019-10-14 10:45:19,906 DEBG killing start-script (pid 149) with signal SIGTERM
2019-10-14 10:45:19,907 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139908803414992 for <Subprocess at 139908803313488 with name start-script in state STOPPING> (stdout)>
2019-10-14 10:45:19,907 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139908803456784 for <Subprocess at 139908803313488 with name start-script in state STOPPING> (stderr)>
2019-10-14 10:45:19,907 INFO stopped: start-script (terminated by SIGTERM)
2019-10-14 10:45:19,907 DEBG received SIGCHLD indicating a child quit
Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

After the first crash, the last bit with logo is repeating every time docker restarts e.g:

 


Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/
2019-10-14 10:46:46.583010 [info] System information Linux DelugeVPN 4.4.59+ #24922 SMP PREEMPT Mon Aug 19 12:13:37 CST 2019 x86_64 GNU/Linux
2019-10-14 10:46:46.648330 [info] PUID defined as '1026'

 

Cheers.

if you change the puid and/or pgid then you need to reset permissions for the container to work again, you do this by stopping the container, then delete the file /config/perms.txt and then start the container again, note it can take a couple of mins to re-apply permissions so be patient.

Link to post
@binhex any feedback or idea based on this .conf file?
The only thing I spotted is that you have 3 plugins enabled, and they may not be compatible with deluge v2. What you could try is rename core.conf to something like core.conf.old and then restart the container see if you can access the web UI

Sent from my CLT-L09 using Tapatalk

Link to post
On 10/14/2019 at 1:01 AM, karka said:

Does anyone know why in my case this docker only works if using root privileges e.g if both PUID & PGID are set to 0? If I set my user (1026 and 100) then docker keeps restarting in an endless loop.

if you change the value of PUID and PGID then you MUST delete the file /config/perms.txt and restart the container.

Link to post
21 hours ago, binhex said:

The only thing I spotted is that you have 3 plugins enabled, and they may not be compatible with deluge v2. What you could try is rename core.conf to something like core.conf.old and then restart the container see if you can access the web UI

Sent from my CLT-L09 using Tapatalk
 

Clearing the old core.conf file allowed me to access the webgui! Now to re-dial in the settings. Thanks @binhex !

Link to post

Unraid newb here. Got my new server up and running. Plex is running great. Got my live tv up and running. I downloaded delugevpn tonight and followed spaceinvaders tutorial. The container works. I can download a public block list from the container. But, if I try to add a .torrent file to manually test it out, it shows the .torrent file name but it does not expand the torrent file and nothing is in "files" or "options" to add. These are from a private tracker. Any ideas?

Link to post

Hello!! I just reinstalled all my dockers etc after a cache failure.... and now I have deluge reinstalled and appears to be running in docker just fine with no errors, except for one, I cannot login.  I have no leftover parts from previous install. and yes i tried the default password of deluge to no avail. Any help would be greatly appreciated. I have reinstalled and deleted everything for deluge multiple times.  Thanks!

Link to post
1 hour ago, Medikherb said:

Hello!! I just reinstalled all my dockers etc after a cache failure.... and now I have deluge reinstalled and appears to be running in docker just fine with no errors, except for one, I cannot login.  I have no leftover parts from previous install. and yes i tried the default password of deluge to no avail. Any help would be greatly appreciated. I have reinstalled and deleted everything for deluge multiple times.  Thanks!

I just deleted the core.conf and am fine now. thanks.

Link to post

Ever since the Deluge V2 upgrade (weeks, or even months, ago) I have been using the AutoAdd plugin to load torrents from CouchPotato (using the BlackHole mechanism).  For some reason, around a week ago, this stopped functioning - the .torrent files are written by CouchPotato, but Deluge no longer seems to respond to them.  To the best of my knowledge, I've not made any configuration changes, and CouchPotato certainly hasn't received any updates.  Has something changed in DelugeVPN which might be responsible?

Link to post
8 hours ago, PeterB said:

Ever since the Deluge V2 upgrade (weeks, or even months, ago) I have been using the AutoAdd plugin to load torrents from CouchPotato (using the BlackHole mechanism).  For some reason, around a week ago, this stopped functioning - the .torrent files are written by CouchPotato, but Deluge no longer seems to respond to them.  To the best of my knowledge, I've not made any configuration changes, and CouchPotato certainly hasn't received any updates.  Has something changed in DelugeVPN which might be responsible?

not that i can think of, no, this is still the same version of deluge v2 so no change there and i very much doubt any code changes i have made would change the function of that plugin.

Edited by binhex
Link to post
On 8/15/2019 at 7:23 AM, binhex said:

not at present, no, its actually a rather large piece of work to add support for wireguard, but i am aware of it.

Now that 6.8-rc1 has been released with wireguard support, does it make it easier for you to support wireguard in your docker images for deluge and qbittorrent? Thanks.

Link to post

Hi all,

 

I keep failing to get several binhex "vpn dockers" run simultaneously.

 

For example: if i start the binhex-delugevpn docker alone, everything works fine; but as soon as I start e.g. binhex-privoxyvpn or binhex-qbittorrentvpn, then all connections made in binhex-delugevpn die.

 

Please note that all of those dockers are set to use différent ports, and that privoxy is set to "no" in binhex-delugevpn and binhex-qbittorrentvpn containers configuration.

 

Any idea why ?

 

Many thanks !

G

 

PS : thank you binhex for your apps !

Link to post
Hi all,
 
I keep failing to get several binhex "vpn dockers" run simultaneously.
 
For example: if i start the binhex-delugevpn docker alone, everything works fine; but as soon as I start e.g. binhex-privoxyvpn or binhex-qbittorrentvpn, then all connections made in binhex-delugevpn die.
 
Please note that all of those dockers are set to use différent ports, and that privoxy is set to "no" in binhex-delugevpn and binhex-qbittorrentvpn containers configuration.
 
Any idea why ?
 
Many thanks !
G
 
PS : thank you binhex for your apps !
Check for port clashes, especially port 8118 (privoxy)

Sent from my CLT-L09 using Tapatalk

Link to post
4 hours ago, binhex said:

Check for port clashes, especially port 8118 (privoxy)

Hi binhex,

Thank you for your answer. The thing is that all dockers are set to use different ports (see screenshot below). Am I missing something ?

Thanks,

G

Capture.thumb.PNG.abe54118ec6487112a27b8c767fe49f9.PNG

Edited by Opawesome
typo
Link to post
On 10/19/2019 at 9:45 PM, Opawesome said:

Thank you for your answer. The thing is that all dockers are set to use different ports (see screenshot below). Am I missing something ?

Thanks,

that looks fine to me, can you just try starting the troublesome container at the command line, this should tell you whats going on:-

 

docker start <name of my container>

@bugster you can have the same port number on the container side, this does NOT cause a port clash when in 'bridge' mode

Edited by binhex
Link to post

Having issues with this docker. When i go pull up the webGUI nothing comes up. I assume cause VPN issues? However it was working a few hours ago. Only change I know of is I restarted and added another drive to unraid server. Any ideas?

 

If i turn off VPN gui comes up. enabled it and gui wont start.

 

unless PIA changed their settings?

Edited by scubieman
Link to post
11 minutes ago, scubieman said:

Having issues with this docker. When i go pull up the webGUI nothing comes up. I assume cause VPN issues? However it was working a few hours ago. Only change I know of is I restarted and added another drive to unraid server. Any ideas?

 

If i turn off VPN gui comes up. enabled it and gui wont start.

 

unless PIA changed their settings?

i earlier saw that PIA DNS is a bit screwed with my logging picking it up as a [crit] failure to resolve the endpoint, check your log.

Edited by binhex
Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.