api error after upgrade

  • Resolved mgdiazanton

    (@mgdiazanton)


    2 years, 8 months ago

    hello

    I am getting this error after updating today to 2.7.

    Mailchimp says: API Request Error – API is failing – try again. on 2203 in /home/u179704334/domains/oxfordtefl.com/public_html/wp-content/plugins/mailchimp-for-woocommerce/includes/api/class-mailchimp-api.php

    WC Version: 6.6.1
REST API Version: ? 6.6.1
WC Blocks Version: ? 7.6.2
Action Scheduler Version: ? 3.4.0
Log Directory Writable: ?
WP Version: 6.0
WP Multisite: –
WP Memory Limit: 2 GB
WP Debug Mode: –
WP Cron: ?
Language: en_US

    ******************************

    It looks like it is going to connect but then, it says try again.

    I have try with your support team, with no results.
    They say it is a problem with permissions, but I execute all the permissions and still having this problem.

    it is driving me crazy.

    Can you help?

    Otherwise, maybe I should go back to an older version, because this is a problem with THIS version 2.7

    thanks in advanced,

    gaby

    • This topic was modified 2 years, 8 months ago by mgdiazanton.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author ryanhungate

    (@ryanhungate)

    Hi @mgdiazanton,

    Can you please look through this wiki article and see if this is the problem?

    We’re not really sure of how this particular error would be happening on 2.7 vs. 2.6.2 because this is directly related to the CURL API requests being made and the HTTP status code was not greater than 99… which means the request didn’t succeed.

    I would also recommend possibly trying to set the outbound IP address on your install to see if this resolves the problem.

    Thanks!

    Thread Starter mgdiazanton

    (@mgdiazanton)

    Hello,

    I need to contact a developer to have a look for your suggestions.
    I’ll get back to you in few days.
    Don’t close the ticket yet please.

    Gaby

    Plugin Author ryanhungate

    (@ryanhungate)

    @mgdiazanton no problem.

    Plugin Author ryanhungate

    (@ryanhungate)

    @mgdiazanton just following up to see if you were able to add this line of code to your wp-config and if it resolved your issue?

    Plugin Author ryanhungate

    (@ryanhungate)

    @mgdiazanton if setting that value to your site’s IP address doesn’t resolve it, we’ve got a confirmation from someone who has your same exact problem that setting that config specific to this solved the problem.

    define( 'MAILCHIMP_USE_OUTBOUND_IP', false );

    Please let us know if this does the trick for you too!`

    Plugin Support khungate

    (@khungate)

    Hi @mgdiazanton, if you haven’t already resolved, the v2.7.1 version of the plugin should clear up this issue. Please let us know if you’re still having any problems and we’ll be glad to try some other troubleshooting steps with you.

    Plugin Support khungate

    (@khungate)

    Hi @mgdiazanton, we’re going to close out this ticket for now since it’s been a few weeks since we’ve been in touch.

    Please let us know if you still need any help and we’ll be glad to reopen and troubleshoot further. Please note, the best way to reach us is over at the GitHub plugin page: https://github.com/mailchimp/mc-woocommerce/. From there, you can receive direct responses from the development team, log new issues, download the latest version, and track existing support tickets.

    Thread Starter mgdiazanton

    (@mgdiazanton)

    Hi khungate,

    I just solved it yestarday.
    I had the help of a developer.
    We tried your suggestions but any of them worked.

    It seems it was a problem with cloudfare. At the end just turning off the cloudfare and loading again the page, connected the plugin to the store.
    So we turned on cloudfare again and it was allright, except that it got stuck syncing the store.
    I added &resync=1 to the page, and it got solved, as it says in here in one of the messages: https://github.com/mailchimp/mc-woocommerce/issues/441

    Thanks for all,

    Gaby

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘api error after upgrade’ is closed to new replies.