Unable to fully load Woocommerce internal pages and crashes the site afterwards

  • Resolved snippet24

    (@snippet24)


    7 months, 1 week ago

    Hi,
    If I try to load:
    https://www.klotho.cl/wp-admin/admin.php?page=wc-admin
    the page returns: “There was an error getting your inbox.”
    and then crashes the site with “A timeout occurred Error code 524” as well with “503 Service Unavailable – The server is temporarily busy, try again later!”

    It seems it keeps trying to load without success https://www.klotho.cl/wp-admin/admin-ajax.php according to the console.log

    Even Sucuri plugin has this issue that keeps trying to load admin-ajax.php

    Here’s the system report: https://docs.google.com/document/d/1_aTlr7BW7piefZMmAgHkDGqA384ksBhzgwSh2Kp8a_o/edit?usp=sharing

    And with error verbose enabled with: ‘WP_DEBUG’, true, I get:


    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wc-quantity-plus-minus-button domain was triggered too

    early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later.

    Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/klothocl/public_html/wp-includes/functions.php

    on line 6121

    Warning: Cannot modify header information - headers already sent by (output started at /home/klothocl/public_html/wp-includes/functions.php:6121) in

    /home/klothocl/public_html/wp-includes/functions.php on line 7168

    Warning: Cannot modify header information - headers already sent by (output started at /home/klothocl/public_html/wp-includes/functions.php:6121) in

    /home/klothocl/public_html/wp-includes/functions.php on line 7144

    Warning: Cannot modify header information - headers already sent by (output started at /home/klothocl/public_html/wp-includes/functions.php:6121) in

    /home/klothocl/public_html/wp-admin/admin-header.php on line 14

    But even after disabling the “Quantity Plus Minus Button for WooCommerce” plugin and effectively no longer seeing the this notice, the orginal problem persists.

    Tried as well adding: WooCommerce Legacy REST API extension, no difference.

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

Viewing 15 replies - 16 through 30 (of 35 total)
1 2 3
  • Thread Starter snippet24

    (@snippet24)

    5 months ago

    • WooCommerce transients – Clear
    • Expired transients – Clear
    • Clear template cache – Clear
    • Capabilities – Reset Capabilities
    • Clear customer sessions -Clear

    Hi, it seems doing so fixes the loading but only for the first time then the error occurs again. Theres an error that always appear with the bug: 

    Uncaught (in promise)
    Object { code: "invalid_json", message: "The response is not a valid JSON response." }

    Is it good idea to share a .HAR file? let me know if that is a good option.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    5 months ago

    Hi there,

    Thanks for the update! To help narrow down the cause, could you please confirm if the issue still occurs after deactivating all plugins? I noticed some plugins were active on your staging site, and they might be affecting the JSON responses.

    Also, have you tried checking the issue in an incognito/private browser window? This can help rule out browser caching or extension interference.

    Additionally, it would be very helpful if you could share:

    1. A .HAR file from your browser capturing the error (please make sure to remove any sensitive information).
    2. Latest System Status Report from your staging site (WooCommerce → Status → Get system report).

    These will give us the information needed to investigate further and identify what might be causing the “invalid JSON” error.

    Thread Starter snippet24

    (@snippet24)

    5 months ago

    Hi, Ok, tried again just to be sure, with all other plugin deactivated but WooCommerce on the third loading try I got again “There was an error getting your inbox. Please try again.” Sometimes is able to load it and some times is not. For example i got “https://www.klotho.cl/wp-json/jetpack/v4/connection?_locale=user with error 503 on that one.

    A .HAR file from your browser capturing the error (please make sure to remove any sensitive information).

    Question how to be sure it doesn’t contain sensitive info?

    Latest System Status Report from your staging site (WooCommerce → Status → Get system report).

    https://drive.google.com/file/d/1f8Ph9OAoc3zD0a9Wv6RFxFMgq3YSjruQ/view?usp=sharing

    Also, have you tried checking the issue in an incognito/private browser window? This can help rule out browser caching or extension interference.

    When the error happens I try to load on a different Firefox container, to discard cache, but you mean logging in another container?

    • This reply was modified 5 months ago by snippet24.
    • This reply was modified 5 months ago by snippet24.
    Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    5 months ago

    Hi @snippet24,

    Thanks for the additional details and for testing with only WooCommerce active. That helps confirm it’s not a third-party plugin conflict.

    From your status report, I noticed:

    • PHP is up to date (8.2) which is good.
    • Memory limit is 256M. You might want to increase this to 512M to rule out resource exhaustion.
    • The Action Scheduler has nearly 1,000 failed actions, which can sometimes cause background requests like the inbox and API calls to fail intermittently.

    About your questions:

    • A HAR file captures all network requests/responses when you load a page. It can include sensitive information such as cookies, authentication headers, or form data if you type it in during capture. Before sharing:
      1. Open the .har file with a text editor.
      2. Search for terms like “cookie”, “authorization”, or your domain/email.
      3. If you see session tokens or personal data, you can safely remove or redact those lines before sending ( add something like [Redacted]). The key info we’re looking for are the failed requests (status codes, URLs, error messages).
    • Incognito/containers: Yes, trying in a Firefox container rules out cached sessions, but what we meant was a full private/incognito window with no extensions or saved cookies. That helps confirm it isn’t a browser cache or extension issue.

    For next steps:

    1. Please try increasing the WP memory limit to 512M.
    2. If possible, clear or reset stuck/failing Action Scheduler tasks (WooCommerce → Status → Scheduled Actions → filter for “Failed”).
    3. If the issue persists, capturing a HAR file with the failed 503 requests (after redacting any sensitive data as described) will be the most useful for debugging.

    Let us know how that goes.

    Thread Starter snippet24

    (@snippet24)

    4 months, 4 weeks ago

    Hi @frankremmy ,

    Done step 1 and 2, on first load it loaded correctly the home internal page, but on the second load it failed with the “There was an error getting your inbox. Please try again.”. Here there are the HAR files. The first one is the first load, and the second is for the failed second load.

    https://drive.google.com/file/d/1lzCazbfHt7dBy86kJSVuRI_Kfv5HzUdr/view?usp=sharing

    https://drive.google.com/file/d/1DQNGMfLaanRVnskfAAOVVWqEicYZm62D/view?usp=sharing

    Do note i did look up for sensitive data but since I don’t have much experience with .HAR files if you find any sensitive data please let me know to remove them asap.

    Regarding incognito mode, I’m not sure if you mean loading the page after the crash and seeing if it returns timeout or 503 error?

    • This reply was modified 4 months, 4 weeks ago by snippet24.
    Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    4 months, 4 weeks ago

    Hi @snippet24,

    Thanks again for all the detailed testing and for sharing the HAR files. That’s been really helpful.

    We noticed something: when we try to access your domain at https://www.klotho.cl, it redirects to https://klotho.mercadoshops.cl, which appears to be using Mercado and not WooCommerce. Could you clarify whether this is expected behavior, or if the WooCommerce site is hosted elsewhere?

    Also, your System Status Report you shared includes the live site link. Do you happen to have a staging site we can reference for further testing? If so, could you please share the staging site URL?

    This will help us better understand your setup and narrow down the source of the issue.

    Looking forward to your update!

    Thread Starter snippet24

    (@snippet24)

    4 months, 4 weeks ago

    Hi @frankremmy ,

    Yes this is expected behavior as we are looking forward to go back to Woocommerce from Mercadoshops, but we need the site to be stable before doing so. Some days ago I temporally disabled the redirection in Cloudflare to see if the problem was gone with it, but it wasn’t.

    Also, your System Status Report you shared includes the live site link. Do you happen to have a staging site we can reference for further testing? If so, could you please share the staging site URL?

    Sure here it is:
    https://www.klotho.cl/klothodebug/
    let me know if you want me to also clear/reset the same items in the sating site as well and to delete the failed log items too.

    Update: i have to disable all the other plugins in the staging site will do so now, do note the active theme is Twenty Twenty-Four

    • This reply was modified 4 months, 4 weeks ago by snippet24.
    Thread Starter snippet24

    (@snippet24)

    4 months, 4 weeks ago

    I noticed something odd: even though the plugin “Custom Product Tabs for WooCommerce” is disabled and in the case of the staging site is deleted, I’m still seeing the tab: “informacion adicional” in the product pages. Screenshot: https://drive.google.com/file/d/14UNEQJrbdWQ7uoK-nRddSLz4f3o_kQp4/view?usp=sharing

    Moses M. (woo-hc)

    (@mosesmedh)

    4 months, 4 weeks ago

    Hi @snippet24,

    Thank you for getting back to me and sharing your observations. I can see you’ve put in a lot of effort troubleshooting this issue, and I completely understand how quickly things can become confusing and frustrating.

    From the steps you’ve already taken and the behavior you described, it looks like some form of caching—most likely on the server—could be causing the problem. As you mentioned, the site works on the first load after clearing the template and other caches, but crashes again on the second load.

    Your note about still seeing settings from a deleted plugin also supports this suspicion.

    Let’s take a step back. You mentioned that you were previously on another platform but are now moving back to WooCommerce, which is when these issues started. Could you clarify how you migrated your products and design to WooCommerce/WordPress? Did you rebuild everything from scratch, or did you use an export/import process?

    Understanding how you arrived at your current setup will give us better insight into the root of the issue.

    Thread Starter snippet24

    (@snippet24)

    4 months, 4 weeks ago

    Hi @mosesmedh

    I will clarify: we had long time ago the Woocommerce site, but then it was decided to redirect to Mercadoshops and use that instead. But now the idea is to resurrect the website with the old Woocommerce, so no migration was done actually of data between platforms, we are just reactivating the old site with Woocommerce. The idea is to get it working.

    • This reply was modified 4 months, 4 weeks ago by snippet24.
    Thread Starter snippet24

    (@snippet24)

    4 months, 4 weeks ago

    Update: seems like it is default the additional info when attributes are set in shipping (so the plugin mentioned above was successfully uninstalled). I do noted now I have issues setting a product to allow reviews. Reviews are enabled in general settings, but if I try to enable them in a product with quick edit or regular in “Enable reviews” under “advanced” it doesn’t get saved. If the plugin for reviews is disabled I actually get:

    Uncaught (in promise)
    Object { code: "fetch_error", message: "You are probably offline." }
    ​
    code: "fetch_error"
    ​
    message: "You are probably offline."

    I will do further tests tomorrow as is late here.

    • This reply was modified 4 months, 4 weeks ago by snippet24.
    Moses M. (woo-hc)

    (@mosesmedh)

    4 months, 3 weeks ago

    Hi @snippet24,

    Thank you for getting back to us and for the update. Could you clarify where exactly the error you shared is showing—are you seeing it in the log?

    I’d also like us to try a different approach. Please export your site to a local environment (such as WP Local, XAMPP, or WAMP) and check whether the same issue occurs there as well.

    Once set up locally, run a conflict test by keeping only WooCommerce active, switching to a default theme, and deactivating all other plugins. Then check if the issue persists in that environment.

    Thread Starter snippet24

    (@snippet24)

    4 months, 3 weeks ago

    Hi @mosesmedh

    Thank you for getting back to us and for the update. Could you clarify where exactly the error you shared is showing—are you seeing it in the log?

    Yes console log.

    I’d also like us to try a different approach. Please export your site to a local environment (such as WP Local, XAMPP, or WAMP) and check whether the same issue occurs there as well.

    Yes I’m afraid is still happening, https://drive.google.com/file/d/1cEQ1hYnHrHxBq3VloI2W-hY0wXM5OQA8/view?usp=sharing but most of time its loads correctly, I should do more tests to be sure I guess? the screenshot happened once only, but I did get more 500 internal errors on : GET
    http://localhost/wordpress/wp-json/jetpack/v4/connection?_locale=user

    even though it loaded the inbox.

    Update2: it happened a second time the classic error “Unable to load the inbox” but it is much less frequently than in the live site.

    Once set up locally, run a conflict test by keeping only WooCommerce active, switching to a default theme, and deactivating all other plugins. Then check if the issue persists in that environment.

    I will do that tomorrow as well my previous tests were with all plugins enabled.

    I have further info though and a theory: it seems like even though first load of the inbox happens it also creates the bug / crash, if i click on “dismiss” in any inbox item it crashes like this (oj this happened on first; try I have to do more tests):

    https://drive.google.com/file/d/1BI5JRPQXc37_rVUB9q6pSYZ_saaCgi2I/view?usp=sharing

    Could it be related to heartbeat?

    • This reply was modified 4 months, 3 weeks ago by snippet24.
    • This reply was modified 4 months, 3 weeks ago by snippet24.
    • This reply was modified 4 months, 3 weeks ago by snippet24.
    • This reply was modified 4 months, 3 weeks ago by snippet24.
    • This reply was modified 4 months, 3 weeks ago by snippet24.
    Moses M. (woo-hc)

    (@mosesmedh)

    4 months, 3 weeks ago

    Hi @snippet24,

    Thank you for getting back to me and for sharing the screenshots—they’re very helpful in understanding the issue. Could you please confirm whether the screenshot was taken in your local environment or on a staging site with your host? If it’s from a local setup, which environment are you using?

    I’ll hold off until I hear back from you. In the meantime, please run a test on your local environment using the Storefront theme, with all plugins disabled except WooCommerce, so we can better understand the behavior of the issue.

    Thread Starter snippet24

    (@snippet24)

    4 months, 3 weeks ago

    Hi

    Could you please confirm whether the screenshot was taken in your local environment or on a staging site with your host? If it’s from a local setup, which environment are you using?

    The first screenshot is from a local WAMP server (you can also see the “localhost” in the screenshot details

    I’ll hold off until I hear back from you. In the meantime, please run a test on your local environment using the Storefront theme, with all plugins disabled except WooCommerce, so we can better understand the behavior of the issue.

    Ok, I tested at least ten times, and none of them crashed or displayed the message “there was an error getting your inbox”.

Viewing 15 replies - 16 through 30 (of 35 total)
1 2 3

You must be logged in to reply to this topic.