Viewing 5 replies - 1 through 5 (of 5 total)
  • I’m having the same issue. Been talking to Mailchimp and my webhost about it and I’ve been told by Mailchimp that my IP (dedicated) has been blocked by Akamai… which blocks the API calls before they even hit the Mailchimp API.

    No clue why they would’ve blocked it. I emailed Akamai customer care but I’m not sure if they even respond to this type of thing.

    Changing my IP may not fix the issue because I don’t know why it got blocked in the first place. So my new IP might get blocked too.

    Strange that there have been a few of us posting about this same issue here just in the past few days.

    The other solution that people have posted in these support forums is: Configure your server to connect to the MailChimp API server using a proxy… but I’m not sure how to do that.

    And this is the response from Akamai:

    We can’t currently assist and process further your request,

    We warmly invite you to get in touch directly with a Support Technician or an Account Representative from Mailchimp to evaluate your request,

    If it will be necessary, then an authorized Account Mailchimp Representative will approach Akamai if a change is needed to be performed.

    Plugin Contributor Lap

    (@lapzor)

    Peezey, you must have gotten 403 error, that indeed means the firewall blocked your servers IP. That can happen on a shared hosting server as you share the IP with many other users and have no control over what they do.

    @tom, another possible reason is an outdated cURL version.

    Here is more information about the different possible reasons for connectivity reasons:
    https://mc4wp.com/kb/solving-connectivity-issues/

    Please let me know if you need more information on this.

    I have the same issue.
    I have issue to connect my WP.org websites to MailChimp.
    I use MailChimp since few years and this is first time I have this issue.
    I have noticed that on my website the status is Not Connected and above message – Service Unavailable.
    RPT_MailChimpIssue.docx
    I have this issue on redpointtailor.com and other new pages – victorvolkers.com and wiktoria.nl
    I created new API key – hoping it would help – NO.
    I put the MailChimp form directly on the website to test – error.
    All set up SignUp forms by Bloom plugin seams to work but there are no new singups on my Maichimp list.
    Thanks for your help.
    Rgds., Beata

    I’ve resolved the issue ??

    This was the response from Mailchimp after discussing the Akamai IP blocking:
    I just got a response back from my colleague after running a special search through Akamai’s logs and here is the information that we were able to gather over the course of logs that were gathered over the past two days.

    Through Akamai’s logging, we were able to gather that there were “brute force” attempts to login to your “WordPress” page. I wouldn’t be able to go into a specific number in regards to these login attempts, but we were able to see that there were many. Additionally, we are seeing that there was a large number of .php extensions that were attempting to gain access across a multitude of non-PHP applications from this IP address. Because we get these logs from Akamai, we wouldn’t be able to go into specifics regarding the names of the applications, but we are able to see this as an error message from their logging.

    Because of the reasons mentioned above, we would need for your web host to change the dedicated IP address for your website in order to avoid this Akamai issue that you are seeing when attempting to use MailChimp for WordPress. I recommend forwarding this email over to your web host as this may help answer some of their questions.

    Response from my web host:
    Your website IP is on a dedicated IP however your MailIP and the IP of the server itself is shared. From the error’s you provided, it appears you are making an API call using cURL. cURL is a command that essentially grabs a files from a remote server. cURL will use the server’s IP to make an outbound connection rather than the websites IP. This being said the best way to resolve this issue is by moving you to another server.

    This most likely happened due to another website on the system becoming compromised. Once the website was compromised a bot or hacker attacked something Akamai was defending and as such Akamai blocked the IP address of your shared server. As such moving you to another shared server is a temporary fix. If you want to prevent this from happening again I strongly recommend upgrading to a VPS plan. In a VPS your server IP is your own. This means that another account can’t effect your website’s functionality or email.

    They moved my website to another server and everything is fine now.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘API not connected’ is closed to new replies.