Too Many Requests error after Woo update

  • Resolved thewebmonk

    (@thewebmonk)


    1 month ago

    My website has been offline for about 1 hour, the error is: “”Too Many Requests – the user has sent too many requests in a given amount of time”.

    I checked the Error_Log in my File Manager, and this is what I see https://pastebin.com/i6cbWPL1 has to do with Woocommerce or WPML, cannot tell.

    All I know is that I updated to the new Woo yesterday.

    Thank you for your help

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello thewebmonk,

    Thank you for your reply.

    I understand you are facing a “Too Many Requests – the user has sent too many requests in a given amount of time” error on your site.

    The error log you shared might be related to this error.
    Is this issue still happening? If yes then please share a screenshot of the error.
    I want to see on which page it appears.

    I visited your site and it seems to be working fine.
    Here is a screenshot:

    To help you further, please share your site’s System Status Report with me.
    You can paste it into https://pastebin.com and share the link here.

    Best regards.

    Thread Starter thewebmonk

    (@thewebmonk)

    Hello Zubair,

    the hosting company helped me fix the problem, looks like it was a malicious attack from some bots that had my website offline. But the event coincided with the time at which WooCommerce Multilingual for some reason was deactivated and created those errors in the logs. Not sure what caused it, if the malicious attack could deactivate the plugin.

    Thank you

    Raffaella

    Plugin Support Mahfuzur Rahman(woo-hc)

    (@mahfuzurwp)

    Hi Raffaella,

    I’m glad to hear that your hosting company was able to help fix the issue. It’s definitely possible that the malicious attack caused unexpected disruptions, such as deactivating plugins like WooCommerce Multilingual, but we can’t say for certain if that was the direct cause.

    It’s always a good idea to keep your plugins and security measures up to date to prevent future incidents.

    Thanks for letting us know, and don’t hesitate to reach out if you have any more questions.

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