Gadgetcoma

Thanks, @drawmyface. That fixed it.

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.

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

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

Done. Thanks again.

Actually, my WordPress experience hasn’t been completely flawless, but it’s been pretty darn good.

Thanks for your explanation. I hadn’t considered that many WordPress sites have member logins, which would, of course, expose the slug. I do recognize that security by obscurity is helpful but not the ultimate answer. (That’s why I like iThemes Security! ?? Given my set up, I just like to have as much obscurity as possible. It would be great to have the option to not include the slug in the notification emails, but I see now that it’s not critical.

BTW, I do have 2FA and will soon be adding SSL.

Thanks again for your response.

– Leon

Reminds me of a story –

A couple was worried about their son. He was approaching 3 years old and hadn’t uttered a word. They took him to doctor after doctor. They did every test imaginable. They couldn’t find any physical problems, he could hear, he had proper vocal cords, his reactions showed that he understood what was going on around him and his brain was as normal and healthy as everyone else his age. Then one day at dinner, he said, “My soup is cold.” His parents were amazed and shocked. After a few minutes, they recovered and explained to the boy how worried they were and why they did all of the tests. Finally, they asked, “Why haven’t you said anything until now?” The boy replied, “Until now, everything was perfect.”

??

The site in question is kidsmovingco.com.

Thanks.