Have trouble connecting Jetpack to WordPress.com? If so, here are some steps that might help you solve the problem. Before following these steps, first check that your site is publicly available, as Jetpack will not be able to connect otherwise.
You can find the importance to have a WordPress.com account connected to the Jetpack here.
Check if the error you received is listed on this page. If it is, follow the instructions there to fix the issue.
Run the Jetpack Debug Tool
The Jetpack Debug will identify any issues with the connection.
Seeing an error message when trying to connect Jetpack or in the Jetpack Debug tool above?
Visit the Error Messages page to see the most common errors, as well as what they mean and how to resolve them.
Check Site Health
Check your site’s health status under Tools > Site Health.
This page will run a number of different checks and provide both critical information about your WordPress configuration as well as any items that may require your attention.
Check your xmlrpc.php file
Jetpack needs this file to connect to WordPress.com. You can perform two checks here, and both of them should work:
yourdomain.com/xmlrpc.php(replacing yourdomain.com with your actual domain in your browser’s address bar). This page should return the following message:
XML-RPC server accepts POST requests only.
The message should look exactly the same, without any spaces or line breaks. Please feel free to compare yours to this working example.
If you have blank lines or extra content in XML-RPC, you will receive an error. Please check here how to fix it before you continue.
Note that, as in our example, your xmlrpc.php file must be in the home directory of your WordPress install. If it is not, you can replace it by reinstalling the core of WordPress (or ask your hosting support to).
- If you passed that test, enter your site’s URL into the WordPress XML-RPC Validation Service. Leave all of the defaults as they are, and don’t provide any usernames or passwords if prompted. If you see “Congratulations! Your site passed the first check,” you’re done and have passed the second check.
If something is off with your xmlrpc.php file in either of these two checks, please contact your hosting support for assistance in getting that file working properly.
Check for the PHP XML extension
PHP needs the XML extension in order to parse XML, which Jetpack needs to properly communicate with your site. Check with your host to make sure the PHP XML extension is installed and active on your server.
Reinstall and Reconnect Jetpack
Sometimes you need to reset your connection between your hosting server and our services. You can follow these instructions to accomplish it:
If you are having issues with the Jetpack connection and you are using Cloudflare, check how to use Jetpack and Cloudflare together.
Look for Plugin Conflicts
Sometimes other plugins can create a conflict with Jetpack that blocks it from connecting to WordPress.com.
To rule out a plugin conflict, disable all other plugins and keep Jetpack active, then try connecting again. If Jetpack connects, you can turn your plugins back on, one by one to make sure everything keeps working.
Note that a conflict may cause other issues in addition to not letting Jetpack connect, so monitor for anything else not working properly. If that plugin is causing a conflict with Jetpack, please reach out to that plugin’s authors to see if there is a fix to get it working with Jetpack.
Check for Theme Issues
If you’re using a theme that’s not coded up to modern standards or kept up-to-date with changes in WordPress development, then the theme could be creating issues with Jetpack’s connection.
Download and temporarily switch to one of the more minimal, default WordPress themes (like Twenty Twenty) and see if the connection issues are resolved. If so, then you’ll need to either replace your original theme or talk to its authors to see if they can figure out what isn’t working with Jetpack.
Test Your Site Speed
Your site must initially load within 5-10 seconds for the Jetpack connection to work correctly.
Check Your SSL Certificate
If you’re using an SSL Certificate for your site (and you should!), you can check its grade at SSL Labs.
It should typically be graded A or A+, and you shouldn’t see any errors. The most common errors are that the certificate is self-signed or that the certificate chains are missing.
Check that both
HOME_URL under Settings > General in your wp-admin dashboard are using HTTPS before your domain rather than just HTTP.
For more information on troubleshooting SSL issues, please refer to Fixes for the most common SSL certificate errors.
Server credentials for Jetpack Backup
If you have issues adding your credentials to the Jetpack Backup, we recommend contacting your hosting support, asking them to confirm the information below.
You need to request to the hosting this information:
WordPress full installation path
wp-config.php or .htaccess misconfigured
Both files doesn’t require changes for Jetpack since it relies on the WordPress setup.
You can check the default configuration for WordPress:
When you should contact your hosting support
This list of issues must be addressed to your hosting support because they are server-related.
- SSL certificate
- Change IP or domain URL
- Migrated from one server to another
- My site is down
- Site error 500 / 502 / 403
- Server resources usage
- Memory usage
- DNS issues: not propagated, not set correctly
- Loading issues
- Outdated server software (PHP, MySQL, etc)
- File and folder permissions (CHMOD)
Other WordPress Issues
If you deactivate and delete the Jetpack plugin and you still continue to see errors or problems on your site, then those errors are most likely related to your site’s WordPress installation or other plugins that you may have installed.
In this case (when you’re sure that the issue is not related to Jetpack), you should reach out to your hosting provider or the WordPress.org support forums for help.
If you continue to have connection issues or if you have any other questions related to Jetpack, please feel free to contact support for assistance.