Are the permissions correct here? spe/spe ?

 

Also I think strong certs use a different port then 1198,  no?

 

That was it!  Working fine now.  Do you think I'm ok to copy all other config data over from my previous docker other than my ovpn directory?

Only one way to find out, just make a back up copy first!

Only one way to find out, just make a back up copy first!

 

Annnnnnnd I'm golden .  Thanks guys for talking me through this one it was really beginning to become an annoyance haha.

Ya PIA really threw a lot of folks a curve ball when they changed ports, added stronger certs etc. Just growing pains.

I hope this hasn't been answered a million times already, but apparently the incoming port for Deluge is blocked by default (or at least it is if one uses a custom VPN, like I am). Is there a work-around for this that anyone has discovered? I've been digging through the config to try to make heads or tails of how I might make the appropriate changes to iptables myself but I'm a total novice.

You're talking about the incoming port that other peers connect to right? The only "work-around" there is is to use a vpn servcie that allows port forwarding, forward a port and use that port in deluge. Check with your vpn provider if they support it and how to set it up.

You're talking about the incoming port that other peers connect to right? The only "work-around" there is is to use a vpn servcie that allows port forwarding, forward a port and use that port in deluge. Check with your vpn provider if they support it and how to set it up.

 

Most VPN providers do not support incoming ports, known good providers that do are PIA and AirVPN, there most probably are others, but these two are known to be pretty solid.

Thanks for the response, I'll check with my provider. I had previously asked them if they restrict any ports, but I can see now that they may have assumed I meant outbound ports. I take it that no additional configuration is needed if my provider isn't restricting incoming ports, other than making sure the Deluge incoming port matches whatever port/port range my provider supports?

 

Thanks!

Thanks for the response, I'll check with my provider. I had previously asked them if they restrict any ports, but I can see now that they may have assumed I meant outbound ports. I take it that no additional configuration is needed if my provider isn't restricting incoming ports, other than making sure the Deluge incoming port matches whatever port/port range my provider supports?

 

Thanks!

Exactly

 

Sent from my SM-G900F using Tapatalk

 

 

Hello,

 

After the upgrade to unraid 6.2 it had me update my Docker image. Now the OpenVPN part of the Docker seems to be failing to start. I've included the logs below.

 

[info] Starting OpenVPN...

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 OpenVPN 2.3.11 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on May 12 2016

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 library versions: OpenSSL 1.0.2h 3 May 2016, LZO 2.09

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 WARNING: file 'credentials.conf' is group or others accessible

 

2016-09-16 02:21:13,753 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 UDPv4 link local: [undef]

 

2016-09-16 02:21:13,753 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 UDPv4 link remote: [AF_INET]46.166.188.240:1194

 

2016-09-16 02:21:14,146 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:14 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected]

 

2016-09-16 02:21:14,146 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:14 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed

Fri Sep 16 02:21:14 2016 TLS_ERROR: BIO read tls_read_plaintext error

Fri Sep 16 02:21:14 2016 TLS Error: TLS object -> incoming plaintext read error

Fri Sep 16 02:21:14 2016 TLS Error: TLS handshake failed

Fri Sep 16 02:21:14 2016 SIGUSR1[soft,tls-error] received, process restarting

Hello,

 

After the upgrade to unraid 6.2 it had me update my Docker image. Now the OpenVPN part of the Docker seems to be failing to start. I've included the logs below.

 

[info] Starting OpenVPN...

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 OpenVPN 2.3.11 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on May 12 2016

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 library versions: OpenSSL 1.0.2h 3 May 2016, LZO 2.09

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 WARNING: file 'credentials.conf' is group or others accessible

 

2016-09-16 02:21:13,753 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 UDPv4 link local: [undef]

 

2016-09-16 02:21:13,753 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 UDPv4 link remote: [AF_INET]46.166.188.240:1194

 

2016-09-16 02:21:14,146 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:14 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected]

 

2016-09-16 02:21:14,146 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:14 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed

Fri Sep 16 02:21:14 2016 TLS_ERROR: BIO read tls_read_plaintext error

Fri Sep 16 02:21:14 2016 TLS Error: TLS object -> incoming plaintext read error

Fri Sep 16 02:21:14 2016 TLS Error: TLS handshake failed

Fri Sep 16 02:21:14 2016 SIGUSR1[soft,tls-error] received, process restarting

Wrong port, change 1194 to 1198

 

Sent from my SM-G900F using Tapatalk

 

 

 

Q5. I can't seem to access the webui from outside my LAN, why is this?

 

A5. DelugeVPN uses iptables in order to secure against ip leakage of your real ip address, this requires all modules loading at the kernel level for iptables, including the iptable_mangle module. If the iptable_mangle module is not loaded/available on your hosts kernel then you will not be able to access the webui outside of your LAN. Until recently unRAID DID include iptable_mangle support, but the latest release (6.1. has removed this, with the exception that if you are running a KVM VM then this forces the inclusion of iptable_mangle support. So the options are downgrade to unraid 6.1.7 or less, or create a KVM VM and start it and then restart the docker container, or run this container on another host that does have iptable_mangle support.

 

If you want to help out with the above issue then please consider contacting jonp/tom regards this issue, the more people that mention it, the more chance we have of getting this added back in for the next release.

 

I'm in my first couple of days of using unRAID and so far so good.  This has got me stumped though.  My server is running headless - what's the best way to connect to configure DelugeVPN?  I've tried RDP but it won't connect.

 

Thanks in advance

 

Q5. I can't seem to access the webui from outside my LAN, why is this?

 

A5. DelugeVPN uses iptables in order to secure against ip leakage of your real ip address, this requires all modules loading at the kernel level for iptables, including the iptable_mangle module. If the iptable_mangle module is not loaded/available on your hosts kernel then you will not be able to access the webui outside of your LAN. Until recently unRAID DID include iptable_mangle support, but the latest release (6.1. has removed this, with the exception that if you are running a KVM VM then this forces the inclusion of iptable_mangle support. So the options are downgrade to unraid 6.1.7 or less, or create a KVM VM and start it and then restart the docker container, or run this container on another host that does have iptable_mangle support.

 

If you want to help out with the above issue then please consider contacting jonp/tom regards this issue, the more people that mention it, the more chance we have of getting this added back in for the next release.

 

I'm in my first couple of days of using unRAID and so far so good.  This has got me stumped though.  My server is running headless - what's the best way to connect to configure DelugeVPN?  I've tried RDP but it won't connect.

 

Thanks in advance

 

ok so you wont have any sort of rdp access unless your running a windows vm (which unraid can do via kvm). deluge is a web based application, so you can connect to it via a web browser on another machine inside your LAN, if you want to access the web interface over the internet then unfortunately this involves a small frig to get this to work (due to a bug in unraid), basically you need to enable vm's (not create one), this then allows you to access deluge webui externally (port forward required on your router to allow this).

 

Q5. I can't seem to access the webui from outside my LAN, why is this?

 

A5. DelugeVPN uses iptables in order to secure against ip leakage of your real ip address, this requires all modules loading at the kernel level for iptables, including the iptable_mangle module. If the iptable_mangle module is not loaded/available on your hosts kernel then you will not be able to access the webui outside of your LAN. Until recently unRAID DID include iptable_mangle support, but the latest release (6.1. has removed this, with the exception that if you are running a KVM VM then this forces the inclusion of iptable_mangle support. So the options are downgrade to unraid 6.1.7 or less, or create a KVM VM and start it and then restart the docker container, or run this container on another host that does have iptable_mangle support.

 

If you want to help out with the above issue then please consider contacting jonp/tom regards this issue, the more people that mention it, the more chance we have of getting this added back in for the next release.

 

I'm in my first couple of days of using unRAID and so far so good.  This has got me stumped though.  My server is running headless - what's the best way to connect to configure DelugeVPN?  I've tried RDP but it won't connect.

 

Thanks in advance

 

ok so you wont have any sort of rdp access unless your running a windows vm (which unraid can do via kvm). deluge is a web based application, so you can connect to it via a web browser on another machine inside your LAN, if you want to access the web interface over the internet then unfortunately this involves a small frig to get this to work (due to a bug in unraid), basically you need to enable vm's (not create one), this then allows you to access deluge webui externally (port forward required on your router to allow this).

 

Hmm I'm not sure what I'm doing wrong.  I've setup your sabnzbd, sonarr and non-vpn deluge (although what's the default password?) so I can't work out why I can't see the WebUI on delugeVPN:

 

 

VPN_USER - I'm using PIA and I've tried my main username/password and the PPTP/L2TP/SOCKS one given in the dashboard

VPN_PASS - Ditto

ENABLE_PRIVOXY - yes

LAN_NETWORK - My subnet mask is 255.255.255.0 and my unRAID IP is 192.168.1.218 and my router is 192.168.1.254 and I've tried 192.168.1.218/24 192.168.1.0/24 and 192.168.1.254/24

 

Update:

 

192.168.1.0/24 and turning off the VPN_ENABLED allows me to connect to the WebUI, but no joy with it on.  I'm wondering if it's the way I've got my home network setup?  My unraid server is connected via a wired connection to a wireless media bridge.  Found 'deluge' default password on web ;-)

 

 

Q5. I can't seem to access the webui from outside my LAN, why is this?

 

A5. DelugeVPN uses iptables in order to secure against ip leakage of your real ip address, this requires all modules loading at the kernel level for iptables, including the iptable_mangle module. If the iptable_mangle module is not loaded/available on your hosts kernel then you will not be able to access the webui outside of your LAN. Until recently unRAID DID include iptable_mangle support, but the latest release (6.1. has removed this, with the exception that if you are running a KVM VM then this forces the inclusion of iptable_mangle support. So the options are downgrade to unraid 6.1.7 or less, or create a KVM VM and start it and then restart the docker container, or run this container on another host that does have iptable_mangle support.

 

If you want to help out with the above issue then please consider contacting jonp/tom regards this issue, the more people that mention it, the more chance we have of getting this added back in for the next release.

 

I'm in my first couple of days of using unRAID and so far so good.  This has got me stumped though.  My server is running headless - what's the best way to connect to configure DelugeVPN?  I've tried RDP but it won't connect.

 

Thanks in advance

 

ok so you wont have any sort of rdp access unless your running a windows vm (which unraid can do via kvm). deluge is a web based application, so you can connect to it via a web browser on another machine inside your LAN, if you want to access the web interface over the internet then unfortunately this involves a small frig to get this to work (due to a bug in unraid), basically you need to enable vm's (not create one), this then allows you to access deluge webui externally (port forward required on your router to allow this).

 

Hmm I'm not sure what I'm doing wrong.  I've setup your sabnzbd, sonarr and non-vpn deluge (although what's the default password?) so I can't work out why I can't see the WebUI on delugeVPN:

 

 

VPN_USER - I'm using PIA and I've tried my main username/password and the PPTP/L2TP/SOCKS one given in the dashboard

VPN_PASS - Ditto

ENABLE_PRIVOXY - yes

LAN_NETWORK - My subnet mask is 255.255.255.0 and my unRAID IP is 192.168.1.218 and my router is 192.168.1.254 and I've tried 192.168.1.218/24 192.168.1.0/24 and 192.168.1.254/24

 

Update:

 

192.168.1.0/24 and turning off the VPN_ENABLED allows me to connect to the WebUI, but no joy with it on.  I'm wondering if it's the way I've got my home network setup?  My unraid server is connected via a wired connection to a wireless media bridge.  Found 'deluge' default password on web ;-)

 

attach the supervisord.log file (found on the host mapping for /config)

Hello,

 

After the upgrade to unraid 6.2 it had me update my Docker image. Now the OpenVPN part of the Docker seems to be failing to start. I've included the logs below.

 

[info] Starting OpenVPN...

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 OpenVPN 2.3.11 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on May 12 2016

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 library versions: OpenSSL 1.0.2h 3 May 2016, LZO 2.09

 

2016-09-16 02:21:13,719 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 WARNING: file 'credentials.conf' is group or others accessible

 

2016-09-16 02:21:13,753 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 UDPv4 link local: [undef]

 

2016-09-16 02:21:13,753 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:13 2016 UDPv4 link remote: [AF_INET]46.166.188.240:1194

 

2016-09-16 02:21:14,146 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:14 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected]

 

2016-09-16 02:21:14,146 DEBG 'start-script' stdout output:

Fri Sep 16 02:21:14 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed

Fri Sep 16 02:21:14 2016 TLS_ERROR: BIO read tls_read_plaintext error

Fri Sep 16 02:21:14 2016 TLS Error: TLS object -> incoming plaintext read error

Fri Sep 16 02:21:14 2016 TLS Error: TLS handshake failed

Fri Sep 16 02:21:14 2016 SIGUSR1[soft,tls-error] received, process restarting

Wrong port, change 1194 to 1198

 

Sent from my SM-G900F using Tapatalk

 

Not sure how that happened but that was it. Thanks!

I just updated to 6.2 and noticed a new update for this docker after doing so.

 

I updated and now it won't run.  I validated that my VPN settings having changed and match what they should.  Here is the log file:

 

2016-09-16 14:29:47,729 DEBG 'deluge-script' stdout output:

[info] deluge config file already exists, skipping copy

 

2016-09-16 14:29:47,730 DEBG 'deluge-script' stdout output:

[info] VPN is enabled, checking VPN tunnel local ip is valid

 

2016-09-16 14:29:47,738 DEBG 'start-script' stdout output:

[info] VPN provider defined as custom

[info] VPN config file (ovpn extension) is located at /config/openvpn/dal-a01.ovpn

 

2016-09-16 14:29:47,741 DEBG 'start-script' stdout output:

[info] VPN provider remote gateway defined as dal-a01.wlvpn.com

[info] VPN provider remote port defined as 1194

[crit] VPN provider remote protocol not defined (via -e VPN_PROTOCOL), exiting...

 

 

anyone know what the -e VPN_PROTOCOL is?  This seems to be a new thing.

 

thanks

david

I just updated to 6.2 and noticed a new update for this docker after doing so.

 

I updated and now it won't run.  I validated that my VPN settings having changed and match what they should.  Here is the log file:

 

2016-09-16 14:29:47,729 DEBG 'deluge-script' stdout output:

[info] deluge config file already exists, skipping copy

 

2016-09-16 14:29:47,730 DEBG 'deluge-script' stdout output:

[info] VPN is enabled, checking VPN tunnel local ip is valid

 

2016-09-16 14:29:47,738 DEBG 'start-script' stdout output:

[info] VPN provider defined as custom

[info] VPN config file (ovpn extension) is located at /config/openvpn/dal-a01.ovpn

 

2016-09-16 14:29:47,741 DEBG 'start-script' stdout output:

[info] VPN provider remote gateway defined as dal-a01.wlvpn.com

[info] VPN provider remote port defined as 1194

[crit] VPN provider remote protocol not defined (via -e VPN_PROTOCOL), exiting...

 

 

anyone know what the -e VPN_PROTOCOL is?  This seems to be a new thing.

 

thanks

david

 

open your ovpn file, the vpn_protocol is the protocol defined via the "proto" or at the end of the remote line, should be either tcp or udp, also whilst your there check the port, as its most probably not 1194 (old default pia port).

Here is my .ovpn file. From usenetserver, it hasn't changed:

 

client

dev tun

proto udp

remote dal-a01.wlvpn.com 1194

resolv-retry infinite

nobind

persist-key

persist-remote-ip

ca dal-a01.cert

tls-client

remote-cert-tls server

auth-user-pass credentials.conf

comp-lzo

verb 3

auth SHA256

cipher AES-256-CBC

 

 

EDIT: I check file permissions.  It is owned by root root, with 644 permissions so that shouldn't be an issue.

 

david

 

I just updated to 6.2 and noticed a new update for this docker after doing so.

 

I updated and now it won't run.  I validated that my VPN settings having changed and match what they should.  Here is the log file:

 

2016-09-16 14:29:47,729 DEBG 'deluge-script' stdout output:

[info] deluge config file already exists, skipping copy

 

2016-09-16 14:29:47,730 DEBG 'deluge-script' stdout output:

[info] VPN is enabled, checking VPN tunnel local ip is valid

 

2016-09-16 14:29:47,738 DEBG 'start-script' stdout output:

[info] VPN provider defined as custom

[info] VPN config file (ovpn extension) is located at /config/openvpn/dal-a01.ovpn

 

2016-09-16 14:29:47,741 DEBG 'start-script' stdout output:

[info] VPN provider remote gateway defined as dal-a01.wlvpn.com

[info] VPN provider remote port defined as 1194

[crit] VPN provider remote protocol not defined (via -e VPN_PROTOCOL), exiting...

 

 

anyone know what the -e VPN_PROTOCOL is?  This seems to be a new thing.

 

thanks

david

 

open your ovpn file, the vpn_protocol is the protocol defined via the "proto" or at the end of the remote line, should be either tcp or udp, also whilst your there check the port, as its most probably not 1194 (old default pia port).

Here is my .ovpn file. From usenetserver, it hasn't changed:

 

client

dev tun

proto udp

remote dal-a01.wlvpn.com 1194

resolv-retry infinite

nobind

persist-key

persist-remote-ip

ca dal-a01.cert

tls-client

remote-cert-tls server

auth-user-pass credentials.conf

comp-lzo

verb 3

auth SHA256

cipher AES-256-CBC

 

 

EDIT: I check file permissions.  It is owned by root root, with 644 permissions so that shouldn't be an issue.

 

david

 

I just updated to 6.2 and noticed a new update for this docker after doing so.

 

I updated and now it won't run.  I validated that my VPN settings having changed and match what they should.  Here is the log file:

 

2016-09-16 14:29:47,729 DEBG 'deluge-script' stdout output:

[info] deluge config file already exists, skipping copy

 

2016-09-16 14:29:47,730 DEBG 'deluge-script' stdout output:

[info] VPN is enabled, checking VPN tunnel local ip is valid

 

2016-09-16 14:29:47,738 DEBG 'start-script' stdout output:

[info] VPN provider defined as custom

[info] VPN config file (ovpn extension) is located at /config/openvpn/dal-a01.ovpn

 

2016-09-16 14:29:47,741 DEBG 'start-script' stdout output:

[info] VPN provider remote gateway defined as dal-a01.wlvpn.com

[info] VPN provider remote port defined as 1194

[crit] VPN provider remote protocol not defined (via -e VPN_PROTOCOL), exiting...

 

 

anyone know what the -e VPN_PROTOCOL is?  This seems to be a new thing.

 

thanks

david

 

open your ovpn file, the vpn_protocol is the protocol defined via the "proto" or at the end of the remote line, should be either tcp or udp, also whilst your there check the port, as its most probably not 1194 (old default pia port).

 

i know it hasnt changed but you haven't actually defined the settings before as they weren't mandatory (fallback to reading ovpn if env vars not specified), they now are mandatory, so you need to specify the following:-

 

VPN_REMOTE

VPN_PROTOCOL

VPN_PORT

 

values for you looking at your ovpn file are:-

 

VPN_REMOTE = dal-a01.wlvpn.com

VPN_PROTOCOL = udp

VPN_PORT = 1194

 

 

Q5. I can't seem to access the webui from outside my LAN, why is this?

 

A5. DelugeVPN uses iptables in order to secure against ip leakage of your real ip address, this requires all modules loading at the kernel level for iptables, including the iptable_mangle module. If the iptable_mangle module is not loaded/available on your hosts kernel then you will not be able to access the webui outside of your LAN. Until recently unRAID DID include iptable_mangle support, but the latest release (6.1. has removed this, with the exception that if you are running a KVM VM then this forces the inclusion of iptable_mangle support. So the options are downgrade to unraid 6.1.7 or less, or create a KVM VM and start it and then restart the docker container, or run this container on another host that does have iptable_mangle support.

 

If you want to help out with the above issue then please consider contacting jonp/tom regards this issue, the more people that mention it, the more chance we have of getting this added back in for the next release.

 

I'm in my first couple of days of using unRAID and so far so good.  This has got me stumped though.  My server is running headless - what's the best way to connect to configure DelugeVPN?  I've tried RDP but it won't connect.

 

Thanks in advance

 

ok so you wont have any sort of rdp access unless your running a windows vm (which unraid can do via kvm). deluge is a web based application, so you can connect to it via a web browser on another machine inside your LAN, if you want to access the web interface over the internet then unfortunately this involves a small frig to get this to work (due to a bug in unraid), basically you need to enable vm's (not create one), this then allows you to access deluge webui externally (port forward required on your router to allow this).

 

Hmm I'm not sure what I'm doing wrong.  I've setup your sabnzbd, sonarr and non-vpn deluge (although what's the default password?) so I can't work out why I can't see the WebUI on delugeVPN:

 

 

VPN_USER - I'm using PIA and I've tried my main username/password and the PPTP/L2TP/SOCKS one given in the dashboard

VPN_PASS - Ditto

ENABLE_PRIVOXY - yes

LAN_NETWORK - My subnet mask is 255.255.255.0 and my unRAID IP is 192.168.1.218 and my router is 192.168.1.254 and I've tried 192.168.1.218/24 192.168.1.0/24 and 192.168.1.254/24

 

Update:

 

192.168.1.0/24 and turning off the VPN_ENABLED allows me to connect to the WebUI, but no joy with it on.  I'm wondering if it's the way I've got my home network setup?  My unraid server is connected via a wired connection to a wireless media bridge.  Found 'deluge' default password on web ;-)

 

attach the supervisord.log file (found on the host mapping for /config)

 

Thanks for trying to help.

 

ok there is a warning regards your PIA password, it looks like it contains characters which might cause problems, i would advise changing the password to use A-Z and/or 0-9 characters only, so no symbols.

 

[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

 

if you change it make sure to change it in docker, then stop the container, delete the supervisord.log file, makesure vpn is set to enabled and try running again, if its still no go then post the new supervisord.log file (minus username and password).

I added VPN_PROTOCOL upd and that worked.

 

I looked at the settings and didn't see the VPN_PROTOCOL, I didn't realize I needed to add it manually to the setup.

 

Up and running again.

 

thanks!

david

 

Here is my .ovpn file. From usenetserver, it hasn't changed:

 

client

dev tun

proto udp

remote dal-a01.wlvpn.com 1194

resolv-retry infinite

nobind

persist-key

persist-remote-ip

ca dal-a01.cert

tls-client

remote-cert-tls server

auth-user-pass credentials.conf

comp-lzo

verb 3

auth SHA256

cipher AES-256-CBC

 

 

EDIT: I check file permissions.  It is owned by root root, with 644 permissions so that shouldn't be an issue.

 

david

 

I just updated to 6.2 and noticed a new update for this docker after doing so.

 

I updated and now it won't run.  I validated that my VPN settings having changed and match what they should.  Here is the log file:

 

2016-09-16 14:29:47,729 DEBG 'deluge-script' stdout output:

[info] deluge config file already exists, skipping copy

 

2016-09-16 14:29:47,730 DEBG 'deluge-script' stdout output:

[info] VPN is enabled, checking VPN tunnel local ip is valid

 

2016-09-16 14:29:47,738 DEBG 'start-script' stdout output:

[info] VPN provider defined as custom

[info] VPN config file (ovpn extension) is located at /config/openvpn/dal-a01.ovpn

 

2016-09-16 14:29:47,741 DEBG 'start-script' stdout output:

[info] VPN provider remote gateway defined as dal-a01.wlvpn.com

[info] VPN provider remote port defined as 1194

[crit] VPN provider remote protocol not defined (via -e VPN_PROTOCOL), exiting...

 

 

anyone know what the -e VPN_PROTOCOL is?  This seems to be a new thing.

 

thanks

david

 

open your ovpn file, the vpn_protocol is the protocol defined via the "proto" or at the end of the remote line, should be either tcp or udp, also whilst your there check the port, as its most probably not 1194 (old default pia port).

 

i know it hasnt changed but you haven't actually defined the settings before as they weren't mandatory (fallback to reading ovpn if env vars not specified), they now are mandatory, so you need to specify the following:-

 

VPN_REMOTE

VPN_PROTOCOL

VPN_PORT

 

values for you looking at your ovpn file are:-

 

VPN_REMOTE = dal-a01.wlvpn.com

VPN_PROTOCOL = udp

VPN_PORT = 1194

I added VPN_PROTOCOL upd and that worked.

 

I looked at the settings and didn't see the VPN_PROTOCOL, I didn't realize I needed to add it manually to the setup.

 

Up and running again.

 

thanks!

david

 

Here is my .ovpn file. From usenetserver, it hasn't changed:

 

client

dev tun

proto udp

remote dal-a01.wlvpn.com 1194

resolv-retry infinite

nobind

persist-key

persist-remote-ip

ca dal-a01.cert

tls-client

remote-cert-tls server

auth-user-pass credentials.conf

comp-lzo

verb 3

auth SHA256

cipher AES-256-CBC

 

 

EDIT: I check file permissions.  It is owned by root root, with 644 permissions so that shouldn't be an issue.

 

david

 

I just updated to 6.2 and noticed a new update for this docker after doing so.

 

I updated and now it won't run.  I validated that my VPN settings having changed and match what they should.  Here is the log file:

 

2016-09-16 14:29:47,729 DEBG 'deluge-script' stdout output:

[info] deluge config file already exists, skipping copy

 

2016-09-16 14:29:47,730 DEBG 'deluge-script' stdout output:

[info] VPN is enabled, checking VPN tunnel local ip is valid

 

2016-09-16 14:29:47,738 DEBG 'start-script' stdout output:

[info] VPN provider defined as custom

[info] VPN config file (ovpn extension) is located at /config/openvpn/dal-a01.ovpn

 

2016-09-16 14:29:47,741 DEBG 'start-script' stdout output:

[info] VPN provider remote gateway defined as dal-a01.wlvpn.com

[info] VPN provider remote port defined as 1194

[crit] VPN provider remote protocol not defined (via -e VPN_PROTOCOL), exiting...

 

 

anyone know what the -e VPN_PROTOCOL is?  This seems to be a new thing.

 

thanks

david

 

open your ovpn file, the vpn_protocol is the protocol defined via the "proto" or at the end of the remote line, should be either tcp or udp, also whilst your there check the port, as its most probably not 1194 (old default pia port).

 

i know it hasnt changed but you haven't actually defined the settings before as they weren't mandatory (fallback to reading ovpn if env vars not specified), they now are mandatory, so you need to specify the following:-

 

VPN_REMOTE

VPN_PROTOCOL

VPN_PORT

 

values for you looking at your ovpn file are:-

 

VPN_REMOTE = dal-a01.wlvpn.com

VPN_PROTOCOL = udp

VPN_PORT = 1194

 

ahh fair enough, thats one of the issues with unraid, any changes in the template do not get pushed out to users, that particular env var has actually been present for months, glad its all working, enjoy!.

 

Q5. I can't seem to access the webui from outside my LAN, why is this?

 

A5. DelugeVPN uses iptables in order to secure against ip leakage of your real ip address, this requires all modules loading at the kernel level for iptables, including the iptable_mangle module. If the iptable_mangle module is not loaded/available on your hosts kernel then you will not be able to access the webui outside of your LAN. Until recently unRAID DID include iptable_mangle support, but the latest release (6.1. has removed this, with the exception that if you are running a KVM VM then this forces the inclusion of iptable_mangle support. So the options are downgrade to unraid 6.1.7 or less, or create a KVM VM and start it and then restart the docker container, or run this container on another host that does have iptable_mangle support.

 

If you want to help out with the above issue then please consider contacting jonp/tom regards this issue, the more people that mention it, the more chance we have of getting this added back in for the next release.

 

I'm in my first couple of days of using unRAID and so far so good.  This has got me stumped though.  My server is running headless - what's the best way to connect to configure DelugeVPN?  I've tried RDP but it won't connect.

 

Thanks in advance

 

ok so you wont have any sort of rdp access unless your running a windows vm (which unraid can do via kvm). deluge is a web based application, so you can connect to it via a web browser on another machine inside your LAN, if you want to access the web interface over the internet then unfortunately this involves a small frig to get this to work (due to a bug in unraid), basically you need to enable vm's (not create one), this then allows you to access deluge webui externally (port forward required on your router to allow this).

 

Hmm I'm not sure what I'm doing wrong.  I've setup your sabnzbd, sonarr and non-vpn deluge (although what's the default password?) so I can't work out why I can't see the WebUI on delugeVPN:

 

 

VPN_USER - I'm using PIA and I've tried my main username/password and the PPTP/L2TP/SOCKS one given in the dashboard

VPN_PASS - Ditto

ENABLE_PRIVOXY - yes

LAN_NETWORK - My subnet mask is 255.255.255.0 and my unRAID IP is 192.168.1.218 and my router is 192.168.1.254 and I've tried 192.168.1.218/24 192.168.1.0/24 and 192.168.1.254/24

 

Update:

 

192.168.1.0/24 and turning off the VPN_ENABLED allows me to connect to the WebUI, but no joy with it on.  I'm wondering if it's the way I've got my home network setup?  My unraid server is connected via a wired connection to a wireless media bridge.  Found 'deluge' default password on web ;-)

 

attach the supervisord.log file (found on the host mapping for /config)

 

Thanks for trying to help.

 

ok there is a warning regards your PIA password, it looks like it contains characters which might cause problems, i would advise changing the password to use A-Z and/or 0-9 characters only, so no symbols.

 

[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

 

if you change it make sure to change it in docker, then stop the container, delete the supervisord.log file, makesure vpn is set to enabled and try running again, if its still no go then post the new supervisord.log file (minus username and password).

 

changed funky lastpass password - still no joy

supervisord.txt

 

Q5. I can't seem to access the webui from outside my LAN, why is this?

 

A5. DelugeVPN uses iptables in order to secure against ip leakage of your real ip address, this requires all modules loading at the kernel level for iptables, including the iptable_mangle module. If the iptable_mangle module is not loaded/available on your hosts kernel then you will not be able to access the webui outside of your LAN. Until recently unRAID DID include iptable_mangle support, but the latest release (6.1. has removed this, with the exception that if you are running a KVM VM then this forces the inclusion of iptable_mangle support. So the options are downgrade to unraid 6.1.7 or less, or create a KVM VM and start it and then restart the docker container, or run this container on another host that does have iptable_mangle support.

 

If you want to help out with the above issue then please consider contacting jonp/tom regards this issue, the more people that mention it, the more chance we have of getting this added back in for the next release.

 

I'm in my first couple of days of using unRAID and so far so good.  This has got me stumped though.  My server is running headless - what's the best way to connect to configure DelugeVPN?  I've tried RDP but it won't connect.

 

Thanks in advance

 

ok so you wont have any sort of rdp access unless your running a windows vm (which unraid can do via kvm). deluge is a web based application, so you can connect to it via a web browser on another machine inside your LAN, if you want to access the web interface over the internet then unfortunately this involves a small frig to get this to work (due to a bug in unraid), basically you need to enable vm's (not create one), this then allows you to access deluge webui externally (port forward required on your router to allow this).

 

Hmm I'm not sure what I'm doing wrong.  I've setup your sabnzbd, sonarr and non-vpn deluge (although what's the default password?) so I can't work out why I can't see the WebUI on delugeVPN:

 

 

VPN_USER - I'm using PIA and I've tried my main username/password and the PPTP/L2TP/SOCKS one given in the dashboard

VPN_PASS - Ditto

ENABLE_PRIVOXY - yes

LAN_NETWORK - My subnet mask is 255.255.255.0 and my unRAID IP is 192.168.1.218 and my router is 192.168.1.254 and I've tried 192.168.1.218/24 192.168.1.0/24 and 192.168.1.254/24

 

Update:

 

192.168.1.0/24 and turning off the VPN_ENABLED allows me to connect to the WebUI, but no joy with it on.  I'm wondering if it's the way I've got my home network setup?  My unraid server is connected via a wired connection to a wireless media bridge.  Found 'deluge' default password on web ;-)

 

attach the supervisord.log file (found on the host mapping for /config)

 

Thanks for trying to help.

 

ok there is a warning regards your PIA password, it looks like it contains characters which might cause problems, i would advise changing the password to use A-Z and/or 0-9 characters only, so no symbols.

 

[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

 

if you change it make sure to change it in docker, then stop the container, delete the supervisord.log file, makesure vpn is set to enabled and try running again, if its still no go then post the new supervisord.log file (minus username and password).

 

changed funky lastpass password - still no joy

Can you just double check that log, I don't think the one you posted is complete or maybe it hadn't finished when you copied it

 

Sent from my SM-G900F using Tapatalk