Users have reported and we have confirmed a problem with the latest version of the Viscosity client on our service. It is appears to be a problem with the handshake while connecting to our service with the latest version. We are currently investigating the issue.
The problem is isolated to the newest version of the Viscosity client, and it spans both Windows and OSX.
For now, we recommend using the default OpenVPN client in Windows (we actually recommend it anyway in Windows) and the TunnelBlick open-source client for OSX.
We have contacted SparkLabs to try to identify the problem for a possible patch on their end.> read more
Some of the Chicago servers are being taken down for updates. You may be disconnected from the service during this maintenance if you are signed in to an affected server. If you are disconnected, you should be able to immediately reconnect to unaffected servers in the cluster.
Also, for the next 12 minutes, you will not be able to generate new configuration files.
Edit: All Chicago services have been fully restored. The ability to generate new config files has also been restored.> read more
We have completed our Ubuntu 13.10 (Saucy Salamander) installation guide for YouTube.
You can view it here: https://www.youtube.com/watch?v=6l4AknUTTCk
This guide is actually substantially simpler than our previous guide, because 13.10 has OpenVPN 2.3.2 built-in which has full support for inline keys. This removes multiple steps from the old install process.
More guides are coming! Next up is Windows 8. Then Android and iOS.> read more
A new vulnerability has been discovered in Google's Android operating system that allows a malicious app to bypass some VPN services. Our OpenVPN service is not impacted by this new vulnerability because our data is encrypted at the application layer, before any other app would get a chance to pull the data to route somewhere else.
This vulnerability will affect PPTP and L2TP VPNs that are using the built-in VPN functionality in Android. VikingVPN, being a security-conscious VPN provider, has never supported these types of VPNs due to their inherent security issues with encryption and man-in-the-middle attacks.> read more
Users have reported problems with the Chicago cluster related to connectivity. We are currently investigating the issue. Depending on the action taken, you may get dropped from the service momentarily while we work on the cluster.
I will report back when the investigation is complete.
Edit: Investigation complete, and the problem should be fixed for all users.> read more
We have completed our rollout of new server clusters in Phoenix, AZ and Amsterdam, NL.
To access the new server clusters, you will need to log into the site and visit the Profile area.
When you generate a new certificate, you will now get 3 configuration files, one for each server cluster. These need to be placed in your config folder. Be sure to delete any of your old config files when you generate new ones, as the old certificates and keys are revoked when you create new ones.
You can then choose which VPN location you wish to connect to by selecting the server in OpenVPN GUI.
Because we use very high quality Tier-1 carriers, under normal conditions you should see the best performance from the cluster that is physically closest to your location. If either of our new sites are closer to you, you should get even better performance when connecting to them!
We have implemented our warrant canary into the site. Functionality is live.
What this means for our users is that they can be alerted if we receive any legal action that contains a gag order. A good example would be the National Security Letters from the US government.
The key component with the warrant canary is it has to be passively activated. We have created a mechanism that will change the logo on the front page of our site to alert our users that something is wrong. Because of the nature of national security letters, if we have been served a national security letter or some other oppressive action that includes a gag order, we will be obliged by law not to talk about the action taken, nor can we acknowledge that the program or legal action that is being discussed even exists.
We are getting multiple customer reports on failures of our service to properly forward traffic on iPads while connected to 4G wireless services.
We are currently investigating the issue.
At this time, we believe that Wifi connectivity is working properly.
As a stop-gap, we recommend trying a hard-reset of your iPad (hold power+home for 10 seconds) to rectify the issue if your VPN stops working on an iPad.
I will update this post as we get more information on the issue and a resolution.
It seems that the iOS application is confirmed to be not working over AT&T 4G LTE properly at this time for all carriers regardless of settings. This is caused by a vendor update to iOS 6 and 7 that doesn't allow SSL VPNs to work properly due to a permissions issue. There is an update to OpenVPN Connect being worked on.
A discussion on the issue is here: