Jump to content
binhex

[Support] binhex - DelugeVPN

5849 posts in this topic Last Reply

Recommended Posts

1 minute ago, binhex said:

simple enough, just add your additional network to the LAN_NETWORK env var using a comma to separate them, e.g.:-

LAN_NETWORK=192.168.1.0/24,10.1.1.0/24

Awesome ! Thanks a lot ! Didn't think it was possible, I should have tried :)

Share this post


Link to post

I'm not using Black Hole but, since the deluge interface from CouchPotato no longer works with deluge v2, I have set CP to use the BH method of sending magnet/torrent files to deluge V2.

Simply configure the 'AutoAdd' plugin in deluge to find the magnet/torrent files.

Share this post


Link to post
1 hour ago, PeterB said:

I'm not using Black Hole but, since the deluge interface from CouchPotato no longer works with deluge v2, I have set CP to use the BH method of sending magnet/torrent files to deluge V2.

Simply configure the 'AutoAdd' plugin in deluge to find the magnet/torrent files.

Perfect! Thank you!

Share this post


Link to post

I must begin and end with IMMENSE appreciation for Binhex for creating all these setups for us to use, and the authors of these software that are incredibly useful.   THANK YOU, THANK YOU

 

Deluge V2 seems to be a huge improvement, but I have found this to be a brutal breaking change given that there are no compatible clients for Windows or OS X.  While I use other utilities like sonarr and radarr to initiate deluge downloading, I also use a Deluge client on my Mac.  Furthermore,  I'm afraid to downgrade, given the reports of losing older seeding torrents.

How do maintainers (such as Binhex) choose when to upgrade underlying components and when to create a new version?  Please feel free to point me at relevant discussion, I'm haven't found anything about this despite my searching.

Please accept this post as feedback that, as a user, I would have preferred to wait for a Deluge V2 upgrade after a OS X client was available.
 

That said, I must begin and end with IMMENSE appreciation for Binhex for creating all these setups for us to use, and the authors of these software that are incredibly useful.   THANK YOU, THANK YOU

Share this post


Link to post

I'm not sure which docker is having this issue. But what is going on is that i'm telling radarr or sonarr to search for a show/movie and it finds it and sends it over to delugevpn no problem. When it is finished it put it back to the bottom of the queue at 100% with no number indicated on the order it is in. For the TV shows it is going to /mnt/user/media/Tv_Shows/ but it is still in the completed folder I have as well. But for the movies it does not go to  /mnt/user/media/Movies like it is set to do and it just stays in the completed folder. I've tried looking for any invalid characters or non English letters. I've re watched the setup videos spaceinvaderone did on each docker again to make sure it is setup correctly.

Share this post


Link to post
2 hours ago, knipster said:

I must begin and end with IMMENSE appreciation for Binhex for creating all these setups for us to use, and the authors of these software that are incredibly useful.   THANK YOU, THANK YOU

 

Deluge V2 seems to be a huge improvement, but I have found this to be a brutal breaking change given that there are no compatible clients for Windows or OS X.  While I use other utilities like sonarr and radarr to initiate deluge downloading, I also use a Deluge client on my Mac.  Furthermore,  I'm afraid to downgrade, given the reports of losing older seeding torrents.

How do maintainers (such as Binhex) choose when to upgrade underlying components and when to create a new version?  Please feel free to point me at relevant discussion, I'm haven't found anything about this despite my searching.

Please accept this post as feedback that, as a user, I would have preferred to wait for a Deluge V2 upgrade after a OS X client was available.
 

That said, I must begin and end with IMMENSE appreciation for Binhex for creating all these setups for us to use, and the authors of these software that are incredibly useful.   THANK YOU, THANK YOU

Typically dockers will update to the most recent version of the app automatically. There isn't really any decision making involved. I'm sure @binhex can provide more specifics for this particular docker.

 

You can downgrade back to deluge 1.3 using tags. Start reading here and scroll through the next several posts you'll see what version number to use in the tag. I also had to restore from backup after downgrading to get my torrents back.

Share this post


Link to post
3 hours ago, knipster said:

How do maintainers (such as Binhex) choose when to upgrade underlying components and when to create a new version?

Plex is the best example for this.

 

LSIO:  Everytime the app is restarted, it will update to the latest release from Plex Inc. (automatic)

Binhex: Whenever the update get pushed upstream to whatever repository he uses, an update to the container will be released. (automatic)

LT: Whenever the maintainer deems that the update is safe / stable / people are complaining will update the container and release an update. (manual)

 

If you take plex out of the equation, then LSIO changes to be every Friday an update is released. 

 

Pros and cons to each of the above scenarios.

 

Edited by Squid

Share this post


Link to post

just updated your contanier now i cant access the webui with pia set to yes.  otherwise if i turn pia off it loads just fine.  ive attached a debug log for you to look at ive made sure that no passwords or username are in it.  thankyou

debug.log

Share this post


Link to post

For those of you using PIA for VPN and have been waiting for the ltConfig plugin to be available for Deluge 2.0, the maintainer has released a forked beta version.  You'll need to compile the plugin yourself in Python 3.7 for it to work however. 

 

ltConfig Beta Version -> https://github.com/JoshDi/deluge-ltconfig

 

To ensure the plugin was compatible, I actually compiled it directly within the latest binhex-delugevpn container and then copied the resulting .egg to the binhex-delugevpn plugin directory on my unRAID host. 

 

After restarting delugevpn, I was then able to enable the plugin and disable/uncheck the following settings.  Make sure to also check "Apply settings on startup".

 

enable_incoming_utp

enable_outgoing_utp

 

Once these two settings are disabled, my torrent speeds skyrocketed back to where they should be.

 

If anyone needs help with this process or would like me to just post the pre-compiled plugin, let me know.

Edited by raiditup

Share this post


Link to post
15 hours ago, dirknina said:

just updated your contanier now i cant access the webui with pia set to yes.  otherwise if i turn pia off it loads just fine.  ive attached a debug log for you to look at ive made sure that no passwords or username are in it.  thankyou

debug.log 16.04 kB · 0 downloads

Found your post as mine did the same thing after latest update that I just applied now.  I flipped the network setting in the docker config from bridge to host, saved, and back to bridge.  It took a min but I was able to access the webui again.  Not sure if that helps or not. 

Share this post


Link to post
5 minutes ago, gzibell said:

Found your post as mine did the same thing after latest update that I just applied now.  I flipped the network setting in the docker config from bridge to host, saved, and back to bridge.  It took a min but I was able to access the webui again.  Not sure if that helps or not. 

i know you are trying to help, but please dont generalise not being able to access the web ui with vpn enabled, there are literally dozens of reasons why you cant access it, and in this case @dirknina yours is this:-

 

Sun Jul 14 15:13:14 2019 AUTH: Received control message: AUTH_FAILED

this means your login and/or password is incorrect, if you haven't touched these then its either the vpn provider was having issues or that your subscription has expired.

Share this post


Link to post
On 5/12/2017 at 4:07 PM, DJiK said:

Hi @binhex, could you please help me out?

 

I'm trying to run DelugeVPN on a remote server that I have full root access to. The problem is that I cannot access WebUI via the public web when VPN_ENABLED=yes. I.e., "page not found" on http://domain.com:8112. Having read through a lot of posts on this thread, I have narrowed the problem down to:

  1. Incorrect LAN_NETWORK settings
    ifconfig returns the following (somewhat masked) results:
    
    docker0   Link encap:Ethernet  HWaddr 02:42:87:a1:2a:94
              inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
              inet6 addr: [masked] Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:365588 errors:0 dropped:0 overruns:0 frame:0
              TX packets:2189298 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:55260071 (55.2 MB)  TX bytes:328364237 (328.3 MB)
    
    ens18     Link encap:Ethernet  HWaddr [masked]
              inet addr:11.22.33.239  Bcast:11.22.33.255  Mask:255.255.255.224
              inet6 addr: [masked] Scope:Link
              inet6 addr: [masked] Scope:Global
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:136502544 errors:145 dropped:0 overruns:0 frame:145
              TX packets:125433044 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:54284693025 (54.2 GB)  TX bytes:27021607924 (27.0 GB)

    Whereby, I have set LAN_NETWORK to be 11.22.33.224/27, according to this CIDR calculator.
     

  2. Not exposing the port from within Docker
    As you have recommended to another user, I ran curl http://localhost:8112 from within the server, and it showed the HTML contents of the Deluge UI client. However, other applications that are configured in the same way (as seen with the docker ps command) are properly exposed and are visible to the outside world.

This is my first time trying to configure Deluge with VPN. I have signed up with privateinternetaccess™ and even generated a different VPN user a few times to ensure that there are no special characters in either the username or the password -- there weren't any.

 

Lastly, please see my slightly masked supervisord.log attached below. Thanks for all of your help and for this great piece of software!

supervisord.log


Hey @binhex I was searching google and this post from two years ago came up. This individual had the same problem I'm facing right now where there is no LAN and it's directly connected to the internet. I was wondering if you pushed a fix for odd cases like these? Thanks.

Share this post


Link to post
2 hours ago, nicekevin said:

This individual had the same problem I'm facing right now where there is no LAN and it's directly connected to the internet.

Unraid is not hardened to be directly connected to the internet. It must be behind a firewall.

Share this post


Link to post
2 hours ago, jonathanm said:

Unraid is not hardened to be directly connected to the internet. It must be behind a firewall.

Ah I'm not running unraid. Just Ubuntu with docker.

Share this post


Link to post

As with a few others I seem to be having problems with PIA, It's been running fine since I moved from rutorrent around December last year, but stopped today after updating the docker yesterday. I have rolled back 2 versions and still can't get to the GUI and other dockers can't send torrents to it, I also tried a different PIA server to see if that was the issue without success. If I disable the VPN the GUI works.

 

No sign of any issues within the logs that I can see.

 

supervisord.log (VPN USER\PASS Masked)

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2019-07-16 11:53:31.684483 [info] System information Linux b50183129941 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 GNU/Linux
2019-07-16 11:53:31.739405 [info] PUID defined as '99'
2019-07-16 11:53:31.778824 [info] PGID defined as '100'
2019-07-16 11:53:31.880990 [info] UMASK defined as '000'
2019-07-16 11:53:31.910583 [info] Permissions already set for volume mappings
2019-07-16 11:53:31.944029 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
2019-07-16 11:53:31.975033 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
2019-07-16 11:53:32.005984 [info] VPN_ENABLED defined as 'yes'
2019-07-16 11:53:32.044512 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...
2019-07-16 11:53:32.090271 [info] VPN remote line defined as 'remote ca-toronto.privateinternetaccess.com 1198'
2019-07-16 11:53:32.122070 [info] VPN_REMOTE defined as 'ca-toronto.privateinternetaccess.com'
2019-07-16 11:53:32.154766 [info] VPN_PORT defined as '1198'
2019-07-16 11:53:32.189617 [info] VPN_PROTOCOL defined as 'udp'
2019-07-16 11:53:32.222186 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-07-16 11:53:32.253393 [info] VPN_PROV defined as 'pia'
2019-07-16 11:53:32.290793 [info] LAN_NETWORK defined as '192.168.0.0/24'
2019-07-16 11:53:32.327020 [info] NAME_SERVERS defined as '209.222.18.222,1.1.1.1,8.8.8.8,209.222.18.218,1.0.0.1,8.8.4.4'
2019-07-16 11:53:32.361452 [info] VPN_USER defined as 'XXXX'
2019-07-16 11:53:32.394370 [info] VPN_PASS defined as 'XXXX'
2019-07-16 11:53:32.426857 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-07-16 11:53:32.463078 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-07-16 11:53:32.496076 [info] ENABLE_PRIVOXY defined as 'yes'
2019-07-16 11:53:32.530811 [info] Starting Supervisor...
2019-07-16 11:53:32,723 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-07-16 11:53:32,723 INFO Set uid to user 0 succeeded
2019-07-16 11:53:32,725 INFO supervisord started with pid 6
2019-07-16 11:53:33,728 INFO spawned: 'start-script' with pid 147
2019-07-16 11:53:33,729 INFO spawned: 'watchdog-script' with pid 148
2019-07-16 11:53:33,730 INFO reaped unknown pid 7
2019-07-16 11:53:33,736 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-07-16 11:53:33,736 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-07-16 11:53:33,736 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-07-16 11:53:33,738 DEBG 'watchdog-script' stderr output:
dos2unix: converting file /config/core.conf to Unix format...

2019-07-16 11:53:33,789 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-07-16 11:53:33,792 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2019-07-16 11:53:33,796 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2019-07-16 11:53:33,799 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-07-16 11:53:33,803 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2019-07-16 11:53:33,806 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2019-07-16 11:53:33,810 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-07-16 11:53:33,853 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2019-07-16 11:53:33,856 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.0/24 as route via docker eth0

2019-07-16 11:53:33,858 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-07-16 11:53:33,858 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.4
192.168.0.0/24 via 172.17.0.1 dev eth0

2019-07-16 11:53:33,859 DEBG 'start-script' stdout output:
--------------------

2019-07-16 11:53:33,861 DEBG 'start-script' stdout output:
iptable_mangle         16384  1
ip_tables              24576  3 iptable_filter,iptable_nat,iptable_mangle

2019-07-16 11:53:33,862 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2019-07-16 11:53:33,898 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-07-16 11:53:33,899 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -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

2019-07-16 11:53:33,900 DEBG 'start-script' stdout output:
--------------------

2019-07-16 11:53:33,901 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-07-16 11:53:33,908 DEBG 'start-script' stdout output:
Tue Jul 16 11:53:33 2019 WARNING: file 'credentials.conf' is group or others accessible
Tue Jul 16 11:53:33 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019
Tue Jul 16 11:53:33 2019 library versions: OpenSSL 1.1.1c  28 May 2019, LZO 2.10

2019-07-16 11:53:33,909 DEBG 'start-script' stdout output:
[info] OpenVPN started
Tue Jul 16 11:53:33 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-07-16 11:53:33,910 DEBG 'start-script' stdout output:
Tue Jul 16 11:53:33 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.107:1198

2019-07-16 11:53:33,910 DEBG 'start-script' stdout output:
Tue Jul 16 11:53:33 2019 UDP link local: (not bound)
Tue Jul 16 11:53:33 2019 UDP link remote: [AF_INET]172.98.67.107:1198

2019-07-16 11:53:34,796 DEBG 'start-script' stdout output:
Tue Jul 16 11:53:34 2019 [dfa7c579c79a374870350adc620b3760] Peer Connection Initiated with [AF_INET]172.98.67.107:1198

2019-07-16 11:53:36,271 DEBG 'start-script' stdout output:
Tue Jul 16 11:53:36 2019 TUN/TAP device tun0 opened
Tue Jul 16 11:53:36 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-07-16 11:53:36,272 DEBG 'start-script' stdout output:
Tue Jul 16 11:53:36 2019 /usr/bin/ip addr add dev tun0 local 10.22.10.14 peer 10.22.10.13

2019-07-16 11:53:36,273 DEBG 'start-script' stdout output:
Tue Jul 16 11:53:36 2019 /root/openvpnup.sh tun0 1500 1558 10.22.10.14 10.22.10.13 init

2019-07-16 11:53:36,279 DEBG 'start-script' stdout output:
Tue Jul 16 11:53:36 2019 Initialization Sequence Completed

2019-07-16 11:53:36,394 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2019-07-16 11:53:38,815 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2019-07-16 11:53:38,886 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com

2019-07-16 11:53:38,887 DEBG 'start-script' stdout output:
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com

2019-07-16 11:53:38,891 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=3dc3cde325c5b407199370458da9d041bb4d98e05d49cf6311983f2ac9112af7...

2019-07-16 11:53:40,015 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=3dc3cde325c5b407199370458da9d041bb4d98e05d49cf6311983f2ac9112af7, response code 200

2019-07-16 11:53:40,052 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2019-07-16 11:53:40,272 DEBG 'start-script' stdout output:
[info] DNS operational, we can resolve name 'www.google.com' to address '172.217.164.228'

2019-07-16 11:53:40,273 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2019-07-16 11:53:40,961 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 172.98.67.107

2019-07-16 11:53:41,010 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.22.10.14 different, marking for reconfigure

2019-07-16 11:53:41,014 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-07-16 11:53:41,017 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-07-16 11:53:41,020 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2019-07-16 11:53:41,020 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 22783 different, marking for reconfigure

2019-07-16 11:53:41,020 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-07-16 11:53:41,375 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.2.11.6'
[info] Deluge key 'listen_interface' will have a new value '10.22.10.14'
[info] Writing changes to Deluge config file '/config/core.conf'...

2019-07-16 11:53:41,586 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'...

2019-07-16 11:53:41,780 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'c11d5166a94dc914db6aea06fdfb28ed32903ef4'
[info] Deluge key 'default_daemon' will have a new value 'c11d5166a94dc914db6aea06fdfb28ed32903ef4'
[info] Writing changes to Deluge config file '/config/web.conf'...

2019-07-16 11:53:42,105 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-07-16 11:53:42,320 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2019-07-16 11:53:45,895 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

deluged.log

11:47:53 [INFO    ][deluge.core.torrentmanager    :885 ] Finished loading 224 torrents in 0:00:00.325328
11:47:54 [INFO    ][deluge.core.torrentmanager    :1609] on_alert_external_ip: 172.98.67.77
11:47:56 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 127.0.0.1:46286
11:47:56 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.

 

Share this post


Link to post
6 hours ago, Wob76 said:

have rolled back 2 versions and still can't get to the GUI and other dockers can't send torrents to it

how are you attempting to connect to deluge?, if you are using the thin client from mac or windows then you wont be able to, as you will be using an out of date deluge client (v1.x) which does not connect to deluge v2.x.

 

read post #3 of this thread for more details.

Share this post


Link to post
how are you attempting to connect to deluge?, if you are using the thin client from mac or windows then you wont be able to, as you will be using an out of date deluge client (v1.x) which does not connect to deluge v2.x.
 
read post #3 of this thread for more details.
I'm just trying to access the web GUI and I get nothing with the VPN on, I did try the windows app but it is probably outdated, I first noticed the issue as SickChill had an issue pushing a download to it. It was working find just a few days ago, but I can't work out if the issue is from the update or if it's a PIA issue.

Sent from my Pixel 3 XL using Tapatalk

Share this post


Link to post
26 minutes ago, Wob76 said:

I'm just trying to access the web GUI and I get nothing with the VPN on, I did try the windows app but it is probably outdated, I first noticed the issue as SickChill had an issue pushing a download to it. It was working find just a few days ago, but I can't work out if the issue is from the update or if it's a PIA issue.

Sent from my Pixel 3 XL using Tapatalk
 

When you say you try to access the web GUI, you launch the GUI from the docker tab? Can't see any errors out of the box from your log above, might be something in your run command

Share this post


Link to post
When you say you try to access the web GUI, you launch the GUI from the docker tab? Can't see any errors out of the box from your log above, might be something in your run command

I tried directly on the docket port for the web, I usually access via reverse proxy, neither work. With VPN on I don't see any activity in the deluge web log.  

 

 

Here is the run command, but it hasn't been changed in months so I don't think it's the issue.

 

docker run -d --name='delugevpn' --net='bridge' --log-opt max-size='50m' --log-opt max-file='3' --privileged=true -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXX' -e 'VPN_PASS'='XXXX' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'NAME_SERVERS'='209.222.18.222,1.1.1.1,8.8.8.8,209.222.18.218,1.0.0.1,8.8.4.4' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/downloads/':'/data':'rw' -v '/mnt/user/downloads/':'/downloads':'rw' -v '/mnt/user/appdata/delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 

 

I'll also try the updated thin client tomorrow to see if the deluge port is open, but to me it seems like none of the ports are open while the VPN is up.

 

Sent from my Pixel 3 XL using Tapatalk

 

 

 

 

 

 

 

Share this post


Link to post

So rolling back to binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04 fixes my issue, but it's not just the deluge port that isn't working, I can't connect to the web socket or the privoxy ports, logs are not giving me much indication of the issue.

 

Wob

Share this post


Link to post
23 hours ago, Wob76 said:

So rolling back to binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04 fixes my issue, but it's not just the deluge port that isn't working, I can't connect to the web socket or the privoxy ports, logs are not giving me much indication of the issue.

 

Wob

Rolling back with this worked for me, thank you. I am wondering if binhex should really fork v2 into delugevpn2.

Share this post


Link to post
4 hours ago, koltz said:

Rolling back with this worked for me, thank you. I am wondering if binhex should really fork v2 into delugevpn2.

Hopefully he is kind enough to create an updated v1 based image/tag should the non-deluge components need major updating.

Otherwise sitting on the most recent v1 tag works just fine IMO as deluge v1 hasn't been updated in 2 years.

Share this post


Link to post
6 hours ago, tjb_altf4 said:

Hopefully he is kind enough to create an updated v1 based image/tag should the non-deluge components need major updating

Indeed, but only in the case where there is a major issue, i.e. ip leakage, for now using the tags is the best way of switching back to v1.x.

 

Just to be clear deluge v2.x DOES work, however you will need to update all plugins to v2.x compatible and make sure your deluge thin client is updated (if you use that). If you dont use the deluge thin client and you dont need third party plugins then you should be good - see post #3 in this thread for more details regards current limitations.

Share this post


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.