Skip to content

Troubleshooting CURL Errors

Jump to bottom
khungate edited this page Jul 25, 2023 · 4 revisions

Troubleshooting CURL Errors

Welcome to the guide on Troubleshooting CURL Errors in the MailChimp for WooCommerce Integration. This guide will help you understand how to diagnose and resolve issues when your server can't communicate with Mailchimp.

Overview

Server Communication Issues

Servers can occasionally be blocked by Akamai - Mailchimp's API gateway service. The most common reason for being blocked is when sites are being served from shared hosting environments.

Testing Server Communication

Steps

  1. Connect to your server's SSH terminal and run the following CURL command:
curl -v -X GET https://{$DATA_CENTER}.api.mailchimp.com/3.0/ecommerce/stores?apikey={$API_KEY}

Replace {$DATA_CENTER} with your actual data center at Mailchimp. You can see it in your API key. Replace {$API_KEY} with your actual API key from Mailchimp.

  1. Execute the command.

  2. Copy the results and xxxx out your API key.

  3. Use this copied text in your support chats with Mailchimp.

Possible Outcomes

  1. You get a valid response 200 status code with a JSON response. This means your server itself can communicate with Mailchimp.

  2. You get an invalid response like a 500+ status code which means your server has been blacklisted by Akamai.

Resolving Issues

Resolving both outcomes often involves the same action, getting a dedicated IP address. Typically this resolves the connection instantly. In case your server is still having trouble after a dedicated IP address is added, please consider adjusting your settings.

Clone this wiki locally