| | | Dear Barracuda,
The issue should be resolved now.
As of a few days ago, Twitter is no longer accepting certain TLS v2 cipher suites when systems connect to their API over https, as is used by the SI webservers to add tweet content to our oEmbed cache database.
Unfortunately, our webservers are running an older version of Windows Server, and will simply not support the cipher suites that Twitter requires now, despite our best efforts to get them going.
So, we've implemented a workaround, where our servers now instead make the request through an Stunnel proxy we now have running, instead of directly to Twitter. Stunnel does support the required cipher suites and so the secure channel can be set up.
The updated code that uses the proxy will work without any proxy when we do buy some newer hardware. It checks the Windows Server version, and only uses the proxy if the required TLS ciphers aren't supported.
It took a lot of effort to diagnose the issue, and an equal amount to figure out a fix. I will admit that ChatGPT is an indispensable resource to developers nowadays and was of great aid in our getting this resolution into place. As a friend of mine in a completely different line of work says, ChatGPT will take your job... to the next level. :)
Regards,
@Dima |
|
