Posts: 1
Registered: ‎10-27-2010

Re: Relay Response (SIM)

Your symptoms sound the most similar to mine, with a few exceptions:



  1. We are using a root-signed certificate (signed by Thawte)
  2. Orders were received without problems for a year and a half, until this May. 
  3. Since then, the relay receipt is successful about 80% of the time: If the relay receipt page is visible in the access_log, then the transaction will succeed; otherwise it will fail. 

I'm the programmer for a low-volume site, and I don't have root access on the machine to run tcpdump for days/weeks until the next failure occurs, so I can't do the same kind of debugging that you have done. Worse, the department that has hired me doesn't seem to care that I am charging them for time to manually confirm with every failure, and they don't seem to be interested in any sort of investigation into where the receipt delivery fails. But I care, and want to resolve the issue!

Posts: 1
Registered: ‎11-23-2010

Re: Relay Response (SIM)

[ Edited ]

Hello Mathew,


We too are experiencing a similar issue. The first transaction run fails on the relay response, all subsequent transactions complete successfully within say 30-45 mins. If no transactions are run within that time frame, the next transaction will fail. Sounds similar to your "if it's not visible in the log" issue. Did you ever find a resolution to this problem? has been no help whatsoever.




Posts: 9
Registered: ‎10-28-2010

Re: Relay Response (SIM)

For what it is worth, we are also experiencing a similar issue.  The same exact transactions sometimes work and sometimes they produce a timeout error.  I haven't actually figured out any kind of pattern to which ones work and which ones do not.  I can take one that fails with a timeout error and do the exact same thing a minute later, and it will go through just fine.

Posts: 2
Registered: ‎08-06-2011

Re: Relay Response (SIM)

For what it's worth, the SIM method with a relay URL worked perfectly for years prior to the data center fire of July 3, 2009.  Right after that fire, when they moved into their backup data center, this issue began.  I worked with Daryn Barney and others at Authorize.Net in uly of 2009.  Not sure they ever worked hard on it, but I did find a solution.  We tested and found that the issue is latency in the Authorize.Net data center.  They spend almost no time letting the name server resolve.  Therefore, we kicked up the TTL on our name server from the 3600 second default to 86400 seconds.  You can even kick it up to a week.  This forces the servers to avoid looking up dns info everytime there's a transaction and makes the relay URL work 99.99% of the time. You still get occasional errors if nobody uses the payment form for awhile.


My challenge now is that I am trying to get this to work on a GoDaddy server for a customer.  GoDaddy will not adjust TTL on their name servers.  I understand why they won't do this, but I have never found another solution.


If anyone ever finds another solution, please post it.  Without another solution, the relay url is a useless feature in SIM until listens to this info and makes some really simple fixes.


Posts: 2
Registered: ‎08-06-2011

Re: Relay Response (SIM)

Just checking in again.  Has anyone out there ever recently gotten Relay Response to work with SIM?  I stripped mine down to nothing more than a static call with a relay response url page that does nothing but says Made It.  The server times out immediately, not after 10 seconds like advertised.  I cannot find a way to make the relay response work with SIM.  Anyone??

Posts: 1,476
Topics: 33
Kudos: 34
Solutions: 126
Registered: ‎09-14-2009

Re: Relay Response (SIM)

That probably means there is something wrong with your URL or server. Can you get the page to work when you call it directly in your browser? Have you verified the proper HTTP headers are being sent by your server.

John Conde :: Certified Authorize.Net Developer (Brainyminds) :: Official Authorize.Net Blogger

NEW! Handling Authorize.Net's Webhooks with PHP

Integrate Every Authorize.Net JSON API with One PHP Class (Sample code included)

Tutorials for integrating Authorize.Net with PHP: AIM, ARB, CIM, Silent Post
All About Authorize.Net's Silent Post
Posts: 1
Registered: ‎09-26-2011

Re: Relay Response (SIM)

@bmarshallbri wrote:

I have been having the same problem and of course, support is pretty much useless. My problem boiled down to SSL connections preventing the script from ever firing.This may not be the same culprit as your problems but my symptoms sound the same. I did some sniffing on the server while testing and here's what was going on on our setup.



1. I can hit the script in my browser, it responds immediately but SIM spits out an error 52 (timeout after 10 seconds) but it times out immediately, not after 10 seconds.

2. When I watch apache logs my return url never fires (never requested by

3. tcpdump shows calling in but again, apache never shows the request in the logs


So this got me thinking maybe it has something to do with our self signed certificates. Of course I called support and asked if their server is picky about ssl, self signed certs anything else along those lines and they said "no, it doesn't care. The problem is with your script'. Of course 4 different support techs tell me this and I know it's bullsh*t because my script never fires. Why does it never fire you ask? Well there where protocol errors with the ssl negotiation and the connection fails before the request ever makes ti through the stack to php. Of course, if what the techs told me were true, and their servers did indeed not care about SSL protocol errors then this would not be a problem and the transaction would complete. But of course it would be a problem for one of the largest gateways to allow encrypted transactions across an ssl tunnel with protocol errors. So the designers of the SIM system, honor protocol failures and terminate the they should.


After some quick testing by defining my SIM urls to be http not https and modifying my post vars in my call out to them I get an immediate response and the URL's function perfectly. I have yet to determine if the problem is the self signed cert or if I have a common name mismatch. But I'm just going to say I'm assuming there's a problem with the keys commonname and not in with the fact it is self-signed; and when I fix that, https URL's will function. If I find it is a problem with self-signed certs I will post back to this forum with an update. If I don't post back assume I messed my keys up :-)



I had the exact same problem, except I was using a paid certificate


it turns out I had a NameVirtualHost directive in my apache server config files, which is a no-no for SSL connections


here's a useful tool for seeing if your certificate is valid:


see more resources here:

"Name-based virtual hosting cannot be used with SSL secure servers because of the nature of the SSL protocol."





Posts: 8
Registered: ‎11-29-2011

Re: Relay Response (SIM)

Anyone know how to set up a Wordpress progress bar that captures donation amounts and adds them to the progress bar?  I really need a solution. Willing to pay for it. 

Posts: 14
Registered: ‎03-08-2012

Re: Relay Response (SIM)

Holy Krap Batman  Lots of people having this problem today


... please see my other posts .. we addressed this concern (Sans the Certificate portion)


with a simple Response.Flush() before doing our data dance to evaluate the post values sent back by AuthNet.


I wasn't even doing any database work just building a list to evaluate the returned values in another method before popping up either my receipt page or a    "You failed -- no payment for you !! "  --- esque..  page...based upon the results of my eval of the post data sent by AuthNet


Wow this is Comedy !!

MVC 3  .NET 4.0  C# 


to the guy that asked about SIM and relay_response  yes Sir ..  I have it working right now.

And this template will serve all of our customers that use this MVC site template and require a Cart system..




Posts: 1
Registered: ‎04-05-2012

Re: Relay Response (SIM)

My x_relay_url was working great until the other day. I don't know what happened and no code was updated from what I can tell.

Now I get the error:

 "Your script timed out while we were trying to post transaction results to it."

The timeout occurs immeidately (not 10 seconds later)

Furthermore, no matter what I change the x_relay_url to, I still get the same message.

Here is what I am posting:

What has me for a loop is that it was all working great and nothing changed on my end. Is there any way to validate a relay url?