I have 2 macbooks with El Capitan. Due to their age no upgrade of the OS is possible.
Now VyprVPN dropped support for EL Capitan thus no bugfixes will be available.
Recently the VyprVPN app stopped working (no connection can get established), so I went through the support pages and noticed the indication of a manual VPN setup with IKEv2 support.
Now fact is that IKEv2 support on these OSs is buggy, every 8 minutes OSX wants to rekey, and the connection breaks.
This issue with IKEv2 is well documented, just google "os x ikev2 failed 8 minutes"

So after contacting support they gave me the hint of checking with openVPN, which actually solves the problem (off course first installing tunnelblick), but I noticed that on the support pages, under Mac there are so many options, and the tunnelblick reference (for a non VPN expert) was confusing.
I only clicked on tunnelblick and OpenVPn because support told me to check openVPN

So actually under EL Capitan, at least for me, tunnelblick and openVPN seems to be the only solution available!But the way of finding this solution was far too complicated and non-intuitive

Requests:
1) For OSX 10.11 and lower remove the IKEv2 hint on support pages, it is misleading and doesn't work in the end. Users might be discouraged when trying that (like me)
2) Instead of the IKEv2 recommendation, the support pages should offer Tunnelblick and OpenVPN more prominently for El Capitan users, perhaps a refrasing would be also smart, mention openVPN before Tunnelblick....
3) the different Mac Options could be reorganized for better intuition, specially offering for 10.11 only the OpenVPN solution (with tunnelblick), I would rewrite the order on this point: first protocol, then the app to be used.

I think it's not a shame to offer the Tunnelblick OpenVPN much more prominent as a fallback solution for older MacOS
It's a bigger shame to have it so hidden that unexperienced users frutratedly stop using your VPN...

It is also recommended to indicate that the main service ooffered is VPN itself, not necessarily the App, at least for older OSs it's completely understandable