topic Secure2 Transistion in Integration and Testing

Secure2 Transistion

mlunn01 — Fri, 29 Apr 2016 00:33:19 GMT

Started transistioning an app running on IIS 7.5 Windows 2008 Server over to the new Akamai infrastructure. For whatever reason, the server to server communication is failing with the following error message:

"No connection could be made because the target machine actively refused it 23.10.117.178:443"

I checked with our firewall admin and the IP is not being blocked. We are able to connect to secure.authorize.net. Does anyone have any insight on this error? Could this be a server certificate issue?

Re: Secure2 Transistion

RaynorC1emen7 — Fri, 29 Apr 2016 12:23:06 GMT

try the url on a web broswer on the server

Re: Secure2 Transistion

Lilith — Fri, 29 Apr 2016 17:23:05 GMT

If you're able to capture the HTTP body, there may be a Reference # there, which we could use to trace the issue.

If you do find a Reference #, post that here along with your server IP address, and the timeframe when this occured, please.

Re: Secure2 Transistion

mlunn01 — Fri, 03 Jun 2016 17:44:21 GMT

I was testing this again last week and was able to establish a successful connection. However, I did more testing today and are getting the the error message again. I've captured traffic, which does me know good over 443.

Re: Secure2 Transistion

mlunn01 — Fri, 03 Jun 2016 17:45:27 GMT

I'm afraid this may not be resolved before june 30th. Will the old URLS still work after this cut off date?

Re: Secure2 Transistion

RaynorC1emen7 — Fri, 03 Jun 2016 21:51:54 GMT

on June 30th, the old url will use Akamai too

https://community.developer.authorize.net/t5/Integration-and-Testing/Integrate-Akamai/m-p/54784/highlight/true#M29743

And the faq

https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Akamai-SureRoute-Technical-FAQ/ba-p/54499

Re: Secure2 Transistion

Lilith — Mon, 06 Jun 2016 17:55:25 GMT

We've got an announcement coming regarding the Akamai SureRoute deadlines. I'll be able to elaborate more once the announcement is up.

For now, I'd really appreciate it if @mlunn01 could provide the HTTP response in full, since there is likely a Reference # there that can help us troubleshoot.