THIS PROBLEM HAS RETURNED!
CURL ERROR: SSL certificate problem: unable to get local issuer certificate
Yesterday, working in the sandbox was fine (I've been working fine all week long), then this morning I started testing again, and first thing I get is this message!
I've done a quick search and found a couple of articles referencing this back in 2015, but it was supposedly solved.
Is anybody else having this problem? How did you fix it? BTW, I have not changed anything on my system since yesterday when it was working fine.
Regards,
Dan Luevano
Solved! Go to Solution.
โ03-22-2018 07:57 AM
Same issue for me.
I'm using composer so the cert.pem file was at vendor/authorizenet/authorizenet/lib/ssl/cert.pem.
Took me a second to catch on...
Hopefully, we get fair warning next time.
โ03-23-2018 05:48 PM
We apologize for the serious inconvenience faced by all the Sandbox developers.
Sincerely
Ashutosh Singh
โ03-24-2018 10:43 AM
We apologize for the serious inconvenience faced by all the Sandbox developers.
Sincerely
Ashutosh Singh
โ03-24-2018 10:48 AM
Could this SSL change have effected other platforms, like .NET or the .NET SDK? Most of the talk has been around Curl and the PHP SDK. I'm using a System.Net.HttpWebRequest and 5% of my transactions respond with 500 internal server error, while through postman they are all fine and none of them fail. I was sandbox testing in February for my Hosted CIM deprecation - Accept Customer upgrade - everything was fine in February, but now i'm seeing some random failures this week.
โ03-26-2018 03:46 PM
Updating the cert worked for me too!
โ04-03-2018 06:35 AM
Hi do we need to rename cacert.pem to cert.pem.
I still cannot getting to work by replacing cert.pem with cacert.pem.
Is there anything else I need to do?
Thanks.
โ04-08-2018 11:34 AM
Hello I tried to do this anc cannot get it to work.
Is there anthing else that is needed to be done other than replacing cert.pem with cacert.pem?
I also tried to rename cacert.pem to cert.pem after copying in ssl forder and no luck as well.
Can someone help please. Thanks.
โ04-08-2018 11:40 AM
โ05-15-2018 09:53 AM
I have a plugin that uses the SDK and I had to update the cert.pem file so that it work on a few sandbox account.
Will the latest cert.pem file from GitHub work across all sandbox and production accounts?
Is it safe to update my plugin to use the latest cert.pem file?
Can you confirm this file will work across all sandbox and production accounts?
Thanks!
โ05-15-2018 09:57 AM
Thank you! The link to http://curl.haxx.se/ca/cacert.pem is now broken, but replacing lib/ssl/cert.pem with the one currently on Github fixed this issue for me. It is working for me on both sandbox and production accounts.
โ11-09-2018 09:15 AM - edited โ11-09-2018 09:16 AM