[Support] binhex - DelugeVPN


Recommended Posts

4 hours ago, binhex said:

my sig, click on help link

 

Cheers. Managed to figure it out (sort of)

I think the VPN server has gone, so I changed to a different one, but then couldn't get that to work either.

Turns out it doesn't know/like DNS so I had to put in the IP of the new server, rather than the URL in "VPN_REMOTE" field

 

Link to comment

So I am at a loss setting this up.  If anyone could take a look it would be appreciated.  I am sure I am missing something easy.

 

here is what was output after editing.  I did verify my user and pass were good.

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="binhex-delugevpn" --net="bridge" --privileged="true" -e TZ="America/Chicago" -e HOST_OS="unRAID" -e "VPN_ENABLED"="yes" -e "VPN_USER"="xxxxxxxx" -e "VPN_PASS"="xxxxxxxx" -e "VPN_REMOTE"="us-chicago.privateinternetaccess.com" -e "VPN_PORT"="1198" -e "VPN_PROTOCOL"="udp" -e "VPN_DEVICE_TYPE"="tun" -e "VPN_PROV"="pia" -e "VPN_OPTIONS"="000" -e "STRONG_CERTS"="no" -e "ENABLE_PRIVOXY"="no" -e "LAN_NETWORK"="192.168.1.0/24" -e "NAME_SERVERS"="8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177" -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/cache/download/":"/data":rw -v "/mnt/user/appdata/binhex-delugevpn":"/config":rw binhex/arch-delugevpn

Link to comment
So I am at a loss setting this up.  If anyone could take a look it would be appreciated.  I am sure I am missing something easy.
 
here is what was output after editing.  I did verify my user and pass were good.
 
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="binhex-delugevpn" --net="bridge" --privileged="true" -e TZ="America/Chicago" -e HOST_OS="unRAID" -e "VPN_ENABLED"="yes" -e "VPN_USER"="xxxxxxxx" -e "VPN_PASS"="xxxxxxxx" -e "VPN_REMOTE"="us-chicago.privateinternetaccess.com" -e "VPN_PORT"="1198" -e "VPN_PROTOCOL"="udp" -e "VPN_DEVICE_TYPE"="tun" -e "VPN_PROV"="pia" -e "VPN_OPTIONS"="000" -e "STRONG_CERTS"="no" -e "ENABLE_PRIVOXY"="no" -e "LAN_NETWORK"="192.168.1.0/24" -e "NAME_SERVERS"="8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177" -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/cache/download/":"/data":rw -v "/mnt/user/appdata/binhex-delugevpn":"/config":rw binhex/arch-delugevpn

My SIG help link

Sent from my SM-G900F using Tapatalk

Link to comment
10 minutes ago, Athens428 said:

 

Got it! I attached the file here.  Please let me know if this is the wrong spot! Thank you

supervisord.log

can you please check that log again, it looks like it hasnt quite completed, is the last line in the log?;- '[debug] Waiting for valid IP address from tunnel...' it should have some log output from openvpn.

 

Link to comment
7 minutes ago, binhex said:

can you please check that log again, it looks like it hasnt quite completed, is the last line in the log?;- '[debug] Waiting for valid IP address from tunnel...' it should have some log output from openvpn.

 

 

I am running it again since it seems to have stopped at some point.  Quick question though.  For my LAN_Network, my router's address is 192.168.1.1 not .....1.0.  Does this make the difference? I also have IP Pooling set up so my assignable IP's start at ...1.50 not from 0 or 1.

 

I have tried both of those options but neither worked, just trying to sort this out.  I will post the new log file in a few minutes.

Link to comment
1 minute ago, Athens428 said:

For my LAN_Network, my router's address is 192.168.1.1 not .....1.0.  Does this make the difference? I also have IP Pooling set up so my assignable IP's start at ...1.50 not from 0 or 1.

if your router ip is 192.168.1.1 then your lan network value should be 192.168.1.0/?? where ?? is the netmask, i cant tell you what that is but assuming a netmask of 255.255.255.0 it would be /24

Link to comment
9 minutes ago, binhex said:

if your router ip is 192.168.1.1 then your lan network value should be 192.168.1.0/?? where ?? is the netmask, i cant tell you what that is but assuming a netmask of 255.255.255.0 it would be /24

 

yeah 192.168.1.0/24 is what i ahve input, i did verify my subnet mask was 255.255.255.0 and therefore should be /24.

 

The log file shows the same last line as before ( [debug] Waiting for valid IP address from tunnel... ) 12 minutes after starting.  I will give it a few more minutes just in case then post the log.

Link to comment
17 minutes ago, binhex said:

if your router ip is 192.168.1.1 then your lan network value should be 192.168.1.0/?? where ?? is the netmask, i cant tell you what that is but assuming a netmask of 255.255.255.0 it would be /24

 

Here is the log, 20 mins and still sitting at the waiting line.  I did double verify that the user/pass are good.  

supervisord.log

Link to comment
Just now, binhex said:

hmm very odd!, ok can you try a different vpn remote endpoint, go for nl.privateinternetaccess.com as i know that works.

 

I will do that when i get home from work. I still have to set up remote access to the server.  Thank you for your help so far!

Link to comment

Maybe this is a general question about Deluge.

 

I don't under stand why i can't add a user and password to Deluge.

Apparently i need it to get Couchpotato to communicate with Deluge.

 

I used Krusader to edit Auth file and added username and password,restarted Deluge.

But i never get the opportunity to choose user when i start Web-gui.

What am i doing wrong?

 

 

Skärmavbild 2017-05-11 kl. 16.01.19.png

Link to comment
2 hours ago, Lappen71 said:

Maybe this is a general question about Deluge.

 

I don't under stand why i can't add a user and password to Deluge.

Apparently i need it to get Couchpotato to communicate with Deluge.

 

I used Krusader to edit Auth file and added username and password,restarted Deluge.

But i never get the opportunity to choose user when i start Web-gui.

What am i doing wrong?

 

 

Skärmavbild 2017-05-11 kl. 16.01.19.png

 

my sig, click on the vpn docker faq link, then scroll down to the delugevpn specific section, its answered there.

Link to comment
8 hours ago, binhex said:

hmm very odd!, ok can you try a different vpn remote endpoint, go for nl.privateinternetaccess.com as i know that works.

 

So I guess it had to do with the url i was using.  switching to the Netherlands one I can start with no issues.  Thanks for all the help!!

Link to comment
13 hours ago, Athens428 said:

 

So I guess it had to do with the url i was using.  switching to the Netherlands one I can start with no issues.  Thanks for all the help!!

i can only assume your isp was blocking you, i could successfully connect to the endpoint you had specified, a bit odd, but it wouldnt be the first time that ISP's have screwed with internet connectivity.

Link to comment
25 minutes ago, binhex said:

i can only assume your isp was blocking you, i could successfully connect to the endpoint you had specified, a bit odd, but it wouldnt be the first time that ISP's have screwed with internet connectivity.

 

The even weirder thing is that on my pc I connect to that server with no issues. Very weird but if the torrent trackers think my isp is in the Netherlands, so much the better heh.

 

If it works don't question it. Thanks again!!!

Link to comment

I am struggling (maybe cos I am using a free VPN that comes with usenetserver sub and not PIA?)


root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Deluge-VPN" --net="bridge" --privileged="true" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "VPN_ENABLED"="yes" -e "VPN_USER"="username@usenetserver" -e "VPN_PASS"="pass1234" -e "VPN_REMOTE"="ams-a01.wlvpn.com" -e "VPN_PORT"="1194" -e "VPN_PROTOCOL"="udp" -e "VPN_DEVICE_TYPE"="tun" -e "VPN_PROV"="custom" -e "VPN_OPTIONS"="" -e "STRONG_CERTS"="no" -e "ENABLE_PRIVOXY"="no" -e "LAN_NETWORK"="192.168.0.0/24" -e "NAME_SERVERS"="8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177" -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/share/downloads/":"/data":rw -v "/mnt/user/appdata/binhex-delugevpn":"/config":rw binhex/arch-delugevpn
 

Nothing untoward in the log which says "starting OpenVPN" and "OpenVPN started" so seems to have that running fine but the Deluge UI (at http://192.168.0.200:8112/) won't open... if I disable VPN it does...

 

Sorry if its appallingly obvious to everyone what I have done wrong but I am stumped.... Maybe when I can get VPN working I can then enable Privoxy too? :-)

Link to comment
1 hour ago, methanoid said:

I am struggling (maybe cos I am using a free VPN that comes with usenetserver sub and not PIA?)


root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Deluge-VPN" --net="bridge" --privileged="true" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "VPN_ENABLED"="yes" -e "VPN_USER"="username@usenetserver" -e "VPN_PASS"="pass1234" -e "VPN_REMOTE"="ams-a01.wlvpn.com" -e "VPN_PORT"="1194" -e "VPN_PROTOCOL"="udp" -e "VPN_DEVICE_TYPE"="tun" -e "VPN_PROV"="custom" -e "VPN_OPTIONS"="" -e "STRONG_CERTS"="no" -e "ENABLE_PRIVOXY"="no" -e "LAN_NETWORK"="192.168.0.0/24" -e "NAME_SERVERS"="8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177" -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/share/downloads/":"/data":rw -v "/mnt/user/appdata/binhex-delugevpn":"/config":rw binhex/arch-delugevpn
 

Nothing untoward in the log which says "starting OpenVPN" and "OpenVPN started" so seems to have that running fine but the Deluge UI (at http://192.168.0.200:8112/) won't open... if I disable VPN it does...

 

Sorry if its appallingly obvious to everyone what I have done wrong but I am stumped.... Maybe when I can get VPN working I can then enable Privoxy too? :-)

 

If possible try a different server.  I was having a very similar issue (with pia) and the solution was pointing at a different vpn server.

Link to comment

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

Link to comment
On 2017-5-13 at 0:07 AM, DJiK said:

I'm trying to run DelugeVPN on a remote server that I have full root access to.

OK so firstly your log shows a clean startup, so there isn't any issues with your configuration, however due to the way delugevpn (and the other vpn dockers i produce) has been coded it currently is suited to a traditional home/work LAN setup, where you access the webui inside your LAN or port forward the port on your router to gain access over the internet. As your box is different, in that its connected directly to the internet (right?) you don't have a separation of LAN and internet. So i think in order to accommodate this new usage i will need to relax the iptable rules to allow access to the webui (obviously not daemon) from any ip, this should then allow you to view the webui, i will have a think about it.

Link to comment
Quote

As your box is different, in that its connected directly to the internet (right?)…

That's correct.

 

Quote

i will have a think about it.

Thank you so much! Please let me know if I can help by trying out different configuration parameters on my server on your behalf.

Link to comment

I updated the container and now just get

Mon May 15 22:31:35 2017 VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=US, ST=NY, L=New York, O=vpnsecure.me, OU=Office, CN=vpnsecure-server, [email protected]
Mon May 15 22:31:35 2017 OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
Mon May 15 22:31:35 2017 TLS_ERROR: BIO read tls_read_plaintext error
Mon May 15 22:31:35 2017 TLS Error: TLS object -> incoming plaintext read error
Mon May 15 22:31:35 2017 TLS Error: TLS handshake failed
Mon May 15 22:31:35 2017 SIGUSR1[soft,tls-error] received, process restarting

 

 

I think it's because of what they talk about in here https://bugs.archlinux.org/task/53831 .  Although when I look at my certs they say Signature Algorithm/Signature hash algorithm SHA256 thumprint algorithm sha1

 

Is there a way to revert back to the previous version?

Link to comment

Hi binhex,

I have been using this docker for a long time now and it is just fantastic.

But recently it stopped working for me.

I can't connect to the website anymore.

 

Previously I was able to debug the logfile, but this time I can't find where to start.

 

root@Tower:/mnt/cache/appdata/deluge# cat supervisord.log
Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/
2017-05-16 22:35:35.099496 [info] Host is running unRAID
2017-05-16 22:35:35.123464 [info] System information Linux b1566d3dff6f 4.9.19-unRAID #1 SMP PREEMPT Thu Mar 30 08:32:28 PDT 2017 x86_64 GNU/Linux
2017-05-16 22:35:35.148573 [warn] PUID not defined (via -e PUID), defaulting to '99'
2017-05-16 22:35:35.177215 [warn] PGID not defined (via -e PGID), defaulting to '100'
2017-05-16 22:35:35.215138 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2017-05-16 22:35:35.240178 [info] Permissions already set for volume mappings
2017-05-16 22:35:35.272918 [info] VPN_ENABLED defined as 'yes'
2017-05-16 22:35:35.296944 [info] VPN_PROV defined as 'custom'
2017-05-16 22:35:35.324490 [info] VPN_REMOTE defined as 'connect-openvpn.swissvpn.net'
2017-05-16 22:35:35.351916 [info] VPN_PORT defined as '443'
2017-05-16 22:35:35.376071 [info] VPN_PROTOCOL defined as 'tcp'
2017-05-16 22:35:35.400712 [info] LAN_NETWORK defined as '192.168.2.0/24'
2017-05-16 22:35:35.424650 [warn] NAME_SERVERS not defined (via -e NAME_SERVERS), defaulting to Google and FreeDNS name servers
2017-05-16 22:35:35.448234 [info] VPN_USER defined as 'XXXXXXX'
2017-05-16 22:35:35.472268 [info] VPN_PASS defined as 'XXXXXXX'
2017-05-16 22:35:35.495133 [warn] VPN_DEVICE_TYPE not defined (via -e VPN_DEVICE_TYPE), defaulting to 'tun'
2017-05-16 22:35:35.516841 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2017-05-16 22:35:35.538718 [info] ENABLE_PRIVOXY defined as 'yes'
2017-05-16 22:35:35.558664 [info] Setting permissions on files/folders inside container...
2017-05-16 22:35:35,788 CRIT Set uid to user 0
2017-05-16 22:35:35,788 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2017-05-16 22:35:35,790 INFO supervisord started with pid 7
2017-05-16 22:35:36,792 INFO spawned: 'start-script' with pid 107
2017-05-16 22:35:36,793 INFO spawned: 'deluge-script' with pid 108
2017-05-16 22:35:36,794 INFO spawned: 'deluge-web-script' with pid 109
2017-05-16 22:35:36,796 INFO spawned: 'privoxy-script' with pid 110
2017-05-16 22:35:36,801 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
2017-05-16 22:35:36,801 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-16 22:35:36,801 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-16 22:35:36,801 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-16 22:35:36,801 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-16 22:35:36,807 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy
2017-05-16 22:35:36,808 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid
2017-05-16 22:35:36,814 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/swissvpn.ovpn
2017-05-16 22:35:36,815 DEBG 'start-script' stderr output:
dos2unix:
2017-05-16 22:35:36,815 DEBG 'start-script' stderr output:
converting file /config/openvpn/swissvpn.ovpn to Unix format...
2017-05-16 22:35:36,838 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1
2017-05-16 22:35:36,841 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf
2017-05-16 22:35:36,843 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf
2017-05-16 22:35:36,845 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf
2017-05-16 22:35:36,848 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf
2017-05-16 22:35:36,852 DEBG 'start-script' stdout output:
[info] Adding 192.168.2.0/24 as route via docker eth0
2017-05-16 22:35:36,853 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------
2017-05-16 22:35:36,853 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.2.0/24 via 172.17.0.1 dev eth0
2017-05-16 22:35:36,853 DEBG 'start-script' stdout output:
--------------------
2017-05-16 22:35:36,859 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables
2017-05-16 22:35:36,876 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16
2017-05-16 22:35:36,919 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------
2017-05-16 22:35:36,922 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-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 tcp -m tcp --sport 443 -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.2.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.2.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 443 -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.2.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.2.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
2017-05-16 22:35:36,924 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...
2017-05-16 22:35:36,937 DEBG 'start-script' stdout output:
[info] OpenVPN started

I am not aware of any changes that I have done recently.

Any help would be greatly appreciated.
 

Link to comment

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.