Skip to content
Connection to OpenVPN CloudConnexa
Got a problem with Viscosity or need help? Ask here!
Hi, I've been using Viscosity for years. About 6-months ago, my company changed to use OpenVPN CloudConnexa (JumpCloud). All was working great with Viscosity until about 2-days ago. Now every time I try to connect with Viscosity, I get a pop-up saying "The version of OpenVPN Connect client installed on this device is not compatible."
I for sure have the latest version of Viscosity 1.10.8 (1658).
My guess is something changed on the server side. Regardless, I have no control over that side, so I'm wondering if there is something I can do on the client side to fix this? Also, I'm able to connect just fine using the OpenVPN Connect app.
P.S. I'm running MacOS version 13.6 (Ventura)
I for sure have the latest version of Viscosity 1.10.8 (1658).
My guess is something changed on the server side. Regardless, I have no control over that side, so I'm wondering if there is something I can do on the client side to fix this? Also, I'm able to connect just fine using the OpenVPN Connect app.
P.S. I'm running MacOS version 13.6 (Ventura)
Hi dvlogic,
Thanks for the report.
We've done some testing, and this is definitely a bug in CloudConnexa. Its login system performs a redirect after you successfully log in, however this redirect has a bug causing duplicate fields to be lost (with only the first field remaining). In this case it's the "auth" field, which must be specified multiple times for each supported authentication mechanism (ref). The reason it's working with the "Connect" clients is a bit of a fluke: they're specifying the fields in a different order to Viscosity, and it just happens that the first field they're using is the field that avoid the "not compatible" message (which is also why they've likely not noticed the bug). I recommend reporting this issue to CloudConnexa.
In the meantime, we've also updated the latest beta versions of Viscosity to use the same ordering as a work-around for the bug. For information on how to update please see: https://www.sparklabs.com/support/kb/ar ... -versions/
Cheers,
James
Thanks for the report.
We've done some testing, and this is definitely a bug in CloudConnexa. Its login system performs a redirect after you successfully log in, however this redirect has a bug causing duplicate fields to be lost (with only the first field remaining). In this case it's the "auth" field, which must be specified multiple times for each supported authentication mechanism (ref). The reason it's working with the "Connect" clients is a bit of a fluke: they're specifying the fields in a different order to Viscosity, and it just happens that the first field they're using is the field that avoid the "not compatible" message (which is also why they've likely not noticed the bug). I recommend reporting this issue to CloudConnexa.
In the meantime, we've also updated the latest beta versions of Viscosity to use the same ordering as a work-around for the bug. For information on how to update please see: https://www.sparklabs.com/support/kb/ar ... -versions/
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
3 posts
Page 1 of 1