Fatal Error

Hi there,

Thanks for the report! This was a known issue with 11.5. We’ve since released Jetpack 11.5.1, which should address the issue. You can notify your host that you can upgrade to the latest version of Jetpack?

Thank you so much.

I’m experiencing the same problem even though the plugin updated to 11.5.1. I’m running WP 6.1.

I am experiencing the same issue after the update. What do I need to do?

Getting really sick of these Jetpack issues, same issue here!

Solution:

Rename Jetpack / Disable it via FTP, regain access and update to Jetpack 11.5.1 and then voila. Fixed.

Jetpack Protect also give fatal error

• This reply was modified 2 years, 4 months ago by Guillermo.

Hi @gadgetcoma,

Please put WordPress in debug mode and look for fatal error messages in the debug log file and what files they highlight.

If you’re not familiar with WordPress debugging, then you may use a plugin like WP Debugging to get started.

If the error doesn’t reference the Jetpack WAF module, something else must be causing it, and the update we released won’t fix that.

It’s showing the error is related to the WAF:

[03-Nov-2022 12:22:19 UTC] PHP Fatal error: Uncaught Error: Failed opening required ‘/volume1/web/blog/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-waf/src/../rules/allow-ip.php’ (include_path=’.:/usr/share/pear’) in /volume1/web/blog/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-waf/rules/rules.php:2
Stack trace:
#0 /volume1/web/blog/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-waf/src/class-waf-runner.php(176): include()
#1 /volume1/web/blog/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-waf/src/class-waf-runner.php(48): Automattic\Jetpack\Waf\Waf_Runner::run()
#2 /volume1/web/blog/wp-content/plugins/jetpack/modules/waf.php(30): Automattic\Jetpack\Waf\Waf_Runner::initialize()
#3 /volume1/web/blog/wp-content/plugins/jetpack/class.jetpack.php(1862): include_once(‘/volume1/web/bl…’)
#4 /volume1/web/blog/wp-includes/class-wp-hook.php(308): Jetpack::load_modules(”)
#5 /volume1/web/blog/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#6 /volume1/web/blog/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#7 /volume1/web/blog/wp-settings.php(480): do_action(‘plugins_loaded’)
#8 /volume1/web/blog/wp-config.php(84): require_once(‘/volume1/web/bl…’)
#9 /volume1/web/blog/wp-load.php(50): require_once(‘/volume1/web/bl…’)
#10 /volume1/web/blog/wp-admin/admin.php(34): require_once(‘/volume1/web/bl…’)
#11 /volume1/web/blog/wp-admin/plugins.php(10): require_once(‘/volume1/web/bl…’)
#12 {main}
thrown in /volume1/web/blog/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-waf/rules/rules.php on line 2

Hello everyone,

We’re very sorry for the inconvenience caused by the fatal error you encountered when updating Jetpack version to 11.5.

Our developers have worked urgently to address the error, and a new version of Jetpack, version 11.5.1, has been released to resolve the problem. You should be able to safely update to this version of Jetpack without encountering any errors.

Please let us know if you run into any further issues, and we’ll be happy to help. Apologies again for the trouble!

We heard this was fixed in 11.5.1 about a week ago. I reported that this version doesn’t fix the problem for me. I just confirmed that I have the latest version but still have this error.

@gadgetcoma If the issue is still occurring, there may have been an issue during the update. Have you tried completely deleting Jetpack and installing it again via Plugins > Add New?

Thanks, @drawmyface. That fixed it.