We use the test/sandbox AIM/CIM APIs environments extensively in our automated builds and have for some time. We're seeing intermittent connection issues particularly to CIM starting yesterday morning.
Are there on-going issues right now? When will they get resolved?
02-22-2012 09:56 AM
I've been seeing the same thing - around 50% of my connections to apitest.authorize.net fail. Everything worked perfectly Monday night, then Tuesday morning they started failing.
02-22-2012 11:49 AM
I been having issues too..
I switched all my code to curl... seemed to fix the problem.. but it came back..
looks like if you post a few things within 1 min, it will fail for 30 sec or so...
I tried talking to live chat, but they arn't too bright..
anywho figure if enough people say there something screwy with the CIM api server they will look into it..
02-22-2012 01:30 PM
Thanks for the reports. I just wanted to let you know that we are going to take a look at our test system and see if we can find something that could be causing the problem. Please let us know if you continue to see these problems.
02-22-2012 02:19 PM
exception 'AuthnetCIMException' with message 'Connection error: Unknown SSL protocol error in connection to apitest.authorize.net:443 (35)' in
there is more to the error, but that should get you started...
Outgoing Parameters customerType individual validationMode liveMode taxExempt false recurringBilling false amount 1 customerProfileId 111111 customerPaymentProfileId 111111 cardCode 111
numbers was changed to "1" by me...
02-22-2012 03:56 PM
Would you please use cURL to connect to the CIM apitest URL, using the -v
flag, a few times to see if the SSL error appears in the verbose response data? That could help pinpoint the issue.
There is no need to post any test data. I would expect API errors when you post without the data, and that can be ignored for this test purpose. The SSL error logging, in contrast, would be insightful.
Running curl -v https://apitest.authorize.net
from the command line or shell prompt a dozen or so times should be sufficient, as long as you've preconfigured cURL and aren't needing to tell cURL to use a specific configuration in your code. If you are specifying a configuration for cURL to use in your code, that configuration might well be part of the problem, but it's hard to be sure without hard data.
02-23-2012 10:58 AM
The error I am seeing using curl -v is as follows
curl -v https://test.authorize.net/
* About to connect() to test.authorize.net port 443 (#0)
* Trying 64.94.118.151... connected
* Connected to test.authorize.net (64.94.118.151) port 443 (#0)
* SSLv3, TLS handshake, Client hello (1):
* Unknown SSL protocol error in connection to test.authorize.net:443
* Closing connection #0
curl: (35) Unknown SSL protocol error in connection to test.authorize.net:443
03-13-2012 08:16 AM
Thanks for that information. I have a few other questions:
03-13-2012 08:58 AM
For me this does not happen that I can see (in 50 attempts) to https://apitest.* it only happens for me to https://test.* (this is what the copy of the SIM and AIM documentation that I have direct me to use for the sandbox? Are my docs out of date should I be attempting to connect to apitest instead? I have not seen this at all with connections to https://secure.authorize.net/gateway/transact.dll
Sam D
03-13-2012 11:50 AM
The live URL for CIM is: https://api.authorize.net/xml/v1/request.api
The test URL for CIM is: https://apitest.authorize.net/xml/v1/request.api
If you're using a different URL, that would explain the errors.
03-13-2012 12:21 PM