khoavo

@josklever – Agreed. Waiting for WC to respond.

@anastas10s – I just saw a notification for WC 8.5.2 that is now available. Is this the version with the fix on this server error issue that we’ve bee discussing on this thread?

Changelog:

WooCommerce

• Fix – Fix PHP warnings and remove opinionated styles from the Banner button. #43354
• Fix – Add defensive checks for strpos in ComparisonOperation. #44033
• Fix – Add rudimentary try catch for all remote endpoint spec evaluators. #44037

@josklever – Just changed it to unresolved, Thanks bro.

@kalaghni – I wouldn’t be able to understand all those error codes from your screenshot. But the fatal server error caused by WC 8.5.1 on some hosting servers seem to be the same: Internal Server Error, Maxed out the CPU & Physical Memory on the server, etc. Just continue to use WC 8.40 on all of your current websites running WC and wait for them to provide a fix. They’ll get to the bottom of it eventually.

• This reply was modified 10 months, 1 week ago by khoavo.

@kalaghni – It’s not resolved, not sure why they marked it resolved. Still awaiting for WC to provide a fix. For now, use WC 8.40 to keep your site running smoothly.

@anastas10s – Before updating to WC 8.5.1 my Marketplace option was enabled and the box checked, see screenshot: https://prnt.sc/G_5yZ0WPxt-y

But the problem persist once I update to WC 8.5.1 – Causing fatal error, 503, internal server error, maxed out my CPU & Physical RAM memory on the server, etc. So yes, it’s affecting some hosting providers and not others.

WooCommerce System Status:

I just pasted both secret links to your QuickForget.com service. That’s where you wanted me to paste it, not on this thread here, correct?

It includes two secret links for:

Website with NO ISSUES running WC 8.5.1

Website WITH ISSUES running WC 8.5.1

Note: The website with issues, I temporarily duplicated the website migrate it to a separate WordPress Installation. Just so I can replicate the fatal error to get you the System Status Data. I’ve now deleted this duplicated site from my hosting server since it crashes any other sites on the same server.

Both secrets will be forgotten in 2 days (1/28/2024, 6:06 PM PST) or after it is viewed 10 more times. Hope this helps. Thanks for your support. Keep us posted on this matter.

@anastas10s – Just for good measures, I just tested it again on default TT3 theme, with only WC 8.5.1 activated and all other plugins deactivated and the same issue occurs. Within 7 seconds, the physical memory usage and CPU Usage on my server gets drained out.

TT3 activated, see: https://prnt.sc/asUfnln5YVkK

With only WC 8.5.1 plugin activated and all other plugins deactivated, see: https://prnt.sc/fNP7VUM9XCOr

And within 7 seconds, the site broke, wp-admin access broke, internal server error displays, 503, etc. and server’s physical memory and CPU usage maxed out at 100%, see: https://prnt.sc/Usn8dffAaHsF

Hope that helps you as your team continues to investigate this matter. Please provide a fix soon as my of us loyal customers are depending on WooCommerce, a great plugin. Thanks!

@anastas10s – Bro, this issue is not caused by other plugins concurrently activated nor any by other themes. I told you my theme developer and web hosting provider did a thorough debugging process and concluded that WC 8.5.1 when activated hogs up all the CPU and Physical Memory on the server, crashing the site and server.

I even did my own test by activating TT3 default theme with all plugins deactivated accept for WC 8.5.1 and it broke my site and server. Something from WC 8.5.1 is hogging up all of the memory ram and CPU usage %.

Hey @anastas10s – I sure did, installed and activated TT3 to test: https://prnt.sc/q3WoFPohr0gG

With WC v8.40 activated, TT3 Theme displays fine, my CPU and Physical Memory Usage on the server shows normal: https://prnt.sc/f3hgRE2j50-9

But as soon as I update to WC v8.5.1: https://prnt.sc/2h7lKOYKtESK – Within 10 seconds, the site breaks, wp-admin access and website pages won’t load, page not found, internal server error, etc. And the CPU and Physical Memory Usage gets maxed out at 100%, see: https://prnt.sc/YG8nZfmfbSBR

As I indicated before, the issue with WC v8.51 seems to affect some web hosting providers / servers only and not others. For example, I have another WordPress site running WC v8.51 on Godaddy.com shared web hosting server and there’s no issues there. The WordPress site that I have issues with while running WC v8.51 is on the Midphase.com shared web hosting server. Perhaps you can find out the type of server Midphase.com is using? Or ask other users that are currently experiencing the same issues with WC 8.51 and find out which web hosting providers they are using. Hope this helps you as you investigate for a fix.

But for now, WC 8.40 is keeping my WordPress site running fine.

• This reply was modified 10 months, 1 week ago by khoavo.

@karolmanijak – After the WC 8.5.1 update, I encountered this main issue: The Physical resources hit 100% (Shared Hosting Memory RAM). We even tried clearing all the running processes however the physical memory reached 100% as soon as the site was visited. We also tried to increase the PHP parameters that did not help.

As a result of this, I couldn’t even logged onto my wp-admin, it would show Internal Server Error, Exceeded Resources, Forbidden Access Not Allowed, etc. and on the live website, when viewed, all the images are not displayed, as if they’re broken. Probably due to the 100% resources maxed out from the WC 8.5.1 update.

But once I rolled back WC to v8.40, all works fine again. Hope this help answer your questions. I’ll just wait for the WC to release the next update once they figure out the fix for this.

Thanks @ckadenge – WC 8.5.1 issue appears to affect only some web hosting servers, not all. For example, I have a site running WC 8.5.1 on the Godaddy web hosting server and there’s no issues there. But on others, WC 8.5.1 breaks the site and generates the 508 Resource Limit is Reached error, where it instantly uses up all the memory ram from the shared hosting server, etc.

I’ll wait for your team to release the next WC update so I can test it again. But for now, WC 8.40 is working fine on all of my sites.

Thanks @hastibe – much appreciate your input.

@hastibe – Thanks for the information, much appreciate it.

@htkike – No problem. See if you can find the older WooCommerce v8.40 to use for now. Because the previous version has no 503 issues. I’m waiting for WC to respond for their input on this matter.

@hthike – Yeah, same here. WC v8.5.1 which is the latest version, crashed my site, caused Internal Server Error since it sucks up all the server’s CPU Ram memory. I had to restore the site back and revert to WooCommerce v8.40 in order for the site to run smoothly. Hoping a newer WC plugin update will fix this.