Plugin Contributor
Lap
(@lapzor)
Hi,
The “Service Unavailable” is a pretty general error that always has to do with network and/or connection issues between your server and MailChimp.com.
Please note that we can not rely on the debugging we did 6 months ago, even if the error message is the same, the problem might be different.
I understand you ran cURL via SSH on your hosting server and that “just worked”, or did you run the cURL command locally or on another internet connection?
What hosting provider are you using? We have seen some hosting providers route all outbound cURL traffic over 1 shared IP (not the servers IP) and of course if that IP is blocked a big chunk of users from this big “WordPress hosting” provider will be blocked at once. Using SSH to run cURL will route it over the servers IP making it hard to debug the problem.
How did you confirm with Akamai that the IP being used to make cURL calls from your hosting server via Apache is not blocked?
Do you see any error in your MailChimp.com account when you go to Account – Settings – Extra – API (bottom of the page you see the last API calls and their result).
Do you see any error in the log on the “Other” page of our plugin?
If you SSH into the server and run cURL command with your server number and API key, do you get any error?
Is it GoDaddy?
Thank you for letting me know,
Thanks for the response, and understood on debugging in the past.
I did run the cURL via SSH on my hosting server, and it does connect. Here’s what it comes back with:
* Trying 69.192.40.21...
* Connected to us1.api.mailchimp.com (69.192.40.21) port 443 (#0)
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* NPN, negotiated HTTP1.1
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Unknown (67):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* Server certificate:
* subject: C=US; ST=Georgia; L=Atlanta; O=The Rocket Science Group, LLC; OU=IT; CN=*.api.mailchimp.com
* start date: Mar 8 00:00:00 2017 GMT
* expire date: Jun 7 23:59:59 2018 GMT
* subjectAltName: us1.api.mailchimp.com matched
* issuer: C=US; O=GeoTrust Inc.; CN=GeoTrust SSL CA - G3
* SSL certificate verify ok.
> GET /3.0/?apikey=[____REDACTED____]-us10 HTTP/1.1
> Host: us1.api.mailchimp.com
> User-Agent: curl/7.45.0
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< Server: openresty
< Content-Type: application/problem+json; charset=utf-8
< Content-Length: 210
< X-Request-Id: 040b22f7-e6f0-4903-b751-7fb66495acbf
< Link: <https://us1.api.mailchimp.com/schema/3.0/ProblemDetailDocument.json>; rel="describedBy"
< Date: Wed, 28 Jun 2017 18:37:10 GMT
< Connection: keep-alive
< Set-Cookie: _AVESTA_ENVIRONMENT=prod; path=/
<
* Connection #0 to host us1.api.mailchimp.com left intact
I’m hosted by Dreamhost.
I confirmed out host IP with Akamai – that it is not blacklisted.
Mailchimp.com account has zero API calls in the last 5 days.
MC4WP Other > has a ton of ERROR: Form 1274 > MailChimp API error: 503 Service Unavailable.
Plugin Contributor
Lap
(@lapzor)
Hi,
I noticed the URL is us1.api.mailchimp.com but your API key ends with 10.
Right now you get 403 forbidden because the API key is not allowed for US1 (only for US10).
Please test to your own API server, us10.api.mailchimp.com and check the result for “Akamai” to confirm it’s indeed the firewall from MailChimp.com.
Plugin Contributor
Lap
(@lapzor)
And again I’m still curious HOW you confirmed your host IP with Akamai – that it is not blacklisted.
Plugin Contributor
Lap
(@lapzor)
I’ve closed this ticket as there have been no replies for awhile.
If you are still having this problem or experience a similar issue please open a NEW topic.
Thank you!
