From github: sample-code-csharp suddenly failing: The request was aborted : Could not create SSL/TLS

[WHOISJohnGalt5]

A month or so ago, I downloaded the sample app solution for Visual Studio, from 

https://github.com/AuthorizeNet/sample-code-csharp (I needed to use it to update some custom C# code to use TLS 1.2). 

I was able to run the method: ChargeCreditCard

However, this weekend when I tried running that same method, I received the error:

System.Net.WebException The request was aborted: Could not create SSL/TLS secure channel.

I can't think of anything that's since changed on my computer (I did try with the firewall disabled, thinking that was interfering with the communication, but that made no difference). 

Any ideas on what could have changed? Help! (Need to upgrade my custom code to TLS 1.2 ASAP).

[WHOISJohnGalt5]

More info: I just uploaded my custom code and ran it from a live web host (instead of from localhost), and it was successful!.

So, there's something specific to computer. After looking at the timelines for when I last successfully ran the sample code on my computer, and what changed since, I saw that my Windows 10 installation was upgraded to version 1803

So, I'm thinking that's the culprit (as far as not being able to run the new API on localhost running on Windows 10, 1803.

Has anybody else seen this behavior?

[ChrisWalker808]

Yes I am having this issue  for me it was not related to 1803 update  the update was a few days before it stopped working when I called into support they reported that they updated the SSL certs.

I believe the SDK needs to be updated with:

 const SslProtocols _Tls12 = (SslProtocols)0x00000C00;
            const SecurityProtocolType Tls12 = (SecurityProtocolType)_Tls12;
            ServicePointManager.SecurityProtocol = Tls12;

 in at least this call for me  

// instantiate the contoller that will call the service
var controller = new createTransactionController(request);
//controller.
controller.Execute();

Authorize.net should update this promptly instead of giving me the support run around.

[DanH]

Strangely, I only get the error on the first time the app pool starts.  So to reproduce it, I can just rebuild my project.  On the production server, if I restart the app pool, it fails too.

Specifying TLS 1.2 as described fixed it for me.  Though from what I've read that should not be necessary if .Net Framework 4.6+ is being used as is my case. 

So it's a mystery to me.

[Draugh44]

Hello bro. I am also having the same type of issue. I am also not able to fix any how. What did u do at last? 

Thanks

-

Drough.