February 26, 201511 yr I have TorGuard, can it work with UNRAID? Also is there a way to let Plex through but everything else goes through VPN?
February 26, 201511 yr I was also looking to use the unRaid 6 but its a normal tendency to people to think Beta stuff is far more 'broken' then the normal, which is what kept me from using it. I have still not moved my data to my server, so i might give unRaid 6 a try. thanks for the advice.
February 27, 201511 yr The betas are fairly established now and seem to be working steadily towards RC status and hopefully final release. You are in the enviable position of having a new setup and if I remember correctly you haven't migrated data across yet, so you can set it all up and test before data migration. If it was beta 1 I probably would recommend sticking to a stable release especially as Limetech development isn't generally that quick. But as we're now at 14b a lot (but not all) of bugs have been documented and either fixed or are being looked at.
February 27, 201511 yr I have TorGuard, can it work with UNRAID? Also is there a way to let Plex through but everything else goes through VPN? I'm still researching how this can be accomplished using OpenVPN on unRAID although some people have had success using their routers (i assume wifi routers) with tomato firmware, and not using OpenVPN on unRAID. See here: http://serverfault.com/questions/382498/howto-only-tunnel-specific-hosts-route-through-openvpn-client-on-tomato Also I found an interesting post on the unRAID forums but it is for Transmission (and I don't know if it works well with Transmission as I don't use it), although there could be a possibility to develop something like but it would take a lot of work I'm sure. I believe the method it is intended for bypassing all traffic including plugins when using OpenVPN on unRAID and directing only specific plugin traffic such as Transmission, but it may require a lot more than just a few changes to settings, and I wouldn't recommend do anything like this since it requires changes to unRAID kernel iptables etc. unless someone very capable is going to take it on as a project. It is worth taking a look however. My use of something like this would be to just route one or two plugins via OpenVPN and the rest of the traffic routed out of the tunnel. See here: http://lime-technology.com/forum/index.php?topic=33118.0 I would be more than happy to donate to anyone who can come up with a successful solution to either of these methods.
February 27, 201511 yr I installed OPENVPN but when i go to setting and click OPENVPN, the page is blank. anyone know why? I created a folder called "openvpn" and pasted config files from Torguard: Telnet'ed in and installed the plugin, this is what's inside the folder after installation. SETTING page is showing blank.
February 27, 201511 yr The betas are fairly established now and seem to be working steadily towards RC status and hopefully final release. You are in the enviable position of having a new setup and if I remember correctly you haven't migrated data across yet, so you can set it all up and test before data migration. If it was beta 1 I probably would recommend sticking to a stable release especially as Limetech development isn't generally that quick. But as we're now at 14b a lot (but not all) of bugs have been documented and either fixed or are being looked at. Allright, i'll give unRaid 6 a try tonite and see how the plugins etc work on them. If it does seem like a good option and better then unRaid 5 i'll stick with it.
March 1, 201511 yr I have TorGuard, can it work with UNRAID? Also is there a way to let Plex through but everything else goes through VPN? Im using TORGuard with no problems. Follow setup instructions.
March 28, 201511 yr i've just installed this and think i've followed the instructions correctly but can't get it working im running unraid 5.0.5 It is installed and 'running' and i can see the settings page. When i go into it there is no way for me to select the ovpn connection to use (cert and ovpn files have been copied to /boot/openvpn). When i enter the settings page i get lots of errors on the console ie "tun0: error fetching interface information: device not found" "cat: /sys/class/net/tun0/statistics/rxbytes: No such file or directory" I have updated to the latest version. (OpenVPN Plugin Version 2.7.28 2.7.28 OpenVPN Software Build OpenVPN 2.3.2 2.3.6) Any ideas?
April 9, 201511 yr Just installed this on v6.0-beta14b, but it's giving me the following error in the logs Options error: You must define TUN/TAP device (--dev) Use --help for more information. About to dig in deeper and figure it out, but at the very least I would have expected this to be something the plugin install should have setup?
April 9, 201511 yr I've just had a fun time trying to setup PIA with OPENVPN Client. Firstly, the download link in the first post of the thread is outdated. By a lot (Version 2.7.4). I managed to track down the GITHUB page and download the latest version from 3 months ago. https://github.com/petersm1/OpenVPN-Client I then had to update the file with the latest OPENSSL links as the J version was outdated and updated to K. I've included this as an attachment and changed the version info to 2.7.29. Then I tried to setup the script but was having issues there because I had changed the port from 9091 to 8084 in transmission. Then found that PIA uses TUN5 not TUN0. So, for those having issues, here's the updated SCRIPT for PIA users. #!/bin/bash ifconfig tun5|grep -oE "inet addr: *10\.[0-9]+\.[0-9]+\.[0-9]+"|tr -d "a-z :"|tee /tmp/vpn_ip curl -d "user=USERNAME_HERE&pass=PASSWORD_HERE&client_id=$(cat /boot/config/plugins/openvpn/.pia_client_id)&local_ip=$(cat /tmp/vpn_ip)" https://www.privateinternetaccess.com/vpninfo/port_forward_assignment 2>/dev/null|grep -oE "[0-9]+"|tee /tmp/vpn_port_opened awk '{print "/usr/bin/transmission-remote --port "$0;}' /tmp/vpn_port_opened |bash ps -ef |grep "transmission-daemon -i" |grep -v grep > /tmp/vpn_ps VPNPS=$(awk '{print $10;}' /tmp/vpn_ps) VPNIP=$(cat /tmp/vpn_ip) if [[ $VPNPS != $VPNIP ]] ; then kill $(awk '{print $2;}' /tmp/vpn_ps) awk '{print "/usr/bin/transmission-daemon -i "$0;}' /tmp/vpn_ip |bash fi P.S. I also updated TRANSMISSION to PHAZE version as I was still using UNPLUGGED version I ran the script through telnet and everything worked corectly Just thought I would share my experience as it took me 2 hours and some to get it working properly. openvpn_client.plg
April 20, 201511 yr EDIT: I ended up upgrading to version 6 beta 15. Result: Everything is awesome. I'll leave the rest of my post here so others can use my mistakes as a lesson in what not to do. END EDIT I've just had a fun time trying to setup PIA with OPENVPN Client. Firstly, the download link in the first post of the thread is outdated. By a lot (Version 2.7.4). I managed to track down the GITHUB page and download the latest version from 3 months ago. https://github.com/petersm1/OpenVPN-Client I then had to update the file with the latest OPENSSL links as the J version was outdated and updated to K. I've included this as an attachment and changed the version info to 2.7.29. Then I tried to setup the script but was having issues there because I had changed the port from 9091 to 8084 in transmission. Then found that PIA uses TUN5 not TUN0. So, for those having issues, here's the updated SCRIPT for PIA users. #!/bin/bash ifconfig tun5|grep -oE "inet addr: *10\.[0-9]+\.[0-9]+\.[0-9]+"|tr -d "a-z :"|tee /tmp/vpn_ip curl -d "user=USERNAME_HERE&pass=PASSWORD_HERE&client_id=$(cat /boot/config/plugins/openvpn/.pia_client_id)&local_ip=$(cat /tmp/vpn_ip)" https://www.privateinternetaccess.com/vpninfo/port_forward_assignment 2>/dev/null|grep -oE "[0-9]+"|tee /tmp/vpn_port_opened awk '{print "/usr/bin/transmission-remote --port "$0;}' /tmp/vpn_port_opened |bash ps -ef |grep "transmission-daemon -i" |grep -v grep > /tmp/vpn_ps VPNPS=$(awk '{print $10;}' /tmp/vpn_ps) VPNIP=$(cat /tmp/vpn_ip) if [[ $VPNPS != $VPNIP ]] ; then kill $(awk '{print $2;}' /tmp/vpn_ps) awk '{print "/usr/bin/transmission-daemon -i "$0;}' /tmp/vpn_ip |bash fi P.S. I also updated TRANSMISSION to PHAZE version as I was still using UNPLUGGED version I ran the script through telnet and everything worked corectly Just thought I would share my experience as it took me 2 hours and some to get it working properly. I just downloaded and installed your plugin on my Unraid 5.0.5. I got this error message when I started openvpn: Options error: No client-side authentication method is specified. You must use either --cert/--key, --pkcs12, or --auth-user-pass Use --help for more information. I followed the instructions from the first post of this thread here when installing your version of the openvpn plugin. I am unsure about how "the script" you ran through telnet fits in with peter_sm's initial instructions. I assume I update the script with my own PIA username and password . Do i execute it before or after i install the openvpn plugin? Does it matter? the loglines that appears when I click the "start" button in openvpn plugin gui is like this: /etc/rc.d/rc.openvpn start Updating the ovpn file... The ovpn file was updated with --> /boot/config/plugins/openvpn/password.txt The ovpn file was updated with --> status /tmp/openvpn/openvpn-status.log Changing to the folder where the openvpn config files belong /boot/openvpn Starting Openvpn Tunnel: Please Wait... Not connected! tun5 not established!!! OK... Started By thew way, in the openvpn client web ui page (in the "Updates" section) I have this: "Update Plugin - An update is available" What am i missing? From what I can tell I've got three potential sources of error: - I don't have a tun5 network interface - I don't have client-side authentication method specified in the openvpn start script (/etc/rc.d/rc.openvpn ?) - I am using an out-dated plugin? Cheers, Jaso
May 2, 201511 yr Edit: I fixed the script! Just minor changes. I agonized over this for 12 hours! The following does not work on Unraid 6. "inet addr:" ifconfig tun5|grep -oE "net addr: [/b]*10\.[0-9]+\.[0-9]+\.[0-9]+"|tr -d "a-z :"|tee /tmp/vpn_ip it needs to be: just "inet" ifconfig tun5|grep -oE "inet *10\.[0-9]+\.[0-9]+\.[0-9]+"|tr -d "a-z :"|tee /tmp/vpn_ip Yes, that was what I agonized over....script worked fine in Unraid 5. old post: ---------------------------------------------------------------- I am just clueless as to why the port open script no longer works for me. I really need that functionality back. it worked before I updated to Unraid 6. #!/bin/bash ifconfig tun5|grep -oE "inet addr: *10\.[0-9]+\.[0-9]+\.[0-9]+"|tr -d "a-z :"|tee /tmp/vpn_ip curl -d "user=*******&pass=*********&client_id=$(cat /mnt/cache/.custom/openvpn/.pia_client_id)&local_ip=$(cat /tmp/vpn_ip)" https://www.privateinternetaccess.com/vpninfo/port_forward_assignment 2>/dev/null|grep -oE "[0-9]+"|tee /tmp/vpn_port_opened awk '{print "/usr/local/Transmission/usr/bin/transmission-remote --port "$0;}' /tmp/vpn_port_opened |bash Like I said, this worked before upgrading to Unraid 6. What could have possibly changed? In the meantime, this command works: The command returns a port number when I do curl -d "user=*****&pass=******&client_id=$(cat /mnt/cache/.custom/openvpn/.pia_client_id)&local_ip=*****" https://www.privateinternetaccess.com/vpninfo/port_forward_assignment
May 4, 201511 yr Remove your VPN authentication details in the post. Edit: I fixed the script! Just minor changes. I agonized over this for 12 hours! The following does not work on Unraid 6. "inet addr:" ifconfig tun5|grep -oE "net addr: [/b]*10\.[0-9]+\.[0-9]+\.[0-9]+"|tr -d "a-z :"|tee /tmp/vpn_ip it needs to be: just "inet" ifconfig tun5|grep -oE "inet *10\.[0-9]+\.[0-9]+\.[0-9]+"|tr -d "a-z :"|tee /tmp/vpn_ip Yes, that was what I agonized over....script worked fine in Unraid 5. old post: ---------------------------------------------------------------- I am just clueless as to why the port open script no longer works for me. I really need that functionality back. it worked before I updated to Unraid 6. #!/bin/bash ifconfig tun5|grep -oE "inet addr: *10\.[0-9]+\.[0-9]+\.[0-9]+"|tr -d "a-z :"|tee /tmp/vpn_ip curl -d "user=p2964796&pass=532yRf1vSaQ2&client_id=$(cat /mnt/cache/.custom/openvpn/.pia_client_id)&local_ip=$(cat /tmp/vpn_ip)" https://www.privateinternetaccess.com/vpninfo/port_forward_assignment 2>/dev/null|grep -oE "[0-9]+"|tee /tmp/vpn_port_opened awk '{print "/usr/local/Transmission/usr/bin/transmission-remote --port "$0;}' /tmp/vpn_port_opened |bash Like I said, this worked before upgrading to Unraid 6. What could have possibly changed? In the meantime, this command works: The command returns a port number when I do curl -d "user=*****&pass=******&client_id=$(cat /mnt/cache/.custom/openvpn/.pia_client_id)&local_ip=*****" https://www.privateinternetaccess.com/vpninfo/port_forward_assignment
May 17, 201511 yr Hi @peter_sm with rc1 when im using Openvpn client with array start, becuase of some issue - docker dont start anymore this is from docker log time="2015-05-17T01:28:46+01:00" level=info msg="+job init_networkdriver()" time="2015-05-17T01:28:46+01:00" level=info msg="+job serveapi(unix:///var/run/docker.sock)" time="2015-05-17T01:28:46+01:00" level=info msg="Listening for HTTP on unix (/var/run/docker.sock)" Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' time="2015-05-17T01:28:46+01:00" level=info msg="-job init_networkdriver() = ERR (1)" time="2015-05-17T01:28:46+01:00" level=fatal msg="Shutting down daemon due to errors: Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0'" when you first start Docker after that Openvpn client - everything working fine.
June 7, 201511 yr Hi @peter_sm with rc1 when im using Openvpn client with array start, becuase of some issue - docker dont start anymore this is from docker log time="2015-05-17T01:28:46+01:00" level=info msg="+job init_networkdriver()" time="2015-05-17T01:28:46+01:00" level=info msg="+job serveapi(unix:///var/run/docker.sock)" time="2015-05-17T01:28:46+01:00" level=info msg="Listening for HTTP on unix (/var/run/docker.sock)" Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0' time="2015-05-17T01:28:46+01:00" level=info msg="-job init_networkdriver() = ERR (1)" time="2015-05-17T01:28:46+01:00" level=fatal msg="Shutting down daemon due to errors: Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0'" when you first start Docker after that Openvpn client - everything working fine. I can also confirm that this happens using rc4. As piotrasd mentioned, the workaround is to set "Start OpenVPN during array mounting" to "No". The docker tab will then appear again as usual and OpenVPN can be started manually without effecting docker.
August 4, 201510 yr FYI for others interested in running the OpenVPN Client and Plex Media Server accessible remotely. In the end I could not get this to work. Even adding a list of usenet servers to the text file and using the option to only route VPN to those servers, I still lost my remote access to Plex whenever the VPN was running. So, I ended up simply adding the crontab entries in the initial post. Now my server is a Plex server by day and secured usenet client by night. One change to the crontab script, the correct command refers to rc.openvpnclient: #Start openvpn at 11 pm every day crontab -l > /tmp/file; echo '#Start openvpn at 11 pm every day' >> /tmp/file; echo '00 23 * * * /etc/rc.d/rc.openvpnclient start >/dev/null 2>&1' >>/tmp/file; crontab /tmp/file; rm /tmp/file #Stop openvpn at 7 am every day crontab -l > /tmp/file; echo '#Stop openvpn at 7 am every day' >> /tmp/file; echo '00 7 * * * /etc/rc.d/rc.openvpnclient stop >/dev/null 2>&1' >>/tmp/file; crontab /tmp/file; rm /tmp/file Obviously this is more of a workaround than a solution, but it works for me just fine. Of course, if anyone is able to get the VPN client to work with Plex, I'd be interested in the solution!
August 21, 201510 yr I had the same issue of Plex among other things becoming unreachable after starting the openvpn client. In my case I have chosen to only route specific IP's through the VPN Client, however my solution may apply to other scenarios as well. The issue is that there is a default route put in place when the tunnel comes up which will route anything not matched in the routing table through the VPN Here are snippets of my routing table before and after I start the VPN Client: Before: root@Unraid:/# ip route default via 10.33.0.1 dev br0 metric 1 10.3.0.0/24 dev br0 proto kernel scope link src 10.3.0.33 10.9.0.0/24 dev tun0 proto kernel scope link src 10.9.0.1 127.0.0.0/8 dev lo scope link 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 After: root@Unraid:/# ip route default dev tun5 scope link default via 10.33.0.1 dev br0 metric 1 8.8.8.8 dev tun5 scope link 10.3.0.0/24 dev br0 proto kernel scope link src 10.3.0.33 10.9.0.0/24 dev tun0 proto kernel scope link src 10.9.0.1 10.157.1.1 via 10.157.1.5 dev tun5 10.157.1.5 dev tun5 proto kernel scope link src 10.157.1. So even though I specified that I only want the specified IP's to go through the tunnel, anything that is not matched in the routing table is still going to be sent out the default route on the tun5 interface (my vpn client interface). Thus, anything plex related would be going through the tunnel. I am able to resolve the issue by simply removing the default route and any IP's that I want going through the VPN still will (ex 8.8.8. root@Unraid:/# ip route delete default dev tun5 root@Unraid:/# traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8, 30 hops max, 60 byte packets 1 10.157.1.1 (10.157.1.1) 88.139 ms 105.143 ms 105.357 ms (<------ this is my first hop VPN tunnel interface) You would either need to write a script to remove the route or perform it manually every time you start the client or Peter needs to change the logic in his pliugin.
August 21, 201510 yr I had the same issue of Plex among other things becoming unreachable after starting the openvpn client. In my case I have chosen to only route specific IP's through the VPN Client, however my solution may apply to other scenarios as well. The issue is that there is a default route put in place when the tunnel comes up which will route anything not matched in the routing table through the VPN Here are snippets of my routing table before and after I start the VPN Client: Before: root@Unraid:/# ip route default via 10.33.0.1 dev br0 metric 1 10.3.0.0/24 dev br0 proto kernel scope link src 10.3.0.33 10.9.0.0/24 dev tun0 proto kernel scope link src 10.9.0.1 127.0.0.0/8 dev lo scope link 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 After: root@Unraid:/# ip route default dev tun5 scope link default via 10.33.0.1 dev br0 metric 1 8.8.8.8 dev tun5 scope link 10.3.0.0/24 dev br0 proto kernel scope link src 10.3.0.33 10.9.0.0/24 dev tun0 proto kernel scope link src 10.9.0.1 10.157.1.1 via 10.157.1.5 dev tun5 10.157.1.5 dev tun5 proto kernel scope link src 10.157.1. So even though I specified that I only want the specified IP's to go through the tunnel, anything that is not matched in the routing table is still going to be sent out the default route on the tun5 interface (my vpn client interface). Thus, anything plex related would be going through the tunnel. I am able to resolve the issue by simply removing the default route and any IP's that I want going through the VPN still will (ex 8.8.8. root@Unraid:/# ip route delete default dev tun5 root@Unraid:/# traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8, 30 hops max, 60 byte packets 1 10.157.1.1 (10.157.1.1) 88.139 ms 105.143 ms 105.357 ms (<------ this is my first hop VPN tunnel interface) You would either need to write a script to remove the route or perform it manually every time you start the client or Peter needs to change the logic in his pliugin. Wow, this is very helpful, thank you! It explains why I was unable to get Plex to work remotely even when I specified IPs. For now I'll leave my schedule in place, but if the client is able to be updated to have the IP list work as expected, that would be great! I'd really like to get the crontab entries out of my "go" script.
August 25, 201510 yr Hi All - am running openvpnclient 2015.8.4 on Unraid Server Plus 6.0.1. Have a 2 part question that stem from an issue I have that I've had for ages - even while running unraid v5.x. In short, my openvpn connection would periodically disconnect but not always successfully reconnect leaving the interfaces in limbo - 'route' would show the normal routes that would appear while connected, yet I'm unable to ping out to the internet. Trying to access the openvpn settings page on the web gui would just hang. The only fix was to kill the openvpn process via a telnet session, then restart it via the web gui. This issue was so annoying that until now I've been running a script via a cron job every 5 minutes that would check for an external connection using wget then if unsuccessful it would run /etc/rc.d/rc.openvpn restart. Having recently updated the server to v6.0.1 and using the new plugin v2015.8.4, I cant find /etc/rc.d/rc.openvpn or rc.openvpnclient or anything similar, so... (1) how does one stop/start/restart the openvpn client via the commandline in the latest version? and (2) does anyone have any ideas on how to keep the openvpn connection alive and healthy without it hanging so often and locking up the settings page? Here are some logs, config file and system info that may be useful: -plugin openvpnclient 2015.8.4 -system Info: Unraid Server Plus 6.0.1; M/B: ASRock - B75 Pro3-M; CPU: Intel® Celeron® CPU G1610 @ 2.60GHz; Memory: 4096 MB; Network: eth0: 100Mb/s - Full Duplex; Kernel: Linux 4.0.4-unRAID x86_64; OpenSSL: 1.0.1o A recent openvpn log: (I've replaced some IP's with <localIP> and <remoteIP> for privacy/security). ====== Tue Aug 25 05:24:00 2015 OpenVPN 2.3.6 x86_64-slackware-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 10 2014 Tue Aug 25 05:24:00 2015 library versions: OpenSSL 1.0.1o 12 Jun 2015, LZO 2.03 Tue Aug 25 05:24:00 2015 WARNING: file '/boot/config/plugins/openvpnclient/password.txt' is group or others accessible Tue Aug 25 05:24:00 2015 UDPv4 link local: [undef] Tue Aug 25 05:24:00 2015 UDPv4 link remote: [AF_INET]46.166.188.211:1194 Tue Aug 25 05:24:01 2015 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Tue Aug 25 05:24:07 2015 [Private Internet Access] Peer Connection Initiated with [AF_INET]46.166.188.211:1194 Tue Aug 25 05:24:09 2015 TUN/TAP device tun5 opened Tue Aug 25 05:24:09 2015 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Tue Aug 25 05:24:09 2015 /usr/sbin/ip link set dev tun5 up mtu 1500 Tue Aug 25 05:24:09 2015 /usr/sbin/ip addr add dev tun5 local <localIP> peer <localIP> Tue Aug 25 05:24:09 2015 Initialization Sequence Completed Tue Aug 25 07:00:29 2015 [Private Internet Access] Inactivity timeout (--ping-restart), restarting Tue Aug 25 07:00:29 2015 SIGUSR1[soft,ping-restart] received, process restarting Tue Aug 25 07:00:51 2015 RESOLVE: Cannot resolve host address: nl.privateinternetaccess.com: Name or service not known Tue Aug 25 07:01:12 2015 RESOLVE: Cannot resolve host address: nl.privateinternetaccess.com: Name or service not known Tue Aug 25 07:01:37 2015 RESOLVE: Cannot resolve host address: nl.privateinternetaccess.com: Name or service not known Tue Aug 25 07:02:03 2015 RESOLVE: Cannot resolve host address: nl.privateinternetaccess.com: Name or service not known Tue Aug 25 07:02:08 2015 UDPv4 link local: [undef] Tue Aug 25 07:02:08 2015 UDPv4 link remote: [AF_INET]109.201.154.204:1194 Tue Aug 25 07:03:08 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue Aug 25 07:03:08 2015 TLS Error: TLS handshake failed Tue Aug 25 07:03:08 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 25 07:03:10 2015 UDPv4 link local: [undef] Tue Aug 25 07:03:10 2015 UDPv4 link remote: [AF_INET]109.201.154.204:1194 Tue Aug 25 07:04:10 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue Aug 25 07:04:10 2015 TLS Error: TLS handshake failed Tue Aug 25 07:04:10 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 25 07:04:12 2015 UDPv4 link local: [undef] Tue Aug 25 07:04:12 2015 UDPv4 link remote: [AF_INET]109.201.154.204:1194 Tue Aug 25 07:05:12 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue Aug 25 07:05:12 2015 TLS Error: TLS handshake failed Tue Aug 25 07:05:12 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 25 07:05:14 2015 UDPv4 link local: [undef] Tue Aug 25 07:05:14 2015 UDPv4 link remote: [AF_INET]109.201.154.204:1194 Tue Aug 25 07:06:14 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue Aug 25 07:06:14 2015 TLS Error: TLS handshake failed Tue Aug 25 07:06:14 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 25 07:06:16 2015 UDPv4 link local: [undef] Tue Aug 25 07:06:16 2015 UDPv4 link remote: [AF_INET]109.201.154.204:1194 Tue Aug 25 07:07:16 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue Aug 25 07:07:16 2015 TLS Error: TLS handshake failed Tue Aug 25 07:07:16 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 25 07:07:19 2015 UDPv4 link local: [undef] Tue Aug 25 07:07:19 2015 UDPv4 link remote: [AF_INET]109.201.154.183:1194 Tue Aug 25 07:08:19 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue Aug 25 07:08:19 2015 TLS Error: TLS handshake failed Tue Aug 25 07:08:19 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 25 07:08:21 2015 UDPv4 link local: [undef] Tue Aug 25 07:08:21 2015 UDPv4 link remote: [AF_INET]109.201.154.183:1194 Tue Aug 25 07:09:21 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) . . . This cycle contines every 1 minute for the next 10 hours... . . . Tue Aug 25 17:48:32 2015 TLS Error: TLS handshake failed Tue Aug 25 17:48:32 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 25 17:48:34 2015 UDPv4 link local: [undef] Tue Aug 25 17:48:34 2015 UDPv4 link remote: [AF_INET]109.201.154.203:1194 Tue Aug 25 17:49:34 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue Aug 25 17:49:34 2015 TLS Error: TLS handshake failed Tue Aug 25 17:49:34 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 25 17:49:36 2015 UDPv4 link local: [undef] Tue Aug 25 17:49:36 2015 UDPv4 link remote: [AF_INET]<remote IP>:1194 Tue Aug 25 17:49:42 2015 [Private Internet Access] Peer Connection Initiated with [AF_INET]46.166.188.211:1194 Tue Aug 25 17:49:45 2015 Preserving previous TUN/TAP instance: tun5 Tue Aug 25 17:49:45 2015 NOTE: Pulled options changed on restart, will need to close and reopen TUN/TAP device. Tue Aug 25 17:49:45 2015 /usr/sbin/ip addr del dev tun5 local <localIP> peer <localIP> Tue Aug 25 17:49:46 2015 TUN/TAP device tun5 opened Tue Aug 25 17:49:46 2015 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Tue Aug 25 17:49:46 2015 /usr/sbin/ip link set dev tun5 up mtu 1500 Tue Aug 25 17:49:46 2015 /usr/sbin/ip addr add dev tun5 local <localIP> peer <localIP> Tue Aug 25 17:49:46 2015 Initialization Sequence Completed my vpn config file (private internet access) ====== client proto udp dev tun5 remote nl.privateinternetaccess.com 1194 resolv-retry infinite nobind persist-key persist-tun ca ca.crt tls-client remote-cert-tls server comp-lzo verb 1 reneg-sec 0 crl-verify crl.pem auth-user-pass /boot/config/plugins/openvpnclient/password.txt status /tmp/openvpn/openvpn-status.log Thanks in advance!
August 30, 201510 yr I'm getting this error when installing the latest plg on unraid 5.0.5: root@Tower:/boot/config/plugins# installplg openvpn_client.plg installing plugin: openvpn_client file /boot/packages/openssl-1.0.1j-i486-1.txz: downloading from ftp://ftp.sunet.se/pub/os/Linux/distributions/slackware//slackware-current/slackware/n/openssl-1.0.1j-i486-1.txz ... No such file `openssl-1.0.1j-i486-1.txz'. bad download, deleting
August 31, 201510 yr Author It looks like they have made a new version of this packages , plugin needs to be updated. Why not try Unraid6 instead ;-)
September 19, 201510 yr hmmmmm.....been putting off buying new hardware and upgrading to v6 for some time...
September 19, 201510 yr Looks like the plg needs openssl-solibs-1.0.1c-i486-3.txz url updated: http://slackware.cs.utah.edu/pub/slackware/slackware-14.0/slackware/a/openssl-solibs-1.0.1c-i486-3.txz
Archived
This topic is now archived and is closed to further replies.