SparkLabs Forum.

Community Help.


Issue with OpenVPN 2.4 - 1.7.10 Build 1570

Hello all!

I'm seeing an issue when trying to connect to any of my VPN connections. Logs are as follows:
----
Jul 31 7:44:00 AM: State changed to Creating...
Jul 31 7:44:02 AM: State changed to Disconnected
Jul 31 7:44:05 AM: State changed to Connecting
Jul 31 7:44:05 AM: Viscosity Windows 1.7.10 (1570)
Jul 31 7:44:05 AM: Running on Microsoft Windows 10 Enterprise
Jul 31 7:44:05 AM: Running on .NET Framework Version 4.7.03056.461808
Jul 31 7:44:05 AM: Bringing up interface...
Jul 31 7:44:07 AM: to start. Please check files for integreity.

The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Ensure ViscosityService is running.
- Make sure the configuration is valid

Jul 31 7:44:07 AM: State changed to Disconnected

----
The Viscosity service is running, but checking the event log yielded the following:
----
Faulting application name: openvpn.exe, version: 2.4.6.0, time stamp: 0x5b317d79
Faulting module name: openvpn.exe, version: 2.4.6.0, time stamp: 0x5b317d79
Exception code: 0xc0000005
Fault offset: 0x0003d4b0
Faulting process id: 0x1464
Faulting application start time: 0x01d428dcee9ecc51
Faulting application path: C:\Program Files\Viscosity\Resources\OpenVPN2.4\openvpn.exe
Faulting module path: C:\Program Files\Viscosity\Resources\OpenVPN2.4\openvpn.exe
Report Id: d8e46bc5-844c-4652-a27f-aaa7650ac73c
Faulting package full name:
Faulting package-relative application ID:

----
I noticed that Viscosity was set to Automatically select the OpenVPN version to use. Forcing it to 2.4 yielded the same results. Forcing Viscosity to use OpenVPN 2.3 allowed the connection to complete successfully, though this isn't something I'd like to run long term and it's proved to be rather unstable (likely something on my end, but I'd love to get back to 2.4 so I don't have to troubleshoot that :) )

I did a complete uninstall and reinstall of Viscosity to ensure there was nothing wrong with my installation files that might cause an issue. I'm using Windows 10 Build 1803 and the latest build of Viscosity (re-downloaded this morning to confirm).

Anyone else having similar issues or have ideas on resolution?

-Will
Hi wudo,

It looks like OpenVPN is crashing, haven't seen this in a very long time. Could you please post (or you may wish to email it to us at [email protected], this is a public forum) a copy of your configuration? To do this, hold shift and right click the connection in Viscosity Preferences, then select View Configuration file.

As you've already reinstalled, there is something going on with your machine or your configuration. In the mean time, please disable all AV, Firewall or development software you have and try again.

Regards,
Eric
Eric!

I just updated to the new build - 1.7.11 (1576) - and without making any other changes to my connection profile or to Viscosity, I'm now able to connect successfully!

Whatever bugs the team fixed seems to have got me working again. Many thanks for the help!

-Will
Thanks for letting us know, Will.

Regards,
Eric
4 posts Page 1 of 1

Copyright © 2016 SparkLabs Pty Ltd. All Rights Reserved. Privacy Policy