Search the Community

Been wondering which is the best protocol to use, or maybe how to use Stealth VPN with TorGuard? Wonder no more! Check out this video I made!

So now that TorGuard offers an OpenConnect connection via SSL I would like to set this up in a jail. I have done this on a Raspberry Pi running Raspbian but cannot seem to get this to work on a FreeNAS jail. I am running 11.0 and have updated the packages in the jail. Here is the link to the guide for using OpeenConnect: https://torguard.net/forums/index.php?/topic/1065-howto-openconnect-on-linux-devices-like-raspberry-pi-openwrt-dd-wrt/ This the the error I am getting: POST https://107.181.189.38:22/ Attempting to connect to server 107.181.189.38:22 Connected to 107.181.189.38:22 SSL negotiation with 107.181.189.38 Server certificate verify failed: unable to get local issuer certificate Server SSL certificate didn't match: sha256:xxxxxxxxxxxxxxxxxx SSL connection failure 34415584520:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1264: Failed to open HTTPS connection to 107.181.189.38 Failed to obtain WebVPN cookie Any help or suggestions would be greatly appreciated!

Hello, I have decided to update my TorGuard clinent after some time to see what is new. When trying to use OpenConnect I get this weird error. It occurs when the client is trying to verify my IP and fails to do so. BUT! after a second the status is set to "verified" and everything seems to be ok (eg. status: N/A -> detecting ... -> my own IP and that message -> verified. Re-check is working without any further errors.). Also when checking for DNS leak it seems like it can't use VPN DNS (google and openDNS is working, is it even related or is it a feature of OpenConnect?). Failed to spawn script 'C:/Program Files (x86)/TorGuard/vpnc-script.js' for connect: Operation ended successfully //. that last part with "Operation..." is actually in my native windows language so it may slightly differ from the same message in english. I tried: - to turn off firewall and antivirus (Avast) - to reinstall TAP drivers - to reinstall Torguard - to reinstall Torguard and TAP drivers :-) ...without any success What may be cause of this error? It seems like the VPN itself is working but I don't feel like trusting it for now.

Requirements: openconnect vpnc vpnc-scripts Install requirements: Ubuntu/Raspbian # Update repository sudo apt-get update # Install openconnect and vpnc scripts sudo apt-get install openconnect vpnc-scripts -y Openwrt/Lede (current available openconnect does not work, you need to compile your own) # Update repository opkg update # Install openconnect and vpnc scripts opkg install openconnect vpnc-scripts Connect to VPN: Method 1 (password stored in a file) (password is stored in plain text) # Method 1 - Password stored in file sudo openconnect -u YourUsername --authgroup=DEFAULT -b --passwd-on-stdin --cafile=/home/pi/torguard/ca.crt --servercert=YourServerCert --pfs Server:Port </home/pi/torguard/userpass.txt Method 2 (pass password in command) (password is in plain text) # Method 2 - Pass password echo YourPass | sudo openconnect -u YourUsername --authgroup=DEFAULT -b --passwd-on-stdin --cafile=/home/pi/torguard/ca.crt --servercert=YourServerCert --pfs Server:Port My results with Raspberry Pi 3 Model B on factory system is 20/20Mb/s during Kodi was running full HD stream. With openconnect, RaspberryPi can be used as streaming service with high vpn encryption provided by TorGuard. Autostart - Method 1 There are plenty of vpnc scripts which can be used. In case of Raspberry Pi 3 Model B, it has onboard WLAN which does not perform very well, I don't get 20Mb/s with it. Connecting USB Wireless N did not solve the issue as it seems that RPi does not provide enough power to get more out of WLAN. For that reason I used external USB HUB with own power supply providing with power wireless or any other device, so that Raspberry itself has enough power. I ran into second problem. Without additional installation or manuall commands typing in terminal, you can't use second wlan that easy. Many suggest methods like to install some additional software for managing wireless, where I do not need onboard wireless at all to boot with the OS. But disabling it turns out often for newbies that they don't remember how to turn it on. That is the reason why I do suggest a very simple method for newbies, especially those who never did deal with this topics before. Using Raspeberry's LAN port is not a problem. I do get 90Mb/s, which is actually almost 100% what 100Mb/Lan card can offer. LAN is always preferable if possible. I will keep this example for the factory delivery of RPi and reffer to Raspberry Pi 3 Model B in this guide. Requirements: CA certificate from TorGuard. You can get it here. Save your password for VPN service into file in plain text, I will use this path in this guide /home/pi/torguard/onlypass-plain.txt Server's fingerprint (SHA1). (If you don't know how to find it, connect manually without and it will print sha1 fingerprint) (you can also always ask TorGuard support for assistance) XTERM xterm is not installed by default, you can install it with this command: sudo apt-get update; sudo apt-get install xterm -y Create a script to start openconnect in new terminal window Path in this guide: /home/pi/Desktop/tg.sh Example of tg.sh: sudo openconnect --verbose --pid-file=/var/run/openconnect.pid -u demouser --authgroup=DEFAULT -b --reconnect-timeout=200 --passwd-on-stdin --cafile=/home/pi/torguard/ca.crt --servercert=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF --pfs 1.2.3.4:22 </home/pi/torguard/onlypass-plain.txt Create a script for autostarting VPN connection on boot. Path in this guide: /home/pi/Desktop/autostart-openconnect-at-sharedip.sh Because we need separate terminal window where we always can see what is going on, we need to start VPN after desktop has been loaded. There are several ways to achive it, but one simple is xterm: sleep 20 sudo xterm -e "bash /home/pi/Desktop/tg.sh;bash" Xterm starts a new window running a script where new terminal window is not closed after sh command has been run, because if it closes, you closed your VPN connection. Here I use 20 seconds to wait until everything loads or vpn will fail to connect. It works also with 10 seconds, but I would not recommend lower value. For more advanced setups, please use vpnc scripts. Edit LXDE session start script for current user Path to start script: /home/pi/.config/lxsession/LXDE-pi/autostart Add command to run a a script autoconnecting to VPN, add to : /home/pi/.config/lxsession/LXDE-pi/autostart Here I do disable onboard wlan0 because I use USB device and if you don't do that, then VPN will connect over wlan0. sudo ifconfig wlan0 down # Disable onboard Wifi @sudo /home/pi/Desktop/autostart-openconnect-at-sharedip.sh # Connect correctly over wlan1 (Here we have second time sudo, but it will not harm anything, it will only ensure, that if you forget sudo in your tg.sh, then autostart will still work) (You need to have root privileges to be able to access vpns folder) Reboot I hope it helps some newbies to get started with this amazing VPN service. On factory RPi and openconnect, I get 30Mb on download constantly which is great result and is enough for almost anything, including streaming in HD. Those who have/need faster connections, they will need to buy better device. But all in all, you can use RPi as Media Center together with IPTV behind TorGuards VPN and it is working very well, everything works very stable. This is much better replacement for any smart tv around and costs barely € 35. I think there is no cheaper device performing better for this price. If you know any, please show me the results, I would love to test them. Once again, TorGuard, thank you very much for such a great service!

OpenConnect Client Guide For Windows: For Android: Usefull Links/Guides: INFO: Please login to your account to find actuall server list and choose your server. All openvpn/l2tp/pptp hostnames work with anyconnect on port 22. Anyconnect hostnames use port 443.