Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: TRESTClient issue connecting over TLS 1.2 on Windows Server 2008 R2



Permlink Replies: 1 - Last Post: Jun 20, 2017 6:59 PM Last Post By: Philip Scott
Philip Scott

Posts: 2
Registered: 3/4/10
TRESTClient issue connecting over TLS 1.2 on Windows Server 2008 R2
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jun 20, 2017 6:23 PM
I have a Delphi (10 Seattle) application that connects to the Stripe API using TRESTClient.

Running it on my Windows 10 PC it works perfectly. On my Windows Server 2008 server it fails. Stripe's API responds with (minimum TLS 1.2 required). I have updated the Wind 2008 R2 server to support TLS 1.2 and managed to connect to the Stripe API using Internet Explorer on the server box, but my Delphi App still reports an error.

Error I receive is: "Stripe no longer supports API requests made with TLS 1.0. Please initiate HTTPS connections with TLS 1.2 or later. You can learn more about this at https://stripe.com/blog/upgrading-tls"

Short of Disabling TLS 1.0 and 1.1 on the server (which seems like it'll stop me from being able to RDP to it), is there something I need to do in my application or is it all purely the OS? As I'm asking I'm beginning to realise it's probably all OS right?

Any advice/suggestions would be appreciated.

Thank you!

Edited by: Philip Scott on Jun 20, 2017 6:26 PM
Philip Scott

Posts: 2
Registered: 3/4/10
Re: TRESTClient issue connecting over TLS 1.2 on Windows Server 2008 R2
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jun 20, 2017 6:59 PM   in response to: Philip Scott in response to: Philip Scott
Seems I found the solution:

https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1.1-and-tls-1.2-as-a-default-secure-protocols-in-winhttp-in-windows

I downloaded the "Easy Fix" utility from this link that changed the DefaultSecureProtocols registry entry and now it seems to be working!
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02