I am getting "could not connect ssl/tls secure channel" error while trying to call our API from Windows application. The dll used in Windows Application targets .Net framework 4.8 and it calls another dll written in .netstandard2.0. This .netstandard2.0 dll eventually uses RestSharp 108.0.2 version to make API call. I tried all the suggestions I could find in following link and so many other pages but nothing is working so far.
Here is the hierarchy of versions involved: MFC App->.Net Framework 4.8 dll->.NetStandard2.0->RestSharp108.0.2.
RestSharp: Could not create SSL/TLS secure channel
Any help here would be great. I am starting to think if the issue is related to having combination of .Net Framework and .NetStandard in the same process. I have tried all the suggestions by changing code in the .Net Framework 4.8 dll but not in the .NetStandard dll that makes the actual API call.
Just for my understanding, can someone clarify which base class library will be used in this case to make the call to api? i.e. .NetFramework4.8 or .NetStandard2.0?
More Info: This is happening on Windows 10 on client's machine. I don't have information about the build number yet. I've never used Wireshark but I can look into it. I'll put actual callstack when I get it back from client.
innerException. Which version of Windows is this? Exact build number please. Can you set up a Wireshark trace to see the Client and Server Hellos, there may be a cipher or TLS version mismatch.InnerExceptionas asked, that has more info on the exact issue. Please give the OS build number as asked.not in the .NetStandard dll that makes the actual API callthe call is made by .NET Framework classes. .NET Standard code can't run by itself. The actual calls are mapped to the underlying runtime and libraries. Since 10.7 RestSharp actually uses HttpClient underneath