sdixon194

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?

Hey folks, thanks for all the reports! We’ll be conducting a point release, Jetpack 11.5.1 to address this within the next 24 hours.

The tldr is that the Firewall module (waf) autogenerates some files for the IP block/allow list that are getting removed in the upgrade and then missing when Jetpack looks for them later.

As some folks have mentioned, simply removing and re-installing Jetpack 11.5 will fix the issue in the meanwhile. If your site is down after upgrading, you can also try toggling the WAF module which should regenerate the needed files by using the WP CLI: wp jetpack module deactivate waf and then wp jetpack module activate waf.

Apologies for the disruption with this release.

Thanks @mikelittle, it looks like that issue is different than this issue. There is an existing report for the same error here: https://github.com/Automattic/jetpack/issues/27213

For the issues with Jetpack WAF, our team has identified a fix. For now, it seems reinstalling Jetpack seems to fix the issue. Additionally, de-activating and re-activating the waf module may fix it (wp jetpack module deactivate waf and wp jetpack module activate waf).

Please continue let us to know of any new instances of the problem so we know how widespread the issue is.

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

Hey Erin, apologies for the confusion here! There was an issue with classic/legacy widget visibility not working with WordPress 5.8 prior to Jetpack 9.9.1, which has been addressed – however visibility settings still aren’t available for the block based widgets (which it sounds like what you converted to).

In the meanwhile, using the legacy widgets you were using before (prior to converting them to block based widgets) should let you continue to use the visibility settings as before. We’re actively working on adding support for the newer block based widgets. While we don’t have an ETA, you can track progress on the issue that Dan provided above, and once it’s closed, will launch in the next version of Jetpack.

If you run into any other issues, don’t hesitate to let us know!