Unable to request twitter v2 API since 03/16/2022

[Julemane]

Hi,

Since yesterday we are not able to generate a token through this endpoint “…/oauth/request_token”

It returning a TLS issue

Our OS is a 2012 R2 Datacenter server
The ciphers exposed are as follow

Can you confim that all 2012 R2 ciphers are not supported anymore ?

We don’t found any comunication about ciphers deprecation Twitter side.

Thanks for reading

[Julemane]

twitter seems to expose only these ciphers :

[iKiteFlyer]

We have the exact same problem.

Windows Server 2008 R2 which has been working fine for years suddenly stopped being able to communicate with api.twitter.com yesterday.

We now have thousands and thousands of users that are unable to login to any of our platforms as our server can no longer connect to the Twitter API.

Are Twitter likely to re-enable the cipher suites they removed yesterday?

Does anyone know a workaround for this?

[rukavina_rob]

Same issue here. Not sure what our server is running but it worked fine until yesterday. Then out of nowhere it just broke. Works fine on my local environment but live site is no bueno

[iKiteFlyer]

Is there anyone at Twitter we can contact about this?

I can’t find any announcements or anything else that might explain what’s going on.

[Julemane]

FYI after updating the OS to windows 2016 all back to normal

But if a Twitter staff can confirm they 've made modification on their API server, and where we can find the announcements to avoid this in the future

[iKiteFlyer]

Thanks for the confirmation @Julemane

In the absence of any response from Twitter on this issue I think I’m going to have to buy a new Windows Server 2019 and move everything.

We’ve got so many users that are locked out of our applications and platforms now, I really can’t wait any longer

[jim_plode]

exact same issue here running windows server 2008.
would be great to get some kind of response from twitter about this.

[garamirez06]

Buenas noches… en mi caso mi desarrollo esta en .Net y tambien tuvimos problemas con servidores Windows Server 2012 y 2016.

La solucion que encontramos fue eliminar Internet Explorer y luego instalar Edge.
Con esto volvio a funcionar nuestro desarrollo…

Saludos

Good evening… in my case my development is in .Net and we also had problems with Windows Server 2012 and 2016 servers.

The solution we found was to remove Internet Explorer and then install Edge.
With this our development worked again.

Greetings

[MikeNapthine]

IT APPEARS TO BE FIXED!!

As of 20:00 18/03/2022 UTC+00 (last night) our original processes on server 2012 burst back into life. (cant vouch for 2008 which is end of lifed), but hopefully Twitter will respect the endof life of Server 2012 of Oct 2023!

[jim_plode]

Still no official word from twitter…

[rukavina_rob]

Yeah, I wish we would hear something from Twitter about this and what we can do if it happens in the future. I tried providing options in .net for tls, tls12, tls13 and ssl3 because I found something on stack overflow suggested that but it did no good. Apparently the fix that @MikeNapthine mentioned above worked for us as well, but I feel like we should get some kind of explanation as to what happened from twitter. boooo