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
Didn't work for me. Win7/XAMPP v3.2.2.
โ03-22-2018 04:33 PM
The sandbox was working for me until this morning. I checked the certs and they are all still good for years to come. It also broke on all of my 4 severs at the same time without any updates. And, it seems to have broken for lots of other people here all at the same time. I can use it if I disable SSL for curl, but this means directly modifying the API and, bigger issue, no security for transactions. At least I can keep testing, but it would be nice to hear from Authorize.Net about what to do about this sudden issue.
โ03-22-2018 05:08 PM
Well I was hoping this would be fixed this morning. Like everyone, I was cruising along fine until the suddenly stopped working yesterday. Small mod to the api got it working for now.
HttpClient.php , line 80, comment out:
curl_setopt($curl_request, CURLOPT_CAINFO, dirname(dirname(__FILE__)) . '/../../ssl/cert.pem');
This is NOT SECURE, not a permanent solution. I'm just testing so it lets me continue working.
So that cert is in a weird place, not sure where it came from. Was it part of the api install? I'm not cert savvy so I've got to wait for our sys admin to wake up and look at it.
โ03-23-2018 04:11 AM
OK, following a post on this thread:
https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net-Begins-I...
I replaced cert.pem with the file from
http://curl.haxx.se/ca/cacert.pem
and all seems well
โ03-23-2018 05:14 AM
This worked for me. Thanks!!!!!
โ03-23-2018 05:41 AM
Replacing the cert.pem also worked for me. Is this a solution or a patch/work-around?
โ03-23-2018 06:05 AM
Just to be clear about what's going on:
โ03-23-2018 07:18 AM - edited โ03-23-2018 07:21 AM
Thank you very much for your explanation! This is helpful. Now I know to also check the production side when I'm ready to go LIVE, and I'll know what to do if I encounter a problem.
Much appreciated!
Best Regards,
Dan Luevano
โ03-23-2018 07:25 AM
I'll chime in and say this worked for me as well. I had to modify one of the files in the API because I couldn't find a way to set the cert path with a function (it's hardcoded), but this made it work. Is this the solution? Do we know why the other stopped working. According to the date in the file it should have worked until May 2022 for the one I have.
I'm happy to have a fix, but it would be interesting to know why it broke suddenly for so many people.
Tom
โ03-23-2018 07:30 AM
Had the same issue this morning but fixed it by replacing the /lib/ssl/cert.pem with the one from http://curl.haxx.se/ca/cacert.pem
Thanks for all the tips and information in this thread!
โ03-23-2018 07:44 AM