We're seeing a lot of this in our error log:
The connection to the gateway failed. Please try again later.
attempt:2
message:Unable to Connect to ssl://api.authorize.net:443. Error #113: No route to host
Are you having network issues?
Connect to ssl://api.authorize.net:443. Error #113: No route to host
Discussions are closed to public comments.
If you need help with Cheddar please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
#1 Posted by Marc Guyer Support staff on 21 Jul, 2010 07:11 PM
No network issues. We periodically experience some connectivity issues with the Authorize.Net API. That's why we've built in some fault tolerance to reattempt the connection up to 3 times before failing entirely. If you see an attempt:2 in the log but no attempt:3, then the 3rd attempt was likely successful. If the 3rd attempt fails, the CG api will return a 502:4000 error.
Marc Guyer closed this discussion on 21 Jul, 2010 07:11 PM.