SSL peer certificate or SSH remote key was not OK

[BrandonM]

I have a production site that worked fine with authorize.net up until about 2:00PM EST today. cURL is throwing back a "SSL peer certificate or SSH remote key was not OK" error when attempting to post data to https://secure.authorize.net/gateway/transact.dll.

I am the only developer on the site, and I have not logged in at all today until someone reported an issue where they could not complete their transaction. Can anyone provide me with any direction? I have tried restarting the entire device just for good measure. No luck.

[aniemi]

Strangely enough I was able o fix this problem by changing our DNS on the server from using OpenDNS to Google.

I'm not sure why/how, but it appears OpenDNS is having an issue.

HTH

[BrandonM]

Changing our DNS from OpenDNS to Google DNS resolved the issue for us yesterday as well. Could have saved you some troubleshooting by replying yesterday, but I was swamped. Not sure what to really make of this, but it worked.

[Lilith]

That's odd that OpenDNS was causing issues, but not Google DNS.

I did a cursory poke at the DNS A records showing up on both servers and compared it to my local DNS A records, and they show the same IP addresses, so I'm not sure where the discrepancy lies.

But I'm glad to know there is at least a workaround.


Aniemi, to answer your earlier question about curl: If you use the --verbose (-v for short) flag, it should dump every step of establishing the connection, including DNS lookup, SSL/TLS negotiation, and of course the raw HTTP data.

I find it sometimes useful to run "curl -v https://secure.authorize.net/gateway/transact.dll" to troubleshoot connection issues to us, and it may have exposed the OpenDNS issue you've now noticed.