ryanhungate

Just to piggyback on what Kyle said, if you’re running into a problem and want to try to get records to sync faster, you can also use the --force option to get it to work. This is one of those situations where you might really need to consider a high performance action scheduler setup if you have lots of jobs in the queue that are not being handled properly. The documentation is on that wiki he mentioned too.

@juliemarie sorry to hear you’re having issues but it’s a little hard to know what the problem is from here. The “historical sync” you speak of is a very normal first step where you’re getting all your order and customer info into Mailchimp to be able to use this for segments and marketing etc. It’s not going to impact your site moving forward after completion, but yes we do understand it could be a little resource intense for some hosting environments. If you’ve got a large store to sync, it could be a good idea to look at your web hosting stack to see if it’s an appropriate size or if it needs to be adjusted.

The second concern seems like an email being sent from Mailchimp based on an order update? That should be something you are able to adjust inside your Mailchimp account. It sounds like you have an automation set up that you might not need?

As the plugin support side, we don’t have any insight to your Mailchimp account, but it would probably be best to reach out directly to your support while logged into your Mailchimp account and ask them to figure out which automation is firing and how to stop that. It should be a simple on/off/pause process that should fix that for you.

If we can help with anything plugin related please feel free to reach back out and we’ll be able to help.

@stevennorth glad to see you were able to use that wiki to solve the problem!

Yes that does highlight the problem being related to the IP address, but this is actually a very common problem while using a shared host. The way PHP works while making a CURL request typically just grabs the first IP address in the network on that machine and uses that as a default. I think in this case there’s a bad actor somewhere on that shared host which is being flagged at the API gateway level which is out of your control to fix ( shared hosting is like this )

In your case, you have a specific IP for your domain which resolves as expected on that server, but your server’s PHP config doesn’t automatically know to use it unless you specify it in the CURL options before making a request. This is why we have that IP config for that purpose.

The other plugin will have to do the same, but we don’t have any sort of control over how that plugin code works at all, and hopefully that gives them a clue as to how to resolve the problem.

@stevennorth this one could very well be related to an API gateway block if it’s a shared host as described. You can try a few things first before doing something drastic like getting a new dedicated IP address for this site. Please check out our wiki to see a few of the options available for troubleshooting this type of problem.

—-

@alekseiwailabs while the end result seems to be similar, these are 2 different issues. Your problem seems like there’s a caching problem where your “data center” isn’t being identified which would indicate that you might possibly need to clear any object caching you might have on your server. Were you able to log into Mailchimp’s authentication flow and set up your store properly, or did this just stop working all the sudden?

We’ll be happy to assist any way we can.

@mdczaplicki Thanks for reporting back, that’s good to hear.

@mdczaplicki it is a requirement that you have CURL installed on your server. This looks like something might have gone wrong with a recent PHP update on your machine? Can you please make sure that your hosting provider / server admin knows to have this running in your PHP build?

@dozza thanks for all the info on this – very helpful. v4.2.1 should address this problem you’re facing, so if that’s still a problem please let us know. I did just briefly look at the site and the plugin seems to load fine at this moment. If we can help with anything else just let us know!

@mikemackechnie are you having trouble with the mailchimp.com or the “chimpstatic” domains? You’re bringing up a very good point that we’ll be glad to get resolved if possible.

@liiam if it’s not too much trouble – you might want to re-install the plugin because it will start you off with a fresh database on the Mailchimp end. Typically the products would be deleted when you trash the products in your store, but if that didn’t happen for whatever reason, the easiest way to accomplish this is by re-installing the plugin and re-syncing things just like you first set it up.

@freshynathan 4.2.1 has been released, please let us know if that resolves your issues.

@macstevenw2013 @wineschoolofcheshire 4.2.1 has been released, please let us know if this resolves your issues. Thanks!

@sareejoh 4.2.1 has been released, please let us know if this resolves your problem. If we’re still having trouble we’ll be glad to help.

@sareejoh thanks for the info – we’re applying some patches right now that should resolve this in the version 4.2.1 so stay tuned and we’ll update here when complete.

ok @wineschoolofcheshire thank you for the error trace. We’re actively working on this fix now and will report asap when complete.

@freshynathan thanks for the report. We’ll get on this right away for a follow up patch and report back here.