Jump to content
binhex

[Support] binhex - DelugeVPN

7511 posts in this topic Last Reply

Recommended Posts

22 hours ago, Pducharme said:

Hi @binhex, using the DelugeVPN docker with wlvpn (the free VPN of NewsHosting account), but I got a new Windscribe account (Pro version Lifetime deal).   Windscribe now support "Port Forwarding".  I would like to know if I can use this with DelugeVPN docker?  Do I only need what is the Port Number that i'm assigned by Windscribe and add it as a Variable of the docker page of DelugeVPN ?  Thanks!

as long as windscribe supports openvpn clients then yep it should work just fine, just download the openvpn config file(s) and certs, put them in /config/openvpn and then set the vpn username and password credentials via the env vars. as far as port forwarding goes, if windscribe allocate you a static port them you simply go to deluge and set the port through the deluge web ui and you are done.

Share this post


Link to post

[Update: issue resolved via this FAQ entry:

 

Q13. I can see from the '/config/supervisord.log' file that the openvpn process keeps getting killed every 30 seconds on my QNAP appliance, what could be the cause of this?

 

A13. For some reason (unknown at this time) QNAP decided to kill any openvpn process running on the host by adding in a line to the 'daemon_mgr.conf' file. In order to prevent this you need to delete the following line from the 'daemon_mgr.conf':-

 

DAEMONxx = openvpn, stop, /usr/sbin/openvpn

Where xx will be 2 random digits.

 

Additional note: found instructions on how to use WinSCP to edit the daemon_mgr.conf file on QNAP here: https://forum.qnap.com/viewtopic.php?t=117004#p519883

 

end update.]

 

 

Hi, been working through setting up DelugeVPN in a Docker container on QNAP. Have it basically working, but get occasional errors. Using this script:

docker run  \

    --cap-add=NET_ADMIN \

    -p 8112:8112 \

    -p 8118:8118 \

    -p 58846:58846 \

    -p 58946:58946 \

    --name=delugevpn \

    -v /share/CACHEDEV1_DATA/appdata/delugevpn/data:/data \

    -v /share/CACHEDEV1_DATA/appdata/delugevpn/config:/config \

    -v /etc/localtime:/etc/localtime:ro \

    -e VPN_USER=[removed] \

    -e VPN_PASS=[rempved]  \

    -e VPN_PROV=torguard \

    -e STRICT_PORT_FORWARD=yes \

    -e ENABLE_PRIVOXY=yes \

    -e LAN_NETWORK=192.168.1.0/24 \

    -e NAME_SERVERS=209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4 \

    -e DELUGE_DAEMON_LOG_LEVEL=info \

    -e DELUGE_WEB_LOG_LEVEL=info \

    -e DEBUG=false \

    -e UMASK=000 \

    -e PUID=0 \

    -e PGID=0 \

    binhex/arch-delugevpn

I seem to get it running, and it does connect through VPN and show the right VPN external IP address. However, I regularly see this error:

2019-01-29 11:09:20,815 DEBG 'start-script' stdout output:
Tue Jan 29 11:09:20 2019 ERROR: Linux route add command failed: external program exited with error status: 2

Is this something of concern?

Possibly related, when I go to the Privoxy port (8118), a web page loads but I only see this error message: "Invalid header received from client."

 

Appreciate any feedback or assistance, with thanks!

Edited by Dublindog
Solved problem.

Share this post


Link to post

For the life of me, I can't fix my speed issues. I'm using PIA per SpaceInvaders youtube guide. I can only get around 1Mb downloads no matter what server I try.

 

Any suggestions?

 

 

Share this post


Link to post

Hey all! Trying to get the DelugeVPN container to work.  Followed SpaceInvaderOne's tutorial but seem to have an issue with torrents not starting.  They get added but forever stay paused at 0%.

I am using PIA and input my user and pass into the config, changed STRICT_PORT_FORWARD and ENABLE_PRIVOXY to yes, selected a PIA Server that supports port forwarding (CA Toronto) and placed that ovpn file in the openvpn folder along with the 2 ca.rsa.2048 files.  Everything appears fine when it starts but when I add torrents they just stay paused at 0%.  Any thoughts? Thanks!

Share this post


Link to post
3 minutes ago, jvorn said:

Hey all! Trying to get the DelugeVPN container to work.  Followed SpaceInvaderOne's tutorial but seem to have an issue with torrents not starting.  They get added but forever stay paused at 0%.

I am using PIA and input my user and pass into the config, changed STRICT_PORT_FORWARD and ENABLE_PRIVOXY to yes, selected a PIA Server that supports port forwarding (CA Toronto) and placed that ovpn file in the openvpn folder along with the 2 ca.rsa.2048 files.  Everything appears fine when it starts but when I add torrents they just stay paused at 0%.  Any thoughts? Thanks!

Sorry if this is a silly question, but are they actually paused?  That is, are you adding them in a paused state?  And if so, does pressing the "Resume" button at the top do anything?

Share this post


Link to post
Just now, Cessquill said:

Sorry if this is a silly question, but are they actually paused?  That is, are you adding them in a paused state?  And if so, does pressing the "Resume" button at the top do anything?

Yes sorry I should have said that, pressing resume appears to change nothing.

Share this post


Link to post

I'm guessing misconfigured volume mappings. Please post your docker run command or screenshot of the template settings and a screenshot of the deluge download settings.

 

Edit: And be sure to redact any username/password

Edited by strike

Share this post


Link to post
3 minutes ago, strike said:

I'm guessing misconfigured volume mappings. Please post your docker run command or screenshot of the template settings and a screenshot of the deluge download settings.

Forgive my ignorance, is the docker run command found in the logs for the docker?

Share this post


Link to post

Just make a change in the container template, change it back then hit apply. The docker run command will then pop up in a window. paste it here, but redact any username/password

Share this post


Link to post
1 minute ago, strike said:

Just make a change in the container template, change it back then hit apply. The docker run command will then pop up in a window. paste it here, but redact any username/password

Thanks!  Run command:

 

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'='REDACTED' -e 'VPN_PASS'='REDACTED' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DEBUG'='true' -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/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 

006a8d92a28b4bdbfdb873f5a604e8766389e1c2c953c2eda6aba34951e6b145

 

delugesettings.thumb.PNG.38992e017b349f32f887cea005c97ce6.PNGdelugedownloadsettings.PNG.c25438599cacb50caeb0fe8249a58475.PNG

Share this post


Link to post
7 hours ago, strike said:

Have you read my post further up? Link to it: https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=715291

Just ignore the first part regarding the password, that was for another user.

 

Thanks for the link, I think it got me looking in the right place.

 

I had to install PIA's client on my PC to find out what ports the server I'm connecting to supports. I found one that gives decent speeds on my PC.

 

What I'm not sure of is how to get Deluge's VPN to use that port. Also, testing on my PC I got way better performance with UDP instead of TCP, but I'm not sure how to make it use UDP. 

 

Just for some more info, I have a 1Gb connection. Sepeedtest on my PC with PIA I get 70Mb/8Mb.  

 

For whatever reason, even with 2 or 3 torrents going with multiple seeds on them, it seems like DelugeVPN is capped at 1..2Mb, I just can't seem to get faster than that.

 

 

Share this post


Link to post
10 minutes ago, jvorn said:

Thanks!  Run command:

 

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'='REDACTED' -e 'VPN_PASS'='REDACTED' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DEBUG'='true' -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/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 

006a8d92a28b4bdbfdb873f5a604e8766389e1c2c953c2eda6aba34951e6b145

 

delugesettings.thumb.PNG.38992e017b349f32f887cea005c97ce6.PNGdelugedownloadsettings.PNG.c25438599cacb50caeb0fe8249a58475.PNG

 

 

That looks good. Do you have a cache drive or are your downloads share on the array? If you have a cache drive I want you to try and change your /mnt/user/downloads to /mnt/cache/downloads and change your appdata to use cache instead of user also. Restart the conatiner after. If you still have issues please follow this procedure: https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

 

Share this post


Link to post
1 hour ago, jvorn said:

Hey all! Trying to get the DelugeVPN container to work.  Followed SpaceInvaderOne's tutorial but seem to have an issue with torrents not starting.  They get added but forever stay paused at 0%.

I am using PIA and input my user and pass into the config, changed STRICT_PORT_FORWARD and ENABLE_PRIVOXY to yes, selected a PIA Server that supports port forwarding (CA Toronto) and placed that ovpn file in the openvpn folder along with the 2 ca.rsa.2048 files.  Everything appears fine when it starts but when I add torrents they just stay paused at 0%.  Any thoughts? Thanks!

click on the container and goto console then run

curl ifconfig.co

That will show the ip inside the container. 

Then goto https://www.iplocation.net/

you will see your wan ip here (not through the vpn) they should be different

Then paste the ip from the curl command into the ip lookup page on the above location. It should report the location as CA Toronto.

If it doesnt maybe something wrong with your openvpn config files

Share this post


Link to post
7 minutes ago, shaunvis said:

Thanks for the link, I think it got me looking in the right place.

 

I had to install PIA's client on my PC to find out what ports the server I'm connecting to supports. I found one that gives decent speeds on my PC.

 

What I'm not sure of is how to get Deluge's VPN to use that port. Also, testing on my PC I got way better performance with UDP instead of TCP, but I'm not sure how to make it use UDP. 

 

Just for some more info, I have a 1Gb connection. Sepeedtest on my PC with PIA I get 70Mb/8Mb.  

 

For whatever reason, even with 2 or 3 torrents going with multiple seeds on them, it seems like DelugeVPN is capped at 1..2Mb, I just can't seem to get faster than that.

 

 

To change the connection port you have to replace .ovpn file with a different one that uses the port you want. Search PIA's website for it, I think the link is in this thread also.  The default port is 1198 UDP. But they have a link with alternative ports. Have you confirmed that you get an incoming port from the server? check the logs

Share this post


Link to post
24 minutes ago, SpaceInvaderOne said:

click on the container and goto console then run


curl ifconfig.co

That will show the ip inside the container. 

Then goto https://www.iplocation.net/

you will see your wan ip here (not through the vpn) they should be different

Then paste the ip from the curl command into the ip lookup page on the above location. It should report the location as CA Toronto.

If it doesnt maybe something wrong with your openvpn config files

Everything looks good here, IP is different and reporting Toronto.

Share this post


Link to post
50 minutes ago, strike said:

 

That looks good. Do you have a cache drive or are your downloads share on the array? If you have a cache drive I want you to try and change your /mnt/user/downloads to /mnt/cache/downloads and change your appdata to use cache instead of user also. Restart the conatiner after. If you still have issues please follow this procedure: https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

 

I do have a cache drive and did your change.  Nothing appeared to be different (torrents still stuck at paused).  Here is the log requested:

supervisord.log

Share this post


Link to post
19 minutes ago, jvorn said:

Everything looks good here, IP is different and reporting Toronto.

Can you check in deluge preferences/network that you dont have peer exchange or dht enabled

Share this post


Link to post
6 minutes ago, SpaceInvaderOne said:

Can you check in deluge preferences/network that you dont have peer exchange or dht enabled

I did have them both checked and unchecking and restarting the docker fixed it! Why do you think those settings were blocking things?

 

Thanks!!

Share this post


Link to post
2 minutes ago, jvorn said:

I did have them both checked and unchecking and restarting the docker fixed it! Why do you think those settings were blocking things?

 

Thanks!!

Ah glad that worked :)

Alot of private trackers don't allow these features as it allows connecting to clients which are not registered with the tracker. 

Share this post


Link to post
3 minutes ago, SpaceInvaderOne said:

Ah glad that worked :)

Alot of private trackers don't allow these features as it allows connecting to clients which are not registered with the tracker. 

Makes sense! I would have never thought to change those, I thought for sure it was a docker config issue since Im new at this... turns out I should have trusted myself more!

Edited by jvorn

Share this post


Link to post

I saw someone else mention windscribe in the last page. Did anyone get it to work? I can download, and it's from my windscribe static ip, verified on a private tracker, but can't seed or upload a linuxiso or on a private tracker. I just set two static ports to forward (35821 & 35822) from windscribe, and set these and incoming and outgoing ranges in deluge, and forwarded in my router to 58946 & 58846. Does this sound correct?

 

I've tested Privoxy and that seems to work as well.

Quote

 


ErrorWarningSystemArrayLogin


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

2019-01-31 00:42:40.789254 [info] System information Linux cf01771614fa 4.19.17-Unraid #1 SMP Thu Jan 24 13:07:56 PST 2019 x86_64 GNU/Linux
2019-01-31 00:42:40.814859 [info] PUID defined as '99'
2019-01-31 00:42:40.893813 [info] PGID defined as '100'
2019-01-31 00:42:41.021603 [info] UMASK defined as '000'
2019-01-31 00:42:41.044252 [info] Permissions already set for volume mappings
2019-01-31 00:42:41.069867 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2019-01-31 00:42:41.093260 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2019-01-31 00:42:41.117594 [info] VPN_ENABLED defined as 'yes'
2019-01-31 00:42:41.146052 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Windscribe-StaticIP.ovpn
dos2unix: converting file /config/openvpn/Windscribe-StaticIP.ovpn to Unix format...
2019-01-31 00:42:41.182681 [info] VPN remote line defined as 'remote STATICIPGOESHERE 443'
2019-01-31 00:42:41.206277 [info] VPN_REMOTE defined as '37.120.141.131'
2019-01-31 00:42:41.229520 [info] VPN_PORT defined as '443'
2019-01-31 00:42:41.255491 [info] VPN_PROTOCOL defined as 'udp'
2019-01-31 00:42:41.279158 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-01-31 00:42:41.300672 [info] VPN_PROV defined as 'custom'
2019-01-31 00:42:41.323298 [info] LAN_NETWORK defined as '192.168.1.0/24'
2019-01-31 00:42:41.346164 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4'
2019-01-31 00:42:41.369284 [info] VPN_USER defined as 'USERNAME'
2019-01-31 00:42:41.391785 [info] VPN_PASS defined as 'PASSWORD'
2019-01-31 00:42:41.414195 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-01-31 00:42:41.437094 [info] ENABLE_PRIVOXY defined as 'yes'
2019-01-31 00:42:41.461351 [info] Starting Supervisor...
2019-01-31 00:42:41,781 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-01-31 00:42:41,782 INFO Set uid to user 0 succeeded
2019-01-31 00:42:41,784 INFO supervisord started with pid 6
2019-01-31 00:42:42,786 INFO spawned: 'start-script' with pid 146
2019-01-31 00:42:42,787 INFO spawned: 'watchdog-script' with pid 147
2019-01-31 00:42:42,788 INFO spawned: 'privoxy-script' with pid 148
2019-01-31 00:42:42,788 INFO reaped unknown pid 7
2019-01-31 00:42:42,792 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-01-31 00:42:42,793 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-31 00:42:42,793 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-31 00:42:42,793 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-01-31 00:42:42,794 DEBG 'watchdog-script' stderr output:
dos2unix: converting file /config/core.conf to Unix format...

2019-01-31 00:42:42,799 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible

2019-01-31 00:42:42,845 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-01-31 00:42:42,848 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2019-01-31 00:42:42,852 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2019-01-31 00:42:42,854 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2019-01-31 00:42:42,857 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-01-31 00:42:42,860 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2019-01-31 00:42:42,863 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2019-01-31 00:42:42,866 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2019-01-31 00:42:42,869 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-01-31 00:42:42,871 DEBG 'start-script' stdout output:
37.120.141.131

2019-01-31 00:42:42,892 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2019-01-31 00:42:42,895 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2019-01-31 00:42:42,896 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-01-31 00:42:42,897 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.6
192.168.1.0/24 via 172.17.0.1 dev eth0

2019-01-31 00:42:42,897 DEBG 'start-script' stdout output:
--------------------

2019-01-31 00:42:42,899 DEBG 'start-script' stdout output:
iptable_mangle 16384 1
ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle

2019-01-31 00:42:42,900 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2019-01-31 00:42:42,938 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-01-31 00:42:42,939 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 udp -m udp --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.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.1.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 -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 udp -m udp --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.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.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

2019-01-31 00:42:42,940 DEBG 'start-script' stdout output:
--------------------

2019-01-31 00:42:42,940 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-01-31 00:42:42,958 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:42 2019 WARNING: file 'credentials.conf' is group or others accessible

Thu Jan 31 00:42:42 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Thu Jan 31 00:42:42 2019 library versions: OpenSSL 1.1.1a 20 Nov 2018, LZO 2.10

2019-01-31 00:42:42,959 DEBG 'start-script' stdout output:
[info] OpenVPN started

2019-01-31 00:42:42,959 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:42 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-01-31 00:42:42,959 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:42 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Jan 31 00:42:42 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Jan 31 00:42:42 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.141.131:443
Thu Jan 31 00:42:42 2019 UDP link local: (not bound)
Thu Jan 31 00:42:42 2019 UDP link remote: [AF_INET]37.120.141.131:443

2019-01-31 00:42:43,159 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:43 2019 VERIFY OK: depth=1, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Operations, CN=Windscribe Node CA
Thu Jan 31 00:42:43 2019 VERIFY KU OK
Thu Jan 31 00:42:43 2019 Validating certificate extended key usage
Thu Jan 31 00:42:43 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Thu Jan 31 00:42:43 2019 VERIFY EKU OK
Thu Jan 31 00:42:43 2019 VERIFY OK: depth=0, C=CA, ST=ON, O=Windscribe Limited, OU=Operations, CN=Windscribe Node Server 4096

2019-01-31 00:42:43,352 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:43 2019 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1602', remote='link-mtu 1550'

Thu Jan 31 00:42:43 2019 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher AES-256-GCM'

Thu Jan 31 00:42:43 2019 WARNING: 'auth' is used inconsistently, local='auth SHA512', remote='auth [null-digest]'


2019-01-31 00:42:43,352 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:43 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu Jan 31 00:42:43 2019 [Windscribe Node Server 4096] Peer Connection Initiated with [AF_INET]37.120.141.131:443

2019-01-31 00:42:49,937 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:49 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu Jan 31 00:42:49 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jan 31 00:42:49 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key

2019-01-31 00:42:49,938 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:49 2019 TUN/TAP device tun0 opened
Thu Jan 31 00:42:49 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Thu Jan 31 00:42:49 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-01-31 00:42:49,939 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:49 2019 /usr/bin/ip addr add dev tun0 10.117.206.3/23 broadcast 10.117.207.255

2019-01-31 00:42:49,940 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:49 2019 /root/openvpnup.sh tun0 1500 1553 10.117.206.3 255.255.254.0 init

2019-01-31 00:42:49,945 DEBG 'start-script' stdout output:
Thu Jan 31 00:42:49 2019 Initialization Sequence Completed

2019-01-31 00:42:49,998 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...

2019-01-31 00:42:49,998 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.117.206.3 different, marking for reconfigure

2019-01-31 00:42:50,001 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-01-31 00:42:50,004 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-01-31 00:42:50,011 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...

2019-01-31 00:42:50,013 DEBG 'privoxy-script' stderr output:
2019-01-31 00:42:50.012 1483cdfb6100 Info: Privoxy version 3.0.26

2019-01-31 00:42:50.012 1483cdfb6100 Info: Program name: /usr/bin/privoxy

2019-01-31 00:42:50,397 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address STATICIPGOESHERE

2019-01-31 00:42:50,409 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-01-31 00:42:50,554 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface currently defined as 0.0.0.0
[info] Deluge listening interface will be changed to 0.0.0.0
[info] Saving changes to Deluge config file /config/core.conf...

2019-01-31 00:42:50,714 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-01-31 00:42:51,394 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2019-01-31 00:42:51,394 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-01-31 00:42:51,394 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

 

Edited by Tritech

Share this post


Link to post
8 hours ago, Tritech said:

two static ports to forward (35821 & 35822) from windscribe, and set these and incoming and outgoing ranges in deluge, and forwarded in my router to 58946 & 58846. Does this sound correct?

 

no, firstly you shouldn't be setting an outgoing port, just leave it as automatic, for incoming port just specify a single port, so either of the two, and thirdly do not port forward on your router is it will do absolutely nothing, the port forward is for the vpn NOT your isp connection.

Share this post


Link to post
23 hours ago, strike said:

To change the connection port you have to replace .ovpn file with a different one that uses the port you want. Search PIA's website for it, I think the link is in this thread also.  The default port is 1198 UDP. But they have a link with alternative ports. Have you confirmed that you get an incoming port from the server? check the logs

I got it working faster, 5MB down. So that's probably closer to the limit of PIA's connection with a different config file. I'm sure I'm not going to be getting much better than that with a VPN.

 

Thanks for the help!

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.