Leaderboard

Release torguard-v3.99.3, 2020-07-09 ==================================== - All platforms: Fix a potential crash upon disconnect when ShadowSock is used. - All platforms: new option "Refresh server list" in "Settings->General" - Windows: Fix TAP driver installation from TorGuard Client * Next release will be the WireGuard release, its 90% done. Downloads

Hello everyone, We seem to be receiving more and more questions about WireGuard recently due to the extreme difference in speeds over other protocols, our developers are working hard on integrating into our Desktop apps at first and then mobile apps thereafter - our WireGuard integration will support Dedicated IP's, Port forwards, Streaming/Residential IP's and support ALL locations. We know everyone is hoping for a design update, there will be some small changes soon but not drastic, we really don't want to change things drastically, our functionality and app flow/security is more important, the app flow will change but again not drastically, remember it's not about how one looks, it's what's inside 😉 Best Regards TorGuard

No serious issues, just server side niggles with our implementation, we are working on that now, it takes a wee bit when there are thousands of servers. We won’t be too long before we send out some Beta's. Regards

We are well aware guys and we resolve these issues with our implementation - this is part of the reason things are a little delayed but just to let you know: 1) All servers now support WireGuard but only from the TG client implementation - so the whole network is now ready. 2) We have WireGuard running inside TG just fine, we are just working out some small issues as we need to have it working with all the features we provide including dedicated IP's. 3) Its very fast indeed! Regards

I 100% agree, my bad 😕

Yes, this is possible!

Do you have Server IP lookup under settings set to Direct IP?

On the sales page:https://torguard.net/anonymoustorrentvpn.php, Torguard states that "x8 Simultaneous Connections". It means you should be able to use the VPN service on 8 devices at the same time.

Here is an alternate method using network manager instead. This will bypass the need for openresolv using wg-quick. This also assumes you named your torguard wireguard config file wg0.conf and already have placed it in /etc/wireguard. Adjust accordingly for your needs. Network manager method only works natively in the command line so far. Third party gui functionality exists but is not officially supported yet. First we need to import the existing config to network manager. If you already restricted access to the wg0.conf file then you'll need to do this using sudo. $ CONF_FILE="/etc/wireguard/wg0.conf" $ nmcli connection import type wireguard file "$CONF_FILE" Connection 'wg0' (xxxxxxxxx) successfully added. As a side note if you import the config from a non restricted file all the restrictions are changed automatically so there is no need to do a sudo chmod 600 command afterwards once the config is imported into a new profile in the /etc/NetworkManager/system-connections/ folder If you want to remove the config $ nmcli connection delete wg0 or $ nmcli c delete wg0 Connection 'wg0' (xxxxxxxxxxx) successfully deleted. To see the details of the config $ nmcli --show-secrets connection show wg0 or $ nmcli --show-secrets c s wg0 To activate the connection $ nmcli connection up wg0 or $ nmcli c u wg0 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) To make the connection permanent if it wasn't done so by default, this is how to set up autoconnect through the command line First assuming we didn't know what the profile name was for the config use the following command $ nmcli connection show or $ nmcli c s Next to edit the profile use the following command, this will open nmcli editor $ nmcli connection edit wg0 or $ nmcli c e wg0 Now we can check individual settings, in this case autoconnect nmcli> print connection.autoconnect If it brings back the following value, this is how to set it so it will autoconnect every time we start up the computer nmcli> print connection.autoconnect connection.autoconnect: no nmcli> set connection.autoconnect yes nmcli> save persistent Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection. Do you still want to save? (yes/no) The connection will now autoconnect on computer restarts once enabled using the nmcli connection up command To deactivate the connection $ nmcli connection down wg0 or $ nmcli c d wg0 Connection successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30)

It will indeed yes.

We will place a notification in your client area once we have them available. Regards

We hope a beta will be out this week - we have hit some bumps but getting there. I promise we will