Viscosity 1.10 getting auth failure (roll back to previous version works)
Posted: Tue Oct 26, 2021 10:23 pm
After the latest Viscosity upgrade a few days ago, I couldn't connect to any of my Openvpn servers.
It was driving me nuts, since I was able to connect with all other VPN clients, like OpenVPN client for instance.
I even wiped all Viscosity items in my KeyChain, uninstalled, reinstall, nothing worked.
I followed the full uninstall process here:
https://www.sparklabs.com/support/kb/ar ... osity-mac/
I ended up installing the previous version of Viscosity here:
https://swupdate.sparklabs.com/download ... 01.9.4.dmg
And now everything works.
I'm using MacOS Big Sur 11.6, if that helps, but I'm pretty confident the issue was with the latest version of Viscosity, since that is the only thing that changed on my system (that I know of).
Unfortunately, I do not have the Viscosity logs, but it was definitely saying "AUTH FAILURE", which was bogus, since I checked like a million times, and it was the same username/password saved in my lasspass account, which worked with my other VPN clients. I was using Google Auth as my MFA too. I don't know if that plays a role in reproducing the bug.
Anyway, I wanted to let you know about this, in case anyone else runs into this.
Thanks!
Alex
It was driving me nuts, since I was able to connect with all other VPN clients, like OpenVPN client for instance.
I even wiped all Viscosity items in my KeyChain, uninstalled, reinstall, nothing worked.
I followed the full uninstall process here:
https://www.sparklabs.com/support/kb/ar ... osity-mac/
I ended up installing the previous version of Viscosity here:
https://swupdate.sparklabs.com/download ... 01.9.4.dmg
And now everything works.
I'm using MacOS Big Sur 11.6, if that helps, but I'm pretty confident the issue was with the latest version of Viscosity, since that is the only thing that changed on my system (that I know of).
Unfortunately, I do not have the Viscosity logs, but it was definitely saying "AUTH FAILURE", which was bogus, since I checked like a million times, and it was the same username/password saved in my lasspass account, which worked with my other VPN clients. I was using Google Auth as my MFA too. I don't know if that plays a role in reproducing the bug.
Anyway, I wanted to let you know about this, in case anyone else runs into this.
Thanks!
Alex