"Could not create SSL/TLS secure channel" Error as of 1:25am today (London)

QVSource · 2014-10-15T07:04:33.445Z

As of 1:25am this morning (London time) we are now getting the following error:
“Could not create SSL/TLS secure channel.”

From our REST API requests, nothing has changed in our code.

Has anything changed which could explain this? It’s been working fine up until now.

starostin13 · 2014-10-15T09:03:57.235Z

I have same issue. Started from 6:30 PM by PTS and still ongoing.
My app developed with C#, i use next options:

            ServicePointManager.Expect100Continue = true;
            ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3;

And auth string have view: https://api.twitter.com/1.1/statuses/user_timeline.json?count=3&screen_name=MyName
But one of my old version of the site work is well. What’s going on?

andypiper · 2014-10-15T10:45:08.836Z

Unfortunately this is likely due to the fact that we disabled SSLv3. We announced this via @twittersecurity and I’ve also just updated the Announcements forum here to reflect the change.

Apologies that we were unable to provide more notice for this change!

QVSource · 2014-10-15T11:11:55.404Z

If you reauthenticate and get a new token does this fix it for you? It seems to for us.

starostin13 · 2014-10-15T11:24:17.996Z

Thanks for tip. Also I had to change the deserialization access token.

QVSource · 2014-10-15T12:00:46.117Z

Would the fact that re-authenticating (i.e. getting a new access token) also seems to have fixed this issue (without changing any of our code) be explained by this SSLv3 change?

andypiper · 2014-10-15T12:44:10.325Z

No, in that case you may already be using TLS and for some reason your token needed to be cycled - but that wouldn’t usually happen, so I’m a little bit surprised by this. I’m glad your code is working again though!

QVSource · 2014-10-15T14:58:43.108Z

Sorry - ignore that comment, re-authenticating just happened to fix it by chance by triggering something else I was tweaking with to fix it.

If you are a .NET user I believe you need to make sure that you DO NOT have this line:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3;

It should be set to either:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 | SecurityProtocolType.TLS

(Which is the default it seems so the above would be redundant) or just TLS.

milvusinfo · 2014-10-16T15:18:09.465Z

I have been using Twitterinvi and as of 15th i got this error as well.
Have tried the above change to tls1.2 /tls1.1 but its still the same
problem. I have not seen any changes on the twitterinvi site to patch
for this problem, any ideas what can be a next step to try?

andypiper · 2014-10-16T23:31:43.382Z

I’m not familiar with Twitterinvi myself. I had a quick look at the source code and cannot see any SSL or TLS references so I’m guessing the library itself isn’t affected - you could always raise an issue with them if you think there is a problem there.

jsakamoto · 2015-04-13T13:48:23.486Z

I have same issue. I’m using C#, and CoreTweet, and the my app is ASP.NET Web application hosted on Microsoft Azure Web Apps (old name is “Azure Websites”).

I encounter this problem at every 8:00am morning in Japan.
It happen always 8:00am JST, every day.

I have no idea at this point, and I am not sure that this issue happened only on Azure.

Could you post comment here about what platform do you using when encounter this issue? > All

joel1 · 2016-01-21T08:48:19.379Z

Has anybody had any success in resolving this problem? I’ve tried to only use TLS (not SSLv3.0), regenerated access tokens, created entirely new twitter applications with new access tokens. I still get this error every day around 10 and 22 UTC.

Using LinqToTwitter