SSL cipher upgrades may have caused .NET issues
We are usually pretty good at catching anything that might cause adverse affects for our users. However it appears that we missed such an event a week ago when we increased the security on our web servers by enforcing only SSLv3 for SSL communication.
On Friday we learned that this change caused issues for those who are using .NET to connect to Chargify. The reported issue was that the SSL connection could not be established.
Thanks to @djbyter for being the hero on this one and quickly releasing an update to his popular Chargify.NET library. So, if you haven’t updated your Chargify.NET wrapper in a few days, you might want to go ahead and do that as soon as possible.
We’re sorry for any trouble this change caused.
