503 but ONLY when viewing “All Products”

Hello eaec,

Thank you for contacting WooCommerce support.

It does sound like a strange issue, especially since it only affects the All Products section in WP Admin while filtered views work fine.

Here are a few steps you could try:

• Check Fatal Error Logs:
  Go to WooCommerce > Status > Logs, and see if there are any fatal error logs that can provide more insight. This could help identify if a specific plugin or function is causing the issue.
• Plugin Updates:
  Do you recall which plugins were updated when the issue began? If you could share the names, it may give us more clues about potential conflicts.
• Conflict Testing:
  Since you mentioned that everything else is working, and you can’t disable all plugins or switch themes in production, I’d recommend setting up a staging site for conflict testing. This will allow you to safely disable plugins or change themes without affecting your live site.

Once I have more details I’ll be happy to assist further.

Best regards.

Hello Zubair

Thanks for the reply. I spun up an updraft clone and did some testing – In the staging area, I disabled all of the plugins except woocommerce and switched to 2024 theme, tested with success, then switched back to the same theme as production and then turned on all of the plugins in staging in groups of 4, and did not encounter the issue. I compared the plugin list to production and it is the same, but production is still returning a 503 error when I try to look at all products in admin. I can use the workround of going to a product filtered URL and can add, delete, and edit listings from there, but still unable to access “all products”.

I checked the error logs and I see something promising refering to jetpack and admin audit plugins which recurs, I will paste that report below. I have tried to access All Products with Jetpack and/or WP Admin Audit disabled, both in turn and together, and I still get a 503 in any scenario.

2024-09-27T05:57:58+00:00 Critical Uncaught Error: Object of class stdClass could not be converted to string in /home/eyeandear/public_html/wp/wp-content/plugins/wp-admin-audit/classes/Sensors/User.php:125 CONTEXT: {“error”:{“type”:1,”file”:”/home/eyeandear/public_html/wp/wp-content/plugins/wp-admin-audit/classes/Sensors/User.php”,”line”:125},”backtrace”:[“”,”#0 /home/eyeandear/public_html/wp/wp-includes/class-wp-hook.php(324): WADA_Sensor_User->onUserMetaUpdate(‘33979’, 1, ‘my-jetpack-cach…’, Object(stdClass))”,”#1 /home/eyeandear/public_html/wp/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)”,”#2 /home/eyeandear/public_html/wp/wp-includes/plugin.php(517): WP_Hook->do_action(Array)”,”#3 /home/eyeandear/public_html/wp/wp-includes/meta.php(290): do_action(‘update_user_met…’, ‘33979’, 1, ‘my-jetpack-cach…’, Object(stdClass))”,”#4 /home/eyeandear/public_html/wp/wp-includes/user.php(1217): update_metadata(‘user’, 1, ‘my-jetpack-cach…’, ‘O:8:”stdClass”:…’, ”)”,”#5 /home/eyeandear/public_html/wp/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-my-jetpack/src/class-wpcom-products.php(133): update_user_meta(1, ‘my-jetpack-cach…’, Object(stdClass))”,”#6 /h”]}

According to the admin audit logs, the plugins that were updated right before this became an issue were as follows:
Customizer Export/Import updated from version 0.9.7.2 to 0.9.7.3
UpdraftPlus – Backup/Restore updated from version 1.24.4 to 1.24.5
WooCommerce Square updated from version 4.8.0 to 4.8.1
WPC Smart Wishlist for WooCommerce updated from version 4.9.0 to 4.9.1
WPC Smart Wishlist for WooCommerce (Premium) updated from version 4.9.0 to 4.9.1
WooCommerce PayPal Payments updated from version 2.9.0 to 2.9.1 (installed but not active)

12 hours before that round of updates, these were also updated.
Elementor updated from version 3.24.3 to 3.24.4
Admin and Site Enhancements (ASE) Pro updated from version 7.4.3 to 7.4.4

The only other thing I can think that may have been abnormal is Elementor was reporting that it was still updating its database when some of the above plugins were updated (the tab ahd not been refreshed so I did not see the dialogue).

Thanks for your help, Brad

• This reply was modified 1 month, 3 weeks ago by eaec.
• This reply was modified 1 month, 3 weeks ago by eaec.
• This reply was modified 1 month, 3 weeks ago by eaec.
• This reply was modified 1 month, 3 weeks ago by eaec.
• This reply was modified 1 month, 3 weeks ago by eaec.

Hello eaec,

Thank you for your reply.

I appreciate the steps you have taken to troubleshoot this issue.

That’s unusual since the staging site works fine with the same setup.
I recommend you plan website maintenance and put the live site in maintenance mode, disable all plugins, switch to the Twenty Twenty-Four theme, and then reactivate everything and switch back to your original theme. If you’re using Apache, try deleting and regenerating the .htaccess file as well.

Please let me know how it goes.

Best regards.

Thanks, I will do that tomorrow and report back.

@eaec, sounds like a plan.

Let us know how it goes.