cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Getting relay response timeout with DPM method and WooCommerce

I'm using WooCommerce as my shopping cart and the official Authorize.net DPM payment gateway from WooThemes to process payments. Everything was working well until recently. Now, when a user submits the pay form, the page hangs for sometime and then they get an error message saying that Authorizet.net was unable to notify the merchant about the transaction.

 

The transactions are successfully authorized and captured and WooCommerce shows the orders as paid, but the error messages are very upsetting to our users.

 

From my reading it seems like the relay response is timing out. I have read the following posts on debugging this issue, but I haven't found a solution yet.

 

- https://support.authorize.net/authkb/index?page=content&id=A663

- http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Relay-Response-Basics-a...

 

The only thing in those articles that I'm not sure about is the SSL cert. Is there a way to check if a site's cert is acceptable to Authorize.net's server? There are so many different ciphers and signature algorithms that it's difficult to tell if my cert is the problem or not.

 

I have looked through my server logs and I see POST requests from Authorize.net IPs for the transactions and the logs show HTTP 200 responses, so it doesn't looke like a firewall is blocking the connection.

 

Any additional help or ideas would be appreciated.

Dominic
Member
1 ACCEPTED SOLUTION

Accepted Solutions

I finally figured this problem out. The issue was that the transactional emails for the order are sent during the relay response and a configuration error was causing the email script to hang (which caused the relay response request to time out).

 

Thanks for the help in debugging it.

View solution in original post

Dominic
Member
5 REPLIES 5

Hello @Dominic

 

One tool you might consider is https://www.ssllabs.com/ssltest/ as it does a good job if diagnosing issues.

 

You might also submit a support request at http://developer.authorize.net/support.  Be sure to include your relay response URL so we can test it.

 

Richard

RichardH
Administrator Administrator
Administrator

Hi @RichardH

 

Thanks for the helpful reply. I tested my domain with ssllabs.com/ssltest. It reported an A grade, but it noted that the Signature Algorithm (SHA1withRSA) is considered weak. Do you think this would be enough to cause Authorize.net to refuse to connect on the relay response request?

 

I will go ahead and submit a support ticket on the developer site. I wasn't aware that was an option.

 

Dominic

I finally figured this problem out. The issue was that the transactional emails for the order are sent during the relay response and a configuration error was causing the email script to hang (which caused the relay response request to time out).

 

Thanks for the help in debugging it.

Dominic
Member

I am receiving the same error message as you did.  Can you share specifically what type of configuration problem caused the issues and what did you do to resolve the problem.

 

TIA 

 

Alan

 

Hi Alan, basically I was connecting to the wrong port on my SMTP server which caused the connection to hang. Eventually, the relay response requested timed out while my server was trying to connect to send the transactional emails. All I had to do was correct the port and it worked.

 

As a side note, I don't think it's a great idea to send the emails during the relay response. It seems to me that the relay response is a critical phase of the transaction and non-essential operations should be done at another time. So, I made my emails asynchronous, so now they are only scheduled to send on the relay response, and they actually send a few seconds later.