The API was working weeks ago was created almost 2 years ago. I created a new API key just now. It is not working either.
Hey @2bearstudio,
Thanks a ton – I’m currently looking into this in detail as it seems this is affecting other people as well.
Question: are you hosted at HostGator or GoDaddy?
Hey @2bearstudio,
Thanks a ton – I’m currently looking into this in detail as it seems this is affecting other people as well.
Question: are you hosted at HostGator or GoDaddy?
The site is hosted by Site5, not HostGator or GoDaddy.
Thanks 2bearstudio, that makes this a bit weird but I’m digging into this with all I got.
Do you have command line access to your server by any chance? If so, can you run the following command to see what it gives you?
openssl version
cURL SSL version: OpenSSL/1.0.2d
I got this off another plugin.
Weird, at command line, here is what I got:
OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
Hi 2bearstudio,
That last version is definitely out of date and more importantly: vulnerable to the Heartbleed injection.
In any case, I think I pinned down the connectivity issues to an update in the MailChimp API server security which made it stop working with old versions of OpenSSL. Therefore, I have good hopes that updating OpenSSL will fix the issue for you.
Updating OpenSSL is really a matter of minutes for your webhost.
Let me know if that fixes it please. Your webserver might have to be restarted for the changes to take effect, but your webhost will know.
Really appreciate your prompt response to this matter. I am contacting the hosting company for this now. Will update here once I got an answer.
Thanks A MILLION!
Update: My server IP is banned by MailChimp.
Don’t understand, but only solution is to contact MailChimp.
Hey 2bearstudio,
Is that what your host tells you? That could definitely be it although I’ve never heard of it before.
What does running the following command from your server give you?
curl -v https://us1.api.mailchimp.com
If it gives you a bunch of text with “200 OK” in it, your server IP isn’t the issue here..
Thanks, @danny van Kooten.
I don’t get any 200 OK.
Here is what I got from the command:
curl 7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz
Sorry, I messed up the command. The uppercase V should have been a lowercased v.
curl -v https://us1.api.mailchimp.com
That command still tells us that your CURL version + OpenSSL version are both severely outdated though. Really something your hosts should fix, regardless of whether they think you’re blacklisted on MailChimp’s side. Your CURL version for example is nearly 10 years old.
I don’t get any 200 OK.
You know what, I am like a ball. The host says:
“As for openSSL, while indeed it is older, it is definitely the most secure, patched on a systematic basis, to ensure top notch security on the servers.”
I don’t like being kicked from one support to another. If they are as good as you guys, this should really be a simple problem to resolve.
But good for me, I am removing this company off my recommended hosting list.
Thank you for all your help. I will move my site to another server, and test it again.
Hey there,
I’m sorry to hear that you have to go through all that but I think you will definitely benefit of it in the long run.
Webhost issues are the worst, and while profit margins are low in that sector they shouldn’t sacrifice on quality or support to make it. =/
You’ll see that switching hosts gets rid of the issue right away. Promise. 🙂
