Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 MailChimp Integration: Not working with Godaddy | Event Espresso - Staging Server
I keep getting the following error message when I enter the correct MailChimp API key via Site hosted at Godaddy.
An error occurred while attempting to connect to the MailChimp server. Error: Invalid Mailchimp API Key (631):
I spoke with both Godaddy and MailChimp.
Godaddy states they are not blocking access to the MailChimp Server. I did request that they move my site to another server with a different IP address.
MailChimp says that there is no issue on their end and to contact EE for support. They keep spitting blame at EE and ignoring the details I provide them via email.
The MailChimp Integration works just fine via my localhost dev server.
Well this isn’t something that is down to EE, I have noticed previously that Mailchimps servers can be temperamental sometimes when it comes to API calls.
Have you tried generating a new API key and trying that?
Have you asked Mailchimp if your sites IP has been blocked? (longshot)
Other than that you really need to keep poking MailChimp/Godaddy to look into it, as the add on from EE’s end is quite simple in what it does (call API, provide info, done.)
The support post ‘MailChimp Integration: Not working with Godaddy’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
This is the support forum for the Mailchimp integration for Event Espresso. You can get help with the add-on here from the Event Espresso team.