@martijnn94 thanks for explaining that to @kingyyyy – we need to see whether or not @kingyyyy is using 2.1.16 version of the plugin for that new ‘rest api’ version.
When a server is not responding to a request that’s made to its own domain name, that typically means there is a configuration on the server that’s out of whack. Some CURL installations are set up in a way that might require you to set a specific IP address or even use localhost etc., so we’ve got some options for you if you’re in that situation as well.
First config option is to set define('MAILCHIMP_USE_CURL', true); in your wp-config.php file. This will make an attempt at using raw CURL vs. wp_remote_x calls. We’ve found that some plugins are indeed altering the core functionality of this function we rely on.
Second option is to make a change to the REST IP address that we will be calling. You may do that by specifying define('MAILCHIMP_REST_IP', 'your.ip.here');. You may also use localhost by specifying define('MAILCHIMP_REST_LOCALHOST', true); and we will use the localhost address to make http calls to your own server instead of your actual domain name.
Third option is that you might need to specify a particular TLS version. By default we’re using the CURL_HTTP_VERSION_1_1 but if for whatever reason you need to change that to something your server admins tell you to do, you may do so by adding in a config of define('MAILCHIMP_USE_LOCAL_CURL_VERSION', 'whatever');
We’re working really hard on finding solutions for all the possible server configurations, but in all fairness it’s a little hard to communicate these things without overwhelming most folks. If you don’t mind working with us to find your solution, we will get you where you need to be.
Please feel free to reach out to us again with questions, and if you are able to fix this using our tweaks listed above.
