Monday, September 11, 2017


Recently I stacked on https related error on .NET Core 2.0

- InnerException {System.Net.Http.WinHttpException (0x80072F8F): A security error occurred
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.Tasks.RendezvousAwaitable`1.GetResult()
   at System.Net.Http.WinHttpHandler.<StartRequest>d__105.MoveNext()} System.Exception {System.Net.Http.WinHttpException}

All that I could found - this error is related to the inability of creation SSL/TLS tunnel.
But could be caused by different reasons:

  1. require explicitly set TLS - https://stackoverflow.com/questions/42746190/https-request-fails-using-httpclient
  2. skip invalid certificate check - https://stackoverflow.com/questions/42746190/https-request-fails-using-httpclient
  3. an absence of common cipher methods between server and client
Or some different reasons.
The core problem - this error is vague in .NET Core, when I tested this on .NET Framework the error was much more clear "The request was aborted: Could not create SSL/TLS secure channel."

In my case, this was an absence of common cipher methods between server and client. So I tracked by Fiddler SSL/TLS handshake and ask server admins to add on server configuration one of the cipher methods from client SSL/TLS handshake.