Title: Too many “e_error” errors
Last modified: September 29, 2025

---

# Too many “e_error” errors

 *  Resolved [depannerobot](https://wordpress.org/support/users/depannerobot/)
 * (@depannerobot)
 * [8 months, 1 week ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/)
 * Hi everybody
 * following answer from Woocommerce plugin, i had too many “e_error” errors.
 * and following them, I have disabled JetPack and, for now, I haven’t had any further
   errors
 * see below logs
 * System Status Report : [https://pastebin.com/s0PysWau](https://pastebin.com/s0PysWau)
 * Fatal error logs is too big >512 k, so it’s on my own server : [http://depannerobot.fr/partage/fatal-errors-2025-09-25.log](http://depannerobot.fr/partage/fatal-errors-2025-09-25.log)
 * Thx
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ftoo-many-e_error-errors-2%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Support [lastsplash (a11n)](https://wordpress.org/support/users/lastsplash/)
 * (@lastsplash)
 * [8 months, 1 week ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/#post-18664066)
 * Hi [@depannerobot](https://wordpress.org/support/users/depannerobot/) –
 * Thanks for sharing the error logs.
 * To isolate the issue, we’ll need you to do a conflict test. Please temporarily
   disable all plugins other than WooCommerce and then reinstall Jetpack. With only
   WooCommerce and Jetpack, do you see the issue?
 * You can also do this test on a staging environment if that is more convenient.
 * Let us know what you find out.
 *  Thread Starter [depannerobot](https://wordpress.org/support/users/depannerobot/)
 * (@depannerobot)
 * [8 months, 1 week ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/#post-18664200)
 * [@lastsplash](https://wordpress.org/support/users/lastsplash/) i can’t disable
   all plugins because i need them for my shop.
 * maybe i need to copy all website to another ? Can i ?
 *  Plugin Support [lastsplash (a11n)](https://wordpress.org/support/users/lastsplash/)
 * (@lastsplash)
 * [8 months, 1 week ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/#post-18664353)
 * Hi [@depannerobot](https://wordpress.org/support/users/depannerobot/) –
 * Yes, you can clone your website into another and do the testing there. Many hosts
   call that a “staging environment”. As you mention, it can be less disruptive 
   to do it there.
 * Let us know what you find out.
 *  Thread Starter [depannerobot](https://wordpress.org/support/users/depannerobot/)
 * (@depannerobot)
 * [8 months ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/#post-18672719)
 * hi, I disabled JetPack and no further errors
 *  Plugin Support [Tamirat B. (a11n)](https://wordpress.org/support/users/tamirat22/)
 * (@tamirat22)
 * [8 months ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/#post-18675009)
 * Hello [@depannerobot](https://wordpress.org/support/users/depannerobot/),
 * Thanks for sharing that disabling Jetpack stopped the errors.
 * If you’re still using WooCommerce, just a heads-up that [some Woo services require an active Jetpack connection](https://jetpack.com/support/woocommerce-products-that-require-a-jetpack-connection/)
   to work properly, including:
    - Automated tax calculations
    - Shipping label purchasing
    - WooCommerce Mobile App support
    - Email notifications and activity logs
 * If you’d like to keep using those features — and help us investigate where these
   errors are coming from — we recommend:
    - Re-enabling and updating Jetpack to version 15.1 (it was at 15.0)
    - Updating WooCommerce to the latest stable release
    - Checking your logs again and sharing any new entries with us
 * Looking at the logs you shared earlier, the most recent fatal errors were from**
   September 25**. A more up-to-date log after updating the relevant plugins could
   give us better insights into what’s going on.
 * Best,
 *  Thread Starter [depannerobot](https://wordpress.org/support/users/depannerobot/)
 * (@depannerobot)
 * [8 months ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/#post-18675058)
 * Hi
 * Twodays ago I got a PayPal payments error when Jetpack was disabled.
 * I just reactivated Jetpack, while leaving PayPal payment disabled.
 * I’m waiting for an error to occur before sending the logs.
 *  Plugin Contributor [Stef (a11n)](https://wordpress.org/support/users/erania-pinnera/)
 * (@erania-pinnera)
 * [8 months ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/#post-18676949)
 * Hi there, [@depannerobot](https://wordpress.org/support/users/depannerobot/),
 * We see our Woo colleagues have replied to your same message on this thread: [https://wordpress.org/support/topic/too-many-e_error-errors/#post-18675123](https://wordpress.org/support/topic/too-many-e_error-errors/#post-18675123)
 * I am going to close this thread for now, to ensure all the info are shared in
   the same place, so we won’t lose any useful data.
 * If Jetpack support and assistance is needed at any capacity, we’ll be happy to
   chime in. Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Too many “e_error” errors’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

 * 7 replies
 * 4 participants
 * Last reply from: [Stef (a11n)](https://wordpress.org/support/users/erania-pinnera/)
 * Last activity: [8 months ago](https://wordpress.org/support/topic/too-many-e_error-errors-2/#post-18676949)
 * Status: resolved