429 Too Many Requests

  • Resolved jfortune

    (@jfortune)


    3 years, 2 months ago

    After running perfectly for over a year, we’ve had problems with our WooCommerce integration with Zenstores.

    Every 30 mins, Zenstores sends an API call to our website using this syntax:

    {{site_url}}/wc-api/v2/orders?status=processing&filter[limit]=15&page=1&consumer_key={{consumer_key}}&consumer_secret={{consumer_secret}}

    For the last year, this results in them receiving full details of any outstanding orders we have received since their last call.

    Suddenly, last week, instead of receiving order details, they received the following error message:

    <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”>
    <HTML>
    <head>
    <title>429 Too Many Requests</title>
    </head>
    <body>
    <h1>Too Many Requests</h1>
    <p>The user has sent too many requests in a given amount of time.</p>
    </body>
    </html>

    We tried whitelisting their IP addresses in WordFence but that had no effect.

    Then we tried switching off Rate Limiting but that had no effect either.

    As soon as we deactivated Wordfence entirely, it all started working again.

    Now, of course, we are not benefiting from all the features offered by WordFence.

    What settings should we use to use WordFence with Zenstores?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @jfortune, thanks for getting in touch.

    The “429 Too Many Requests” you’re seeing is actually a HTTP response rather than a Wordfence error page – which would come back with HTML containing our branding. This is why altering Rate Limiting settings or allowlisting didn’t change the outcome. However, why disabling Wordfence solves the issue is quite interesting, although could be related to checks made by the WAF when a request comes in causing the server to hit some sort of limit that has either been set by your host or in the configuration files.

    Most commonly, we’ve seen this with Cloudflare rate limiting, or the max_questions value set on your server, but some hosts will restrict your ability to alter this.

    If you’re able to reenable Wordfence, you could send us a diagnostics report to
    wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Note: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.

    Thanks,

    Peter.

    Thread Starter jfortune

    (@jfortune)

    Thanks for this Peter.

    I have reactivated Wordfence, run ‘Send Report by Email’, include my name here (@jfortune) and then deactivated Wordfence again.

    I look forward to your further thoughts on this problem.

    Thanks,
    James

    Plugin Support wfpeter

    (@wfpeter)

    Hi @jfortune, thanks for sending those over.

    Your general communication to/from our servers seems fine, Cloudflare doesn’t seem to be a factor, and your host doesn’t have any history in terms of support topics we’ve seen of this nature. I think the full response headers from the 429 response will likely indicate which component returned it, which should help identify the rate limiting.

    You can see how to return the full response here. If you’re not using Chrome, most in-browser developer tools operate similarly in terms of their layouts now.

    Thanks,

    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘429 Too Many Requests’ is closed to new replies.