Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

The request was aborted: Could not create SSL/TLS secure channel - SecurityProtocol behavior

After installing certificate into Local Computer storage of Trusted Root Certification Authorities the .NET WebRequest still throws:

The request was aborted: Could not create SSL/TLS secure channel

ServicePointManager.SecurityProtocol now contains SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls.

After reading Simon Dugré's answer https://stackoverflow.com/a/2904963/121968, I have set:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3;

It works ok. After setting back:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls;

it still works ok. I have two questions:

  1. Why it still works? Is there sort of caching?

  2. And why it was previously working just with flag Ssl3 only and not with both Ssl3 and Tls?

like image 539
TN. Avatar asked Dec 18 '12 09:12

TN.


People also ask

Why the request was aborted could not create SSL TLS secure channel?

The error “The request was aborted: Could not create SSL/TLS secure channel.” can happen during any download HTTP request. This error generally will correspond to firewalls, proxies or DNS filtering blocking the connection or an SSL/TLS cipher misconfiguration.

Can't create SSL TLS secure channel IIS?

However, the "Could not create SSL/TLS secure channel" error usually means that there's something wrong with the server certificate, e.g. the certificate is for a different hostname, or otherwise invalid, or not trusted etc.


1 Answers

There is SSL/TLS session resumption, probably that's your case. Maybe you do not have shared TLS1 ciphersuites. The best way to check is to run Wireshark, and see SSL packets for your connection, they are very good explained in Wireshark.

like image 95
Nickolay Olshevsky Avatar answered Oct 04 '22 21:10

Nickolay Olshevsky