Hi Kodran,
Could you run the test command again but with a lowercased -v option instead? I’d love to see the output to troubleshoot this issue.
curl -v https://us1.api.mailchimp.com/3.0/?apikey=test
Thread Starter
Kodran
(@kodran)
Thanks for the quick response. Here is the output:
curl -v https://us1.api.mailchimp.com/3.0/?apikey=test
* About to connect() to us1.api.mailchimp.com port 443 (#0)
* Trying 23.15.114.165… connected
* Connected to us1.api.mailchimp.com (23.15.114.165) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
* Server certificate:
* subject: CN=*.api.mailchimp.com,OU=Rocket Science Group,O=ROCKET SCIENCE GROUP,L=Atlanta,ST=GA,C=US
* start date: Sep 22 14:39:14 2015 GMT
* expire date: Sep 22 14:39:13 2016 GMT
* common name: *.api.mailchimp.com
* issuer: CN=Verizon Akamai SureServer CA G14-SHA2,OU=Cybertrust,O=Verizon Enterprise Solutions,L=Amsterdam,C=NL
> GET /3.0/?apikey=test HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: us1.api.mailchimp.com
> Accept: */*
>
< HTTP/1.1 401 Unauthorized
< Server: nginx
< Content-Type: application/problem+json; charset=utf-8
< Content-Length: 233
< X-Request-Id: 682b013d-ced6-471c-b305-2962c6a6eb1d
< Link: <https://us1.api.mailchimp.com/schema/3.0/ProblemDetailDocument.json>; rel=”describedBy”
< Date: Mon, 30 Nov 2015 10:46:06 GMT
< Connection: keep-alive
< Set-Cookie: _AVESTA_ENVIRONMENT=prod; path=/
<
* Connection #0 to host us1.api.mailchimp.com left intact
* Closing connection #0
{“type”:”http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/”,”title”:”API Key Invalid”,”status”:401,”detail”:”Your API key may be invalid, or you’ve attempted to access the wrong datacenter.”,”instance”:””}
I see I get an 401 Unauthorized, but I have no clue why.
Thread Starter
Kodran
(@kodran)
Update:
Ok, so I maybe onto something here. If I use my api key I get:
“title”:”Wrong Datacenter”,”status”:403,”detail”:”The API key provided is linked to a different
But if I do the curl like this:
curl -v https://us11.api.mailchimp.com/3.0/?apikey
I get the response ok.
I don’t know what the difference is between the us1 and us11 servers.
My question is, can I configure the plugin to use the us11 server?
Thanks
Hi Kodran,
If you configure your API key then the plugin will automatically use the correct datacenter for you.
If the plugin is showing the 403 forbidden response it usually really means that you’re blocked by Akamai, the firewall that MailChimp is using. You could contact MailChimp about this as they are able to check this for you.
Are you running the curl .... command check from the same computer your website is hosted on or from your own computer?
Thread Starter
Kodran
(@kodran)
Update 2:
Just checked the plugin and now it says “Connected”.
I don’t know what happened but now it seems to be working.
Thank you for your support and good luck with further development. I think this is a really solid plugin.
