Troubleshooting
Mailchimp WordPress Plugin Not Working? How to Fix Signups and Connection Errors

Short answer
When a Mailchimp plugin for WordPress stops working, the cause is usually a revoked or wrong API key, the wrong audience selected, subscribers waiting on double opt-in confirmation, or your server failing to reach the Mailchimp API. Check the plugin's connection status, test a signup, then read the plugin's debug log for the exact error Mailchimp returned.
Key takeaways
- Most failures come from the API key, audience choice or double opt-in.
- Pending subscribers have not confirmed yet; they are not missing.
- The plugin's debug log shows the exact error Mailchimp returned.
- Server timeouts and blocked outgoing requests can stop all signups.
- Caching, security plugins and JavaScript conflicts can break form submissions.
Why is my Mailchimp WordPress plugin not working?
Most Mailchimp plugin problems come from a broken API connection, the wrong audience, double opt-in confirmation, a server that cannot reach Mailchimp, or a conflict that stops the form from submitting.
Start by deciding which symptom you have. The fix for a plugin that shows “Not connected” is different from a form that connects fine but adds nobody.
| Symptom | Likely cause | First check |
|---|---|---|
| Plugin says not connected | Invalid or revoked API key | Create a new key |
| Form submits, no subscriber | Wrong audience or double opt-in | Audience settings and pending list |
| Form spins or does nothing | JavaScript or caching conflict | Browser console and cache |
| Error message on submit | Mailchimp rejected the address | Plugin debug log |
| Timeout errors | Server cannot reach the API | Outgoing requests and cURL |
This guide uses the popular Mailchimp for WordPress plugin, often called MC4WP, as the main example. The same checks apply to most Mailchimp integrations.
If you have not set the connection up yet, follow our guide on how to add Mailchimp to WordPress first.
How do you fix the API key connection?
Create a fresh API key in your Mailchimp account, paste it into the plugin's Mailchimp settings, save, and confirm the status changes to connected before testing a form.
Mailchimp's help page about API keys explains where keys are created and that a disabled or deleted key stops every integration using it.
Keys break more often than people expect. Someone may have cleaned up old keys, the account owner changed, or the key belongs to a different Mailchimp account.
Copy the whole key, including the part after the dash. That suffix identifies your Mailchimp data centre, and a cut-off key will not connect.
After saving, most plugins have a button to renew or refresh the cached list of audiences. Click it so the plugin loads your current audiences and fields.
Why are subscribers not showing in Mailchimp?
Subscribers usually are not missing: they are either waiting to confirm a double opt-in email, going to a different audience, or being rejected by Mailchimp for a reason the plugin logs.
With double opt-in turned on, people appear as pending until they click the confirmation link. Check the pending contacts in your audience before assuming signups failed.
Confirmation emails can land in spam or promotions folders. Test with your own address and look in every folder.
If the form is linked to an old or test audience, new contacts go there instead. Open the form's settings and confirm the selected audience matches the one you check in Mailchimp.
When you connect a form plugin instead, such as in our guide on connecting WPForms to Mailchimp, check the audience inside that form's Mailchimp integration too.
How do you read the plugin's debug log?
Open the plugin's debug or log screen, submit a test signup, then read the newest entry, which normally shows the exact error message Mailchimp sent back.
In MC4WP, the log is found under the plugin's other settings. Other integrations keep similar logs, or record errors in the WordPress debug log.
If your plugin has no log, turn on WordPress debugging. Our guide on enabling debug mode in WordPress shows the settings to add to wp-config.php.
The WordPress developer handbook page on debugging in WordPress explains each debug constant and where the log file is saved.
What do common Mailchimp errors mean?
Most errors mean Mailchimp refused the request: the contact already exists, the address looks fake, the person unsubscribed before, a required field is missing, or the API key is invalid.
| Error | What it means | What to do |
|---|---|---|
| Member exists | Address is already on the audience | Enable updating existing subscribers |
| Looks fake or invalid | Mailchimp rejected the address | Test with a real address |
| Forgotten email | Contact was permanently deleted | Contact must re-subscribe via a Mailchimp form |
| Required field missing | A merge field is required | Add the field or make it optional |
| API key invalid | Key deleted, disabled or mistyped | Create and save a new key |
Mailchimp documents these responses in its Marketing API error glossary. Use it to look up any code your log shows.
Required merge fields catch many site owners out. If the audience requires a last name or address that your form does not collect, every signup fails.
How do you fix timeout and connection errors?
Timeout errors mean your server could not reach the Mailchimp API in time, so check your host's outgoing request rules, firewall, SSL certificates, PHP cURL extension and DNS resolution.
WordPress plugins talk to Mailchimp through outgoing HTTPS requests. Some hosts and security plugins block or slow those requests.
A common message is a cURL timeout. Our guide on fixing cURL error 28 covers the server-side checks in detail.
The official libcurl error codes list helps you decode other cURL numbers that appear in logs.
If other plugins also fail to reach outside services, ask your host whether outgoing connections are restricted. Site Health can also flag REST API and loopback problems.
Can caching or security plugins break signups?
Yes. Cached pages can serve expired security tokens, minified or delayed JavaScript can stop the form script, and firewalls can block form submissions or outgoing API calls.
Exclude your signup page from page caching while you test. Then clear every cache layer, including any CDN.
Our guide on how to clear cache in WordPress lists the cache layers most sites have.
If you use JavaScript delay or combine features in a speed plugin, exclude the Mailchimp plugin's scripts and test again.
Security plugins and web application firewalls sometimes flag form posts. Check their logs for blocked requests at the time of your test.
How do you check for plugin conflicts?
Temporarily switch to a default theme and deactivate other plugins on a staging copy, then test the form after each change to find which one breaks it.
Open the browser console on the signup page before you start. A red JavaScript error often names the plugin or theme file causing it.
Our guide on how to fix a plugin conflict walks through a safe testing order that avoids breaking the live site.
Keep the Mailchimp plugin, WordPress and PHP up to date. Old plugin versions can fail after Mailchimp API changes.
Are emails from WooCommerce or other plugins affected?
Store and form integrations have their own Mailchimp settings, so a working signup form does not guarantee that WooCommerce, checkout opt-ins or form add-ons are syncing correctly.
Check each integration separately. Look at its own connection status, audience and sync log.
E-commerce syncs can take time on large stores. A first sync may run in the background for a while before all customers appear.
How do you prevent Mailchimp problems in the future?
Use one dedicated API key per site, test a signup after every update, keep double opt-in and required fields in mind, and check the plugin log whenever subscriber numbers look low.
Name API keys clearly in Mailchimp, such as by site name. That stops someone deleting a key they think is unused.
Set a simple monthly check. Submit a test signup, confirm it, and make sure it appears in the right audience with the right tags.
If list growth matters to your business, our guide on growing an email list with WordPress covers forms and placements that keep signups coming.
Frequently asked questions
Why does my Mailchimp plugin say not connected?
The API key is usually wrong, incomplete, disabled or deleted. Create a new API key in Mailchimp, paste the full key into the plugin, save and refresh the list of audiences.
Why are new subscribers pending in Mailchimp?
Double opt-in is turned on. Contacts stay pending until they click the confirmation email, which may land in spam or promotions folders.
What does the member exists error mean?
The email address is already on the audience. Enable the plugin option to update existing subscribers if you want repeat signups to update their details.
Can caching stop Mailchimp forms from working?
Yes. Cached pages, delayed JavaScript and firewalls can all stop form submissions. Exclude the signup page from caching and clear every cache layer when testing.
Where can I see Mailchimp plugin errors?
Most Mailchimp plugins have their own debug log. If yours does not, turn on WordPress debugging and check the debug log after a test signup.
Sources
- Mailchimp for WordPress WordPress.org Plugins
- About API keys Mailchimp
- Errors Mailchimp Developer
- Debugging in WordPress WordPress Developer Resources
- libcurl error codes curl
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


