Unable to Establish a Secure SSL/TLS Channel to Awork API from Windows Server 2012

Developer Forum
1

Hello everyone,

Since earlier this week, we are no longer able to connect to the Awork API from a Windows Server 2012 machine. The same setup had been working fine until last week.

The issue seems to be related to the SSL/TLS handshake. Specifically, we are receiving an error indicating that a secure SSL/TLS channel could not be established when attempting to communicate with your API.

There have been no changes to our code or server configuration during this time. We suspect the issue might be related to updated TLS requirements or a change in supported cipher suites on your end (e.g., deprecation of older TLS versions such as TLS 1.0 or 1.1).

Can you please confirm if there were any recent changes to the TLS configuration of your API servers, such as enforcing TLS 1.2 or newer?

Any information you can provide would be helpful in resolving this issue.

Best regards,

2

Hi @Thomas.Martin ,

we changed a week ago our edge networking service and i just checked the configuration and we only allow only TLS 1.2 upwards.

Sorry with this causing trouble for you, but TLS is already deprecated since March 2021, so we did not expect to have anybody trouble with that.

Best regards

Nils

3

Hi Nils,

thank you very much for your quick response. We’re actually using TLS 1.2, but our system is running on Windows Server 2012 R2, and it seems there’s an issue with the TLS handshake that prevents a secure channel from being established.

Would you happen to know which cipher suites are required by awork for the TLS handshake?

4

sure:

image
image906×366 13.6 KB

5

Thanks for the clarification. That effectively rules out Windows Server 2012 R2 for this integration, but I appreciate the heads-up. I’ll review our alternatives and circle back if anything else comes up.

Best regards

6

Hey Nils, I had one more quick question:

Where do you usually announce updates like this? I had a look around your blog and documentation but might’ve overlooked it — would you mind pointing me in the right direction?

Thanks again, really appreciate your help — and best regards!

7

Usually we post it here: Changelog

But we did not anticipate that the change of the edge provider had such an impact. We could for a limited time downgrade to this policy (the right one):

image
image1296×1324 78.4 KB

My quick research showed that this should work on windows server.

Best

Nils

8

Thank you very much for the offer!
We actually planned to upgrade the server anyway, so we’re now moving things forward and migrating the service to a newer system. From our side, everything is fine — we were just a bit caught off guard by the sudden change.

I’ve now subscribed to the changelog, so we should be informed about such updates in the future.
Thanks again for your kind and helpful support!

1 Like