Support » Plugin: Mailchimp for WooCommerce » 500 error when trying to connect Mailchimp

  • Resolved funkyhomme



    I’m currently abroad, and each time I log into my Mailchimp account it’s asking for verification. For day-to-day use this is fine, but it’s causing problems when attempting to link Mailchimp and Woocommerce.

    After installing the plugin and clicking Connect, the pop-up login window opens. I enter my username and password, then the window closes, and the plugin page refreshes to a 500 error. I think this is happening because my login is not completing properly.

    Please can you advise on how I can link the two accounts? I will not be in my home country (where I don’t need to verify to log in) for a few weeks, and I cannot wait until then to have Mailchimp linked.

    Thank you,

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author ryanhungate


    @funkyhomme thanks for reporting this. If you’ve authenticated with the OAuth server successfully, then the next step is to see whether or not your web host has been blocked by Mailchimp’s API gateway service called Akamai.

    Here’s what we’ll need to do next. Please reference this post here and validate that this is not the reason you’re being blocked:

    Once you’ve done this, please let us know if you’re getting a successful response referencing the store information.

    We’ll look out for your reply and follow up after this is done based on what the outcome is.

    So the issue seems to be with Curl. It was not activated on the server, then when I installed it, all manner of problems popped up. I’ve had to uninstall and reboot.

    Silver lining though: in the brief window that Curl was installed, I got confirmation from the Mailchimp API…

    Not really sure how to proceed from here?

    Plugin Author ryanhungate


    @funkyhomme as current, CURL is required to communicate with the Mailchimp API in the plugin. Not really sure how installing CURL would have any negative side effect but anything is possible I guess.

    Unfortunately, there is not a workaround at this time, but we can put this on the roadmap for future discussions on using a different transport. CURL is just so common that it’s the right thing to do in 99.9% of all situations.

    Stay tuned for updates though and thanks for reporting your issue 🙂

    Hi again, Ryan,

    So I’ve got Curl installed and working on my server now, and I’ve worked through the steps in the Github link you sent across.

    Here is the response I received. I don’t think it references the store?

    * Trying…
    * TCP_NODELAY set
    * Connected to ( port 443 (#0)
    * ALPN, offering http/1.1
    * successfully set certificate verify locations:
    * CAfile: /etc/ssl/certs/ca-certificates.crt
    CApath: none
    * TLSv1.3 (OUT), TLS handshake, Client hello (1):
    * TLSv1.3 (IN), TLS handshake, Server hello (2):
    * 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, Change cipher spec (1):
    * TLSv1.2 (OUT), TLS handshake, Finished (20):
    * TLSv1.2 (IN), TLS handshake, Finished (20):
    * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
    * ALPN, server accepted to use http/1.1
    * Server certificate:
    * subject: C=US; ST=Georgia; L=Atlanta; O=The Rocket Science Group, LLC; OU=IT;
    * start date: Jul 9 00:00:00 2019 GMT
    * expire date: Oct 7 12:00:00 2020 GMT
    * subjectAltName: host “” matched cert’s “*.api.mailchimp .com”
    * issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA
    * SSL certificate verify ok.
    > GET /3.0/ecommerce/stores?apikey=[I’ve removed API key for security reasons] HTTP/1. 1
    > Host:
    > User-Agent: curl/7.69.0-DEV
    > Accept: */*
    * Mark bundle as not supporting multiuse
    < HTTP/1.1 200 OK
    < Server: openresty
    < Content-Type: application/json; charset=utf-8
    < Content-Length: 714
    < Vary: Accept-Encoding
    < X-Request-Id: 30698233-f420-4661-9432-b372b04463fb
    < Link: < son>; rel=”describedBy”
    < Date: Thu, 13 Feb 2020 06:32:27 GMT
    < Connection: keep-alive
    < Set-Cookie: _AVESTA_ENVIRONMENT=prod; path=/
    < Set-Cookie: _mcid=1.ae9975475c27a8555dab7a8a176a08f4.62d750f0feb63a04e648ddec1 fc97985561607529c290c3c669779089fb7daef; expires=Fri, 12-Feb-2021 06:32:27 GMT; Max-Age=31536000; path=/;
    * Connection #0 to host left intact
    {“stores”:[],”total_items”:0,”_links”:[{“rel”:”self”,”href”:””,”method”:”GET”,”targetSchema”:”https://us17.ap” },{“rel”:”parent”,”href”:”;,”method “:”GET”,”targetSchema”:” ommerce/Namespace.json”},{“rel”:”create”,”href”:” 3.0/ecommerce/stores”,”method”:”POST”,”targetSchema”:”https://us17.api.mailchimp .com/schema/3.0/Definitions/Ecommerce/Stores/Response.json”,”schema”:”https://us”}]}

    • This reply was modified 1 week, 1 day ago by funkyhomme. Reason: Removed API key
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.