Benbot2000 on Tue, 14 Nov 2017 11:28:14
Yesterday the translation API stopped accepting connections from my .Net web app. The code in my app hasn't changed for months. The exception message is:
The underlying connection was closed: An unexpected error occurred on a send.
From my testing it looks like you made a change to prevent connections that don't use TLS1.2. I can connect from my dev machine (which supports TLS1.2) but not from the server (which does not support TLS1.2).
Oddly enough these two addresses will not accept a connection:
But I can still get a token without TLS1.2 from:
Can you confirm if I am correct about you no longer accepting TLS1.0 connections?
Benbot2000 on Mon, 20 Nov 2017 12:55:32
After being broken for a bit less than a week this started working again (no changes on my server, not even a reboot). I have to assume someone at Microsoft pressed a switch by accident and then flipped it back again.
I tweeted Azure support and they told me to raise the issue here and then an engineer would review it. That was a week ago and no response from MS support. I wonder if AWS support provides a better response than no response at all?