Support » Plugin: Mailchimp for WooCommerce » Mailchimp says: API Request Error – cURL error 28: Operation timed out

  • Resolved Rasti WebKinder

    (@rastiwebkinder)


    Hello

    We encountered a problem with version 2.1.12 of the plugin.
    When we insert API key, after a longer time loading we get an error message:
    Mailchimp says: API Request Error – cURL error 28: Operation timed out

    This doesn’t happen when we install version 2.1.9 (which we could confirmed worked on another shop of ours).

    Our setup:
    PHP 7.2.14
    WordPress 4.9.9
    WooCommerce 3.5.1

    Thank you for help in advance.

    Best regards
    Rasti

Viewing 3 replies - 46 through 48 (of 48 total)
  • Plugin Support khungate

    (@khungate)

    @magicsun Sorry to hear you’re having issues, we definitely want to try to help out.

    Usually, when there are logs that reference things of this nature, it’s related to the server host preventing critical processes for the plugin to work correctly. As an initial troubleshooting attempt, you’ll want to reach out to them to ensure that they aren’t blocking admin-ajax.php in your WordPress install and the REST API is enabled.

    Would you care to check on those two first and report back? I look forward to hearing back from you.

    @khungate rest api is enabled.
    Everything works, except it won’t sync.

    When i visit [mysite]/wp-json/mailchimp-for-woocommerce/v1

    I get:
    {"namespace":"mailchimp-for-woocommerce\/v1","routes":{"\/mailchimp-for-woocommerce\/v1":{"namespace":"mailchimp-for-woocommerce\/v1","methods":["GET"],"endpoints":[{"methods":["GET"],"args":{"namespace":{"required":false,"default":"mailchimp-for-woocommerce\/v1"},"context":{"required":false,"default":"view"}}}],"_links":{"self":"https:\/\/www.vanrene.nl\/wp-json\/mailchimp-for-woocommerce\/v1"}},"\/mailchimp-for-woocommerce\/v1\/ping":{"namespace":"mailchimp-for-woocommerce\/v1","methods":["GET"],"endpoints":[{"methods":["GET"],"args":[]}],"_links":{"self":"https:\/\/www.vanrene.nl\/wp-json\/mailchimp-for-woocommerce\/v1\/ping"}},"\/mailchimp-for-woocommerce\/v1\/queue\/work":{"namespace":"mailchimp-for-woocommerce\/v1","methods":["GET"],"endpoints":[{"methods":["GET"],"args":[]}],"_links":{"self":"https:\/\/www.vanrene.nl\/wp-json\/mailchimp-for-woocommerce\/v1\/queue\/work"}},"\/mailchimp-for-woocommerce\/v1\/queue\/work\/force":{"namespace":"mailchimp-for-woocommerce\/v1","methods":["GET"],"endpoints":[{"methods":["GET"],"args":[]}],"_links":{"self":"https:\/\/www.vanrene.nl\/wp-json\/mailchimp-for-woocommerce\/v1\/queue\/work\/force"}},"\/mailchimp-for-woocommerce\/v1\/queue\/stats":{"namespace":"mailchimp-for-woocommerce\/v1","methods":["GET"],"endpoints":[{"methods":["GET"],"args":[]}],"_links":{"self":"https:\/\/www.vanrene.nl\/wp-json\/mailchimp-for-woocommerce\/v1\/queue\/stats"}},"\/mailchimp-for-woocommerce\/v1\/survey\/disconnect":{"namespace":"mailchimp-for-woocommerce\/v1","methods":["POST"],"endpoints":[{"methods":["POST"],"args":[]}],"_links":{"self":"https:\/\/www.vanrene.nl\/wp-json\/mailchimp-for-woocommerce\/v1\/survey\/disconnect"}}},"_links":{"up":[{"href":"https:\/\/www.vanrene.nl\/wp-json\/"}]}}

    Which looks fine, no errors.

    I’ve added this to my wp-config.php

    define('ALTERNATE_WP_CRON' , true );
    define('DISABLE_WP_HTTP_WORKER', true);
    define('MAILCHIMP_USE_CURL', true);

    This starts up the connecting process, makes the rest api error disappear. All the way up to last step: syncing. Then i get this error:

    2019-09-19T19:12:34+00:00 NOTICE sync.started :: Starting Sync :: Thu, Sep 19, 2019 7:12 PM
    2019-09-19T19:12:34+00:00 ERROR mailchimp_woocommerce_rest_api_get ::  :: 
    Plugin Author ryanhungate

    (@ryanhungate)

    @magicsun sorry for the delay – but you seem to have a configuration that would rely on having the WPCLI running in the background. Have you added the cron schedule as described in this wiki?

    https://github.com/mailchimp/mc-woocommerce/wiki/Advanced-Queue-Setup-In-CLI-mode

Viewing 3 replies - 46 through 48 (of 48 total)
  • You must be logged in to reply to this topic.