Desktop applications release [v59rc1]
The v59 beta test is over, and the final version is now available on our website. We thank everyone for their participation and inputs. We look forward to adding more functionality, stability with greater speed and transparency for the coming releases. You can find the release here
Today we are launching a new beta version of the Private Internet Access desktop application. This new version features a major overhaul of the internals of the application, with many new features and improvements.
- Switched from Titanium to node-webkit for GUI engine.
- New desktop notifications to see when you're connected and disconnected.
- Significant reduction in disk usage, and improved app performance.
The PIA desktop app makes it easy to connect to our service, but also handles configuring your OS settings to further protect your privacy online. The existing client is built on top of Titanium Desktop, a framework to build desktop applications with web technologies. Titanium is no longer maintained and proved to be a barrier for us by slowing down new feature development while hampering the performance of the application, most notably by increasing disk usage.
We made the decision to replace Titanium with node-webkit, another similar framework but with vastly improved capabilities, stability and a healthy, active community. This required a significant portion of the application being re-written while preserving the same experience our users were used to.
We are happy to announce that the transition is now complete and the new version is now available. Due to the significant number of changes we are releasing a beta version which is available for anyone to use and provide feedback.
Even though this is a beta version, we have taken measures to ensure the privacy protection functionality is robust and has been thoroughly checked and verified. You can always verify that your privacy filters are active by visitinghttps://www.privateinternetaccess.com/pages/whats-my-ip/
HOW TO PARTICIPATE IN THE BETA PROGRAM:
- Download the new version from the links at the bottom of this post.
- Ensure the older version of PIA is disconnected and closed.
- Run the installer
- Connect using the new version
- If possible, please send a debug log, by pressing <Control+L>.
- If possible, include a screenshot, and any relavant information about your hardware and software.
- Send an email to email@example.com. Please include [BETA] in the subject so it is directly assigned to the beta support team.
Restoring old version
You can restore the older stable version at any time if you encounter any issues which prevents you from using PIA normally.
- Download older version of PIA Desktop client
- Run installer of older version
- Multiple processes of "pia_nw" and "pia_nw.exe" (up to 4) can be running on your computer while the application is active. This is due to the multi-process nature of the application, which is derived from Google's Chromium engine. This is not a bug.
- Only 64 bit Ubuntu is supported for this build. 32 bit support is coming soon.
- This version is tagged v59 instead of v57. Explanation will be provided in a separate post.
- Bug fixes, performance and stability improvements.
- Upgraded openssl version.
- Vastly reduced dependencies for linux. Only libxss and libindicator1 are required
- Added support for 32 bit linux. The linux installer should work with both platforms.
- Added an option to disable debug logs being collected on your computer. These are primarily used by support to diagnose issues. If you have an SSD you can consider turning these off to further reduce writes to the disk.
- A clear message is displayed while connected, explaining that you cannot change settings. The UI is also grayed out more prominently.
- The PIA icon won't appear in your taskbar or Alt-Tab menu, which was the behaviour of the older application. Users requested the older behaviour to be restored.
- Known Issue: In some cases, on Windows 10, if you have VPN kill switch enabled, suspending/hibernating your computer and resuming might break the openvpn connection. This is currently a major priority and will be fixed in an upcoming release. A workaround is to disconnect and re-connect if you encounter issues.