Activating WooCommerce causes mass calls and crashes websites

Hi there @icarusmanifest,

Based on the log files you’ve shared, it seems like there’s an excessive amount of requests being made to your WooCommerce CSS files. This is unusual.

Please ensure you are using the latest version of WooCommerce and any other plugins/themes in your site. Also, try running a conflict test to see if the issue persists with only having WooCommerce as the only active plugin. You can find a detailed guide on how to perform a conflict test here: https://woo.com/document/how-to-test-for-conflicts/.

Let us know how it goes.

Thank you for your reply.

Today I deleted WC via FTP and installed new from plugin library. Website crashes again. Also I deactivated all plugins except WC. Website doesn’t. It is really strange and I have no clue what to do.

Deactivating WC only works by renaming the plugin folder via FTP.

I am also having this problem. A pattern is observed of multiple requests from the Site IP, with requests are pouring in and reaching over 400 per minute at times.

We’re seeing the same issue on a woo site. All plugins updated, no malware, etc… Disabling woo stops it. Plugins:

+---------------------------------------+----------+--------+----------+
| name | status | update | version |
+---------------------------------------+----------+--------+----------+
| activecampaign-subscription-forms | active | none | 8.1.14 |
| activecampaign-for-woocommerce | active | none | 2.5.5 |
| add-from-server | active | none | 3.4.5 |
| advanced-coupons-for-woocommerce-free | active | none | 4.5.9.2 |
| advanced-coupons-for-woocommerce | active | none | 3.5.8.1 |
| ahrefs-seo | active | none | 0.10.2 |
| all-in-one-favicon | active | none | 4.8 |
| fusion-builder | active | none | 3.11.3 |
| fusion-core | active | none | 5.11.3 |
| powerpress | active | none | 11.4.5 |
| broken-link-checker | active | none | 2.2.4 |
| classic-widgets | active | none | 0.3 |
| duplicate-menu | active | none | 0.2.2 |
| duplicate-page | active | none | 4.5.3 |
| easyconnect_auth | active | none | 2.0 |
| duracelltomi-google-tag-manager | active | none | 1.19.1 |
| intercom | active | none | 2.6.5 |
| jetpack | active | none | 13.0 |
| nitropack | inactive | none | 1.11.0 |
| pinterest-for-woocommerce | inactive | none | 1.3.20 |
| pixelyoursite-pinterest | active | none | 5.3.2 |
| pixelyoursite-pro | inactive | none | 9.12.0.1 |
| redirection | active | none | 5.4.1 |
| rename-wp-login | inactive | none | 2.6.0 |
| scripts-n-styles | active | none | 3.5.8 |
| simple-user-avatar | active | none | 4.3 |
| social-warfare | active | none | 4.4.5.1 |
| social-warfare-pro | active | none | 4.3.0 |
| sucuri-scanner | active | none | 1.8.41 |
| team-showcase | inactive | none | 2.2 |
| updraftplus | inactive | none | 1.23.16 |
| woocommerce | active | none | 8.5.1 |
| woo-gutenberg-products-block | inactive | none | 11.7.0 |
| woothemes-updater | active | none | 1.7.2 |
| woocommerce-legacy-rest-api | inactive | none | 1.0.1 |
| woocommerce-paypal-payments | active | none | 2.5.1 |
| woocommerce-services | active | none | 2.4.2 |
| woocommerce-gateway-stripe | active | none | 7.9.1 |
| woocommerce-zapier | active | none | 2.10.0 |
| woocommerce-subscriptions | active | none | 5.9.1 |
| wp-add-mime-types | active | none | 3.1.1 |
| wp-recipe-maker | active | none | 9.1.2 |
| wp-recipe-maker-premium | active | none | 9.1.0 |
| wp-rocket | active | none | 3.15.8 |
| wp-rocket-compat-wc-cart-fragments | active | none | |
| wordpress-seo | active | none | 21.9 |
| zapier | active | none | 1.0.4 |
| advanced-cache.php | dropin | none | |
+---------------------------------------+----------+--------+----------+

Following this thread as I have several sites running WC and one is exhibiting this behavior.

Hi @icarusmanifest and everyone.

Could everyone please check the solution shared on our dev blog and see whether this issue gets resolved?

• https://developer.woo.com/2024/01/16/woocommerce-8-5-1-issues-with-web-application-firewalls-modsecurity/

Looking forward to resolving this issue for everyone.

Our site has been having a similar issue, activating WC causes hundreds of css requests which create apache children, inevitably crashing the site.

@shameemreza

This solution doesn’t work. I can’t change any WC options, because if I activate the plugin, the website crashes.

I hope, you find a solution quickly, so we can’t launch ours shops again.

@shameemreza – That does not apply here, as the css files get called over and over, not 403, and no WAF in place.

Pinging this thread again so I can get notifications. I’m glad I checked here because I saw the update get pushed out and was worried about installing it.

For those encountering the issue, could you please share your system status if it’s still active? I’m finding it difficult to replicate the problem with my setup.

• This reply was modified 10 months ago by moon0326.

Dear Support-Team,

could we expect a solution in the next days or how long do I have to let my Woocommerce shop be deactivated yet? Thank you.

Best regards,

This issue is now also under investigation via a GitHub ticket: https://github.com/woocommerce/woocommerce/issues/44093
They don’t know the cause yet, so it might still take some time before a fix is available.

There are 2 workarounds:

1. Rollback to WooCommerce 8.4.0
2. Immediately after the installing the update (or activating WC again), disable the Order Attributing feature by going to?WooCommerce > Settings > Advanced > Features > Order Attribution

@josklever

Option 1. Rollback to WooCommerce 8.4.0 worked for me.
Thanks

Hey, everyone!

@josklever, thank you for sharing the GitHub link and workaround options!

@samovic, glad to know it is working.

@icarusmanifest @rmang @kalaghni @madbirdesign2 Please try the workaround options shared above to see if the issue persists. If it does, please let us know so we can assist you further.

If you are not the thread starter and you need further help, per WordPress forum guidelines, would you mind opening up a new thread for this so that we can keep things organized and offer more personalized support for you? We’ll be happy to help you out with this over there!

Regarding when this will be solved, we are not able to provide a timeline for this yet, as we are looking into it. But rest assured we are doing everything we can to solve this as soon as possible.

In the meantime, you can subscribe to the GitHub issue to get updates about it.

Have a wonderful day!