Viscosity 1.7.8 disconnects intermittently, asks for user/pw
Posted: Sat Apr 07, 2018 10:05 am
Hi,
After upgrade to Viscosity 1.7.8 on my Mac 10.13.3 High Sierra I noticed that Viscosity started to disconnect from time to time, bringing up the dialog to provide username and password to connect to my VPN provider again and again. I always tick the "store credentials in keychain", but it does not help. After I quit the app and start over again, I would be able to connect. The logs showed something "unable to read askpasswd" - unfortunately I did not save the exact text and now they are gone.
I tried going back to Viscosity 1.7.7 by copying the app over from one of my other Macs, but upon launch it says "Viscosity detected its helper tool needs to be installed" and after pressing "install" and providing credentials for the admin access, it complains that it failed to install the helper tool. So I had to reinstall the 1.7.8 again.
Could you advise whether there is a bug in 1.7.8 and where I can download the 1.7.7 version to test if that's really the issue with the latest version?
Thank you,
Roman
After upgrade to Viscosity 1.7.8 on my Mac 10.13.3 High Sierra I noticed that Viscosity started to disconnect from time to time, bringing up the dialog to provide username and password to connect to my VPN provider again and again. I always tick the "store credentials in keychain", but it does not help. After I quit the app and start over again, I would be able to connect. The logs showed something "unable to read askpasswd" - unfortunately I did not save the exact text and now they are gone.
I tried going back to Viscosity 1.7.7 by copying the app over from one of my other Macs, but upon launch it says "Viscosity detected its helper tool needs to be installed" and after pressing "install" and providing credentials for the admin access, it complains that it failed to install the helper tool. So I had to reinstall the 1.7.8 again.
Could you advise whether there is a bug in 1.7.8 and where I can download the 1.7.7 version to test if that's really the issue with the latest version?
Thank you,
Roman