Desktop client v1.7.0 is now available
The beta period for v1.7.0 provided us with some additional insights as to areas to improve, which have now been done. This version is a major improvement compared to v1.6.1.
List of changes in v1.7.0
- Bug fix: DNS leak test is quicker and more reliable (additionally improved after beta)
- Bug fix: recognize .cc email addresses as valid when sending support messages
- Bug fix: properly handle special characters in passwords for Ubuntu (resolved after beta)
- Bug fix: display proper error message when max allowed devices has been reached
- Bug fix: improve font color on macOS when dark mode is enabled (resolved after beta)
- Bug fix: change directory for temporary OpenVPN file creations on Windows, which should resolve issues some Windows users had (resolved after beta)
- Improvement: choosing the best server automatically has been improved (resolved after beta)
- Improvement: clarify a few log entries (resolved after beta)
- Improvement: migrated from QtWebEngine to QML
- Improvement: VPN server load is re-fetched every 30 minutes when not connected to a VPN server
- Improvement: renamed Account to Settings in the menu
- Improvement: client is considerably more responsive and requires less resources to run
- Improvement: updated to Qt 5.12.6 for macOS & Linux
How can I update the desktop client?
- Launch client
- You will now see a notification pop up asking you if you wish to update to version 1.7.0
- Wait for the installation to finish and enter your password if asked for it
- As soon as the installation finishes the new version will launch automatically.
- Enjoy your privacy!
If for some reason the online update fails
If something goes wrong, simply close the desktop client and install it manually.
The download links for each operating system can be found below.
Some Windows users are experiencing issues with the killswitch, which causes random disconnects. We've been working and researching this issue and it'll be fixed in v1.8.0. The next version will also contain several other improvements related to the killswitch, across all operating systems.
We've also discussed internally in the team and have decided to remove DNScrypt from our desktop client. We'll still run the DNScrypt servers in our infrastructure for now since it's used by people.
Our reasoning to remove DNScrypt is that it doesn't provide enough additional value for our users - since the VPN connection encrypts the traffic anyway. Furthermore, it causes delays in DNS responses as all DNS requests are sent to Sweden when DNScrypt is enabled - regardless of where the user is located.