topic Re: Getting a "timeout" error on Relay Response in Integration and Testing

Getting a "timeout" error on Relay Response

kevin2r2sours — Wed, 30 Jan 2019 19:36:28 GMT

I'm trying to get a DPM integration working with the new hash requirements. I know I need to upgrade to the newer approach, but I need to get this working before I dig into that. The problem is that I can't get my development site talking to the sandbox.

I get the standard opaque "timeout" error. Based on the speed of response, it's not timing out, but this appears to be a generic "something went wrong with the connection" error.

Because of security concerns the development box is behind a firewall, but I've whitelisted the IPs found here:

198.241.206.38
198.241.207.38

https://support.authorize.net/s/article/Authorize-Net-Domains-and-IP-Addresses

I've read https://support.authorize.net/s/article/Why-Are-My-SIM-Relay-Response-Transactions-Timing-out-After-Submitting-the-Request and done everything I can think of there (including removing the query string from my relay url.

The problem is that authorize.net is not calling my webserver after a submission. However I'm at a loss on how to troubleshoot this further since a.net doesn't provide a real error message nor can I find a tool that would determine why the connection is failing.

I'm posting here because after pointing me to articles I told them I already reviewed, a.net support told me to post here because "as we are not trained to review your code".

Anybody know how to troubleshoot this?
Kevin

Re: Getting a "timeout" error on Relay Response

RichardH — Wed, 30 Jan 2019 20:16:46 GMT

Hello @kevin2r2sours

You might check first to ensure your URL is publicly available and on standard ports 80 or 443, otherwise it will continue to fail.

Richard

Re: Getting a "timeout" error on Relay Response

kevin2r2sours — Wed, 30 Jan 2019 20:21:59 GMT

As I've mentioned it's not publicly available. And my admins are not going to approve that for a test site. I *have* allowed access to the mentioned IP addresses for authorize.net.

Further conversation with support suggests that the problem is that I'm using an http link for the relay url. Nothing in the documentation suggests this is a requirement (I'm using https to connect to authorize.net) but if that's the case at least its an answer (requiring a properly signed certificate for a *test* server is seriously annoying but whatever).