What is Error 6050?

This is an error specific to the OpenVPN and Chameleon protocols. In most cases, this will mean that the connection was successful but the post-connection call to our servers to verify a "good" connection failed. Thus, the connection was terminated.

You can try the following steps to resolve this error:

1. Flush DNS resolver cache.
   1. Click the Start button and navigate to the Command Prompt by Start > All Programs > Accessories > Command Prompt
   2. Right click the Command Prompt application and select "Run as Administrator" from the options.
   3. On the Command Prompt line, type in the following command and hit enter: ipconfig /flushdns
      
2. Reset the TCP/IP stack.
   1. Navigate back to the command prompt using the steps indicated above.
   2. On the Command Prompt line, type in the following command and hit enter: netsh int ip reset resetlog.txt
      
3. Try connecting with a different protocol (other than OpenVPN or Chameleon).
   1. If you are unable to connect with any other protocol, then contact our Support Team to troubleshoot your connection issue.
   2. If you are able to connect with other protocols, then proceed to step 4.
      
4. Please navigate to your settings menu try connecting with both TAP adapters. To do this, select Customize in the bottom left-hand corner of the application. Scroll down to the Tap Adapter option and try both TAP Adapter(s).
   
   1. If only one TAP adapter is successful, then please attempt to reinstall the problematic TAP adapter. (OpenVPN TAP | VyprVPN TAP (x64) | VyprVPN TAP (x86))
   2. If both TAP adapters are unsuccessful, proceed to 5.
      
5. Please try connecting with the 3rd party OpenVPN GUI app. (Vista | Win 7 | Win 8 | Win 10)
   1. If OpenVPN GUI is successful, then it is likely an issue with the VyprVPN application. Please contact our Support Team to for further assistance
      
   2. If the OpenVPN GUI is unsuccessful, then it is likely that OpenVPN connections are not supported on your local network. For further assistance, you will need to contact your ISP.
      

 

Last reviewed/updated August 2019