Sandbox issues: The underlying connection was closed: An unexpected error occurred on a send.

[Devin]

All of our sandbox requests are getting the following error: 

Outer Exception : The underlying connection was closed: An unexpected error occurred on a send.
Inner Exception : Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Inner Exception : An existing connection was forcibly closed by the remote host

The same requests to the live servers are working.

These are CIM/soap requests (GetHostedProfilePage and GetCustomerProfile) as examples.

Is anyone else experiencing this issue?

[RichardH]

@Devin

Are you connecting using our SDK, or if using our API what is the endpoint you are using?

You might also want to log the HTTPS traffic to see if there is more detail in the connection information.  It appears to be an issue negotiating a secure connection.

Richard

[Devin]

@RichardH,

This just started today. We're using CIM/Soap (in process of updating to use your SDK). The endpoint being used is

"https://apitest.authorize.net/soap/v1/Service.asmx";

For production we use  

"https://api.authorize.net/soap/v1/Service.asmx";

[millers_35]

We have been seeing the same issue since April 1. From our webserver probably only 20% of time I can load "https://api.authorize.net/soap/v1/Service.asmx" Error: The underlying connection was closed: An unexpected error occurred on a send. Problem is it only seems to be happening from that one network. Every other network I try it from works no problem. When using wireshark I see "Client Hello" and then a bunch of TCP Retransmission and TCP Spurious Retransmission then eventually connection reset.

[RichardH]

Hello @millers_35 @Devin

To assist you further, we'll need the following information:

• The Gateway ID or API Login ID used;
• The API endpoint used
• The dates when this occurred
• A PCAP file showing the point where the connection is dropped, and the TLS negotiation before that.

You may send these to developer@authorize.net

Richard

[millers_35]

@RichardH I submitted an eticket this morning but havent heard back yet. I just emailed the ticket number to developer@authorize.net.

Thanks

[lgallardocr]

Hi, I am having exactly the same issue but using API.

It started happening from April, 28th.

The endpoint used is:

https://apitest.authorize.net/xml/v1/request.api

[RichardH]

@lgallardocr

You'll want to make certain you can connect using TLS 1.2 to our sandbox, otherwise your connection will fail.

Richard

[lgallardocr]

thanks Richard for your quick response.

I have been looking at how to do it. but I didn't find yet.

Do you have any documentation to follow?

*our project is in c# and we are using the class AuthorizeNet.CustomerGateway to call the API methods.

Best, 

[RichardH]

@lgallardocr  Another developer suggested the following: https://community.developer.authorize.net/t5/Integration-and-Testing/Sandbox-issues-The-underlying-c...

Richard