Got a problem with Viscosity or need help? Ask here!
If you were to import the connection, does Viscosity ever create an adapter or are you saying that this is where it is getting stuck? It does sometimes take a minute.
There may have been a problem before you did the reinstall, have you allowed Viscosity to try and create an adapter since you reinstalled it?
It was installing OK, no errors, but would hang when it tried to connect. Service wouldn't start on reboot, actually had no status. When I started the service manually, I could get it to connect.
Once I stopped letting the connection create and use its own adapter, everything started working.
It did give the OpenVPN admin privileges warning, but its doing that now when everything works.
With the problem of the service not starting on reboot, if you go to Services, right click Viscosity Service then select Properties, go to the Recovery Tab, then change the "First Failure" drop down box to "Restart the Service", this seems to fix that problem. There is a service on some computers that starts in the wrong order which causes Viscosity Service not to start correctly.
As for the admin warning, are you able to post a screen shot of this warning? Is it coming from Windows or is it a Viscosity warning, as OpenVPN should NOT be asking for admin rights.
It's in the details pane for the connection -
NOTE: OpenVPN 2.1 requires '-script-security 2' or higher to call user-defined scripts or executables.
Interesting for 2 reasons, I think. One, we aren't calling any user defined scripts or executables with this configuration. And two, unless I'm mistaken, this version of Viscosity is supposed to be using OpenVPN 2.2, correct?
I've missunderstood you there. That warning is perfectly normal and will appear all the time.
Viscosity Windows is still running OpenVPN 2.1, version 1.3 will be upgraded to OpenVPN 2.2 and is the next addition to the current beta located here.
Who is online
Users browsing this forum: No registered users and 1 guest