Website not working due woocommerce

Hello Giuseppe,

Thank you for your reply.

When I make the staging website should I delete the debug sentences in the wp-config of the live website and add them in the wp-config of the staging website?

You are right, since we are going to continue troubleshooting at the staging site, it would be better to add debug lines to the wp-config.php file at the staging site.

In addition to my previous message I wanted to inform you that in my server in the directory WordPress I found a new strange file called .htgwzr4x.appconfig.php and another one called it-api.php

These are not WordPress files. These files might be added by your web host to manage the server. I recommend you contact them to confirm the purpose of these files.

Looking forward to your response. 🙂

Hi @govisola,

Thank you for the clarification, and apologies for the confusion earlier. Since the uptime monitoring you’re using doesn’t rely on a plugin, if possible, please add the staging site as a separate site in your monitoring tool instead of grouping it with the live site. This way, any notices or errors will be tracked individually for both the staging and live sites.

The goal is to see if any errors are recorded for the staging site, where only WooCommerce is active and the Storefront theme is enabled, similar to how they appear on the live site.
Thank you for your continued patience.

Hi @govisola,

Thanks for following up. If the uptime monitor is detecting server errors on your live site but not on your staging site, this suggests that high traffic or specific requests from live users may be triggering a conflict that leads to downtime. Since the staging site isn’t receiving the same level of activity, it doesn’t experience the same issue — which supports this theory.

Regarding the logs you mentioned, it appears that every time a request hits the server, it’s triggering the problem you’re facing. The message in the log isn’t actually an error — it’s just a notice related to background plugin updates, which is normal.

As previously mentioned, all signs continue to point to a server-related issue. It could be struggling with background processes, scheduled actions, or being blocked in some way.

At this stage, it’s clear that the issue is rooted in the server’s ability to handle certain types of requests. You’re welcome to continue monitoring and updating us, but your hosting provider is best equipped to help resolve this. Alternatively, you could hire a WordPress or WooCommerce expert from Codeable or WooCommerce Development Services for a deeper investigation.

You can also raise an issue on GitHub here so the WooCommerce development team and community can review it:
👉 https://github.com/woocommerce/woocommerce/issues

Thank you for your patience so far and effort. Since you’re using WooCommerce, we’d really appreciate it if you could take a moment to leave an honest review. Your feedback is incredibly valuable and helps us continue improving the plugin:
👉 https://wordpress.org/support/plugin/woocommerce/reviews/#new-post

Hi @govisola ,

Thanks for your message!

From what you’re describing, it seems like the issue could be related to your server. It might be worth considering an upgrade to handle higher traffic or moving away from shared hosting, which can sometimes cause performance hiccups. I’d suggest touching base with your hosting provider to see if they can offer any insights or suggestions.

Since the issue isn’t replicable on the staging site, I don’t think opening a GitHub issue would be necessary at this point. However, if you’d like to investigate further, feel free to create, and our developers can take a closer look from their end.

P.S. I really appreciate you taking the time to leave a review — thank you so much!

I hope this helps clarify things!