Jetpack Update produced critical error

  • Resolved heesea

    (@heesea)


    2 years, 10 months ago

    I updated my site to the latest Jetpack version today. Since then, I cannot get back in my site. It produces a 503 error whether for the frontend or backend. The WordPress message I received was this with my site name redacted:

    Howdy!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Jetpack.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.8.3
Current theme: xxx (version 1.0.2)
Current plugin: Jetpack (version 10.5)
PHP version 7.4.26

Error Details
=============
An error of type E_COMPILE_ERROR was caused in line 90 of the file /home/xxx/public_html/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php. Error message: require(): Failed opening required '/home/xxx/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-functions.php' (include_path='.:/opt/alt/php74/usr/share/pear')
Viewing 3 replies - 1 through 3 (of 3 total)

  • I had a similar error when installing latest uypdate on two sites today. The update seems to have worked ok but the critical error notification came up both times. The sites are still fine though and I can access the Dashboard normally so not sure if the error has had any consequences at all.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hello @heesea and @wildambience,

    Apologies for the inconvenience caused by this error notification. Our developers are aware of the problem, and we’ve confirmed this error shouldn’t cause any issues on your site. The error resolves itself during the process of updating the Jetpack plugin, and the error should not occur again now that the plugin update is complete.

    Sorry for the false alarm!

    If you have any further questions or want us to take a look at your sites, please share your site URL. If you want it to remain private, you can also contact us via this contact form:
    Contact Support.

    Thread Starter heesea

    (@heesea)

    Thank you so much for your attention! My host was having an issue that coincided with the Jetpack update, confusing matters.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Jetpack Update produced critical error’ is closed to new replies.