Thanks for letting us know about this. I know the message said Jetpack was the plugin with the error, but we often find that the cause of these errors is that another plugin is conflicting with Jetpack.
Are you able to try having only Jetpack active with all other plugins deactivated? Then you can reactivate them one at a time to find out which one was causing the issue. You can use the Troubleshooting mode of the Health Check plugin to do this without impacting visitors to your site.
Troubleshooting mode allows you to have a clean WordPress session, where all plugins are disabled, and a default theme is used, but only for your user until you disable it or log out.
https://www.ads-software.com/plugins/health-check/
When utilizing the troubleshooting mode, your currently logged-in user is given a stripped-down version of WordPress, where all plugins are disabled and one of the default themes is activated.
It is important to note that this is only the case for your user, it does not affect any other site visitors, or users of your site, for them the theme will be the same, and all plugins will still be running as before.
This mode is essential when trying to identify the cause of an issue, as in most cases, any issue you have will be introduced by your theme or one of your plugins (or maybe even multiple plugins interacting poorly with each other).
When in troubleshooting mode you are able to verify if a problem still exists in a basic WordPress setup, thus helping us identify and fixing a bug others may be encountering, or finding out which plugin or your theme is causing the problems so that you can report this to the applicable authors.
https://make.www.ads-software.com/support/handbook/appendix/troubleshooting-using-the-health-check/
Can you give this a try and see what comes of it?
