The request was aborted: Could not create SSL/TLS secure channel - TLS 1.3 & WebRequest
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
14-03-24 11:17 AM
Hi guys,
I'm struggling with a HTTP request, which needs TLS 1.3.
Yesterday the ECB changed its TLS from 1.2 to 1.3 ( SSL Server Test: www.ecb.europa.eu (Powered by Qualys SSL Labs) ) and currently when I'm trying to execute a request receiving an error: 'The request was aborted: Could not create SSL/TLS secure channel.'
I have tried to add:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls13
but without success, a new error appears: ''The underlying connection was closed''
I would like to avoid skipping checking a certificate.
Does any of you have any experience with TLS 1.3 and WebRequest class?
Thanks for any bit of advice!
Best,
L
------------------------------
Łukasz Kiciak
RPA Developer
UI
Europe/London
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
24-05-24 09:00 AM
@BluePrism Any update on this we are facing similar issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
30-05-24 03:46 AM
@ewilson Any Clue about this issue, we have same issue here. Everything works perfectly fine with Postman&TLS1.3, however encounter an same Error by using utility-http or Postman&TLS1.2. Any idea about that? Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
30-05-24 03:10 PM
Support for TLS 1.3 is only included in certain recent versions of Windows and was only added to the .NET Framework in 4.8. You can find the list of support Windows OS's at the following link:
Cheers,
Eric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
31-05-24 02:31 AM
Thanks for your response @ewilson, clear now, we will see what we can do from our end.
Hanyuan