Jetpack loses connection with WordPress in WordPress 5.4

By the way, even after uninstalling the plug-in “Jetpack” and installing and setting again, the following error was also displayed and I could not proceed to the setting.

The Jetpack server was unable to communicate with your site https://www.senris.com/xxxxxxx [HTTP 403].

Right now, after setting the Jetpack again after a while, I successfully connected to WordPrees.
Jetpack’s server may have had a problem, and Jetpack technicians may have fixed the problem, anyway I report that the “403 error” of problem has been resolved. (200 error is unresolved)

Although there is a time lag, the following measures were taken for restoration for your information.

1. Add the following sentence to “.httaccess” (essentially unnecessary)
# Accept xmlrpc.php
<FilesMatch “xmlrpc.php”>
Allow from all
</ FilesMatch>

2. Uninstall Jetpack plugin and install it again

3. Activate Jetpack and go to settings (if failed, go to step 4)

4. Disable and enable Jetpack plugin

5. After a while, enable Jetpack and configure again

After that, when the site health check was executed, “xxxxxxxx Not connected.: 200” was still displayed as “1 fatal problem”, so this problem has not been resolved.

Hi there,

Thank you for updating us that everything has been resolved. However, let us know if you encounter any more issue and we’d be happy to take a look for you.

Thanks!

Hello darnelldibbles,

Thank you for your reply immediately.
Unfortunately, not all issues seemed to be communicated.

Not all problems have been solved yet!

My website diagnostics “Site Health Check” still shows fatal errors.
The same phenomenon occurred on my other test server. As a trial, it was the same even if I downgraded to WP5.3.2. Isn’t this a bug in the Jetpack plugin (site-health.php?)?

Site health status
Fatal problem
“My site name” is not connected .: 200

Today, Jetpack has been updated to 8.4.1, but the following error is still displayed.

1 fatal problem

Wpcom Connection Test

My site name is not connected .: 200

Contact Jetpack support.

The same applies if you downgrade WordPress to 5.3.

Okay, thank you for the information. I know that you have attempted a fresh install to no avail, but now that everything is updated, I was wondering if you can try everything again following these steps:

• From the wp-admin dashboard of your site, please go to Jetpack > Dashboard > Connections > Manage site connection from your left-hand menu.
• Click the “Disconnect” button. If it’s already disconnected, you can skip to the next step.
• Deactivate your Jetpack plugin by heading to Plugins > Installed Plugins and finding “Jetpack by WordPress.com.”
• Completely uninstall Jetpack.
• Reinstall the newest version of Jetpack.
• Deactivate all of your plugins.
• Activate only Jetpack.
• Back in Jetpack > Dashboard > Connections > Manage site connection, Click the “Set up Jetpack” button and continue through the approval process.

Please let me know the results of this troubleshooting and we can go from there. Thanks!

Hi Darnelldibbles,

Thanks for the detailed explanation for the solution.
I tried it immediately.
This time I experimented with two websites.
One is a “https” site (https://senris.com) and the other is a non-public, “http” unencrypted site.

Report the result.

For unencrypted sites with “http”, following the steps to enable Jetpack and perform a site health check, no fatal error was displayed.
For unencrypted sites, Jetpack seems to work properly with the above steps.

However, for non-encrypted sites of “https”, following the steps to enable Jetpack and perform a site health check, the same fatal error was displayed as before.

Wpcom Connection Test
My site name is not connected.: 200
Contact Jetpack support.

After all, encryption sites don’t seem to have improved.

Correction of description errors (the following is correct)

However, for encrypted sites of “https”, following the steps to enable Jetpack and perform a site health check, the same fatal error was displayed as before.

Wpcom Connection Test
My site name is not connected.: 200
Contact Jetpack support.
After all, encryption sites don’t seem to have improved.

P.S.

After performing the above procedure to disable all plug-ins of the encrypted site (senris.com), a serious problem occurred on the site after the plug-in was activated.
And the database was restored to the normal state to restore the website to normal status I have to start over from restoration.

Therefore, please pardon the test of disabling the plug-in in the future.
In the site health check, a fatal error that the connection has been cut is issued, but actually the connection between Jetpack and WordPress is in place, so there is no particular problem in operation, so I think I will operate my site in this status for the time being.
We would like you to fix the bug of Jetpack so that it works only by replacing Jetpack. Those that are not are unfortunately useless.

Thanks for the troubleshooting and the update. If you could please contact us so that Jetpack staff can further look into this issue for you?

https://jetpack.com/contact-support/

Thanks again,

Hi darnelldibbles,

I’ve already contacted Jetpack Support.
Thank you for this time.