Hi, To reset this setting, Exit Viscosity and then run: "C:\Program Files\Viscosity\Viscosity.exe" SetPref ConnectionScriptTimeout deletepref To reset all settings, delete the file at %appdata%\Viscosity\Settings.xml (type in %appdata%\Viscosity into an explorer window and press Enter). Please keep ...

Hi Andreas, Viscosity adds the 0/0 route you are most likely seeing as Windows requires a gateway for Network Location Awareness to work correctly. Please rest assure though that this 0/0 route is disabled and is not being used. You can confirm this by running a couple of trace routes to see where t...

Hi, Viscosity will terminate scripts that run for longer than 60 seconds to prevent scripts getting in a stuck state forever. It looks like your script is timed to not start your application until at least 65 seconds after it's first run if I'm reading your timeout values correctly. You have two opt...

Hi n8chavez, We've done some extensive testing and we're unable to find a problem using taskkill in a batch script. The route-pre-down script option is executed by the service, so running Viscosity as Admin will have no effect. Please ensure you have enabled AllowOpenVPNScripts option as per - https...

Hi n8chavez,

Do these scripts function correctly if just double clicked?

Regards,
Eric

Hi Greg,

We will see what we can do.

Regards,
Eric

Hi ratness, Our suggestion would be to move to a static challenge-response setup if possible. This way you can have the username/password window only ask for a username/password, and even save these credentials if you wish, and then a secondary window request your Google-auth with any message that y...

Hi n8chavez,

It sounds like an AV program may be intercepting the script, do you have any AV or Firewall software running? Do these scripts function correctly if just double clicked?

Regards,
Eric

Hi diman,

Using the Batch Start command will launch obfsproxy without waiting before the batch script continues. For e.g.

start "C:\path\to\obfsproxy" obfs2 .....

Regards,
Eric

Hi diman, I'm afraid obfs2 and obfs3 don't support shared-secrets within Viscosity, we recommend updating to scamblesuit or obfs4 if you wish to use a shared secret. If your only option is obfs2 and you need a shared secret, you can start your version of obfsproxy manually and then set your client a...