- Issue created by @Anybody
- Status changed to Closed: works as designed
9 months ago 7:59pm 11 September 2024 - 🇺🇸United States xenophyle
Based on a web search of this phrase, this is an issue on the Mailchimp end of things and isn't related to the module.
- 🇩🇪Germany Anybody Porta Westfalica
@xenophyle I don't really agree. The API was used via the module and we did nothing special. Maybe the module simply sends too many requests and should better combine them in a timeframe or something like that?
I'd vote to reopen this.
- 🇺🇸United States bdimaggio Boston, MA
Hey there — this is a tricky one. We have seen it a couple of times (well, once → that I know of) over the years we've been maintaining the Mailchimp suite, but we've never successfully pinned down what causes it. I am encouraged that it has only made it to the issue queue that one time, but of course I'm sure that's no consolation for you.
To try and make more progress with it, let's get all the info we can.
- Can you paste here the entire error message you're seeing (including all HTML)?
- Did the problem definitively start at a certain point (e.g. after upgrading to a certain version of the module)?
- If you're not already using OAuth rather than an API key to authenticate, can you try that (admittedly, a shot in the dark)?
- 🇺🇸United States bdimaggio Boston, MA
Hey @anybody — just wanted to check on this. Should we assume the problem cleared up with a recent release, or...?
- 🇺🇸United States derekw
Just cropped up for me over the last couple days after working fine for years, and I'm using OAuth to authenticate.
It's hit and miss though -- on a page/function accessing the Mailchimp API, sometimes it will throw the "suspicious IP" error but reloading the page/re-sending the request it will work.
For example on the OAuth settings page I re-authenticated and have a "Authentication complete! Successfully connected to Mailchimp API" on that page... but if I reload the page... then I might see "Error, please re-authenticate" but if I reload the page once or twice it'll be happy again.
Possibly related, the website in question is hosted on Pantheon which uses dynamic IPs for outgoing requests. I'm guessing a Pantheon-hosted site was doing something that got that IP flagged by a database of suspicious IPs that Mailchimp relies on.
In short... I don't think this is a module issue but a problem with dynamic outgoing IPs on shared hosting. I see Pantheon has instructions for setting up a fixed-ip proxy for outgoing requests, I might have to look into that.