HTTP Error: SSL: CA certificate set, but certificate verification is disabled

Did you ever find a solution to this?
I am having the same issue trying to work locally.

No, I did not unfortunately. I just had to work around it.

Hey guys,

Sorry for the late reply but this is quite a hard one to debug, it seems to be an issue with certain versions of PHP CURL. Does any of you by any chance know what version you’re on?

Thanks in advance!

It was a few month now so I don’t know if the bug is still there but it probably is.
I don’t have time to check on it right now so I’ll just send you the version I’m running and I’ll test it in a few hours when I’m back.

$ curl --version
curl 7.40.0 (x86_64-apple-darwin14.0.0) libcurl/7.40.0 OpenSSL/1.0.2 zlib/1.2.8 libidn/1.29
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets

Array
(
    [version_number] => 468225
    [age] => 3
    [features] => 33469
    [ssl_version_number] => 0
    [version] => 7.37.1
    [host] => x86_64-apple-darwin14.0
    [ssl_version] => SecureTransport
    [libz_version] => 1.2.5
    [protocols] => Array
        (
            [0] => dict
            [1] => file
            [2] => ftp
            [3] => ftps
            [4] => gopher
            [5] => http
            [6] => https
            [7] => imap
            [8] => imaps
            [9] => ldap
            [10] => ldaps
            [11] => pop3
            [12] => pop3s
            [13] => rtsp
            [14] => smtp
            [15] => smtps
            [16] => telnet
            [17] => tftp
        )

)

Still the same error.

I tested sending the same thing in the terminal:
curl -X POST --cacert ca-bundle.crt -H "Content-Type: application/x-www-form-urlencoded; charset=UTF-8; Content-Length: 53" --data "body: limit=100&apikey=13456789123456789-us9" https://us9.api.mailchimp.com/2.0/lists/list.json

And that worked

Hi Patrik,

That CURL version is definitely up to date, so no issue there it seems. We’ve just pushed out an update of the plugin that should fix this issue.

Please let us know if it doesn’t – although I’m fairly certain it will. ??

Hi Danny. Yes it works beautifully now! Thanks!