Sign in Get Started

Fix Jetpack Issues

Last updated:

Have trouble connecting Jetpack to your website, or with some other Jetpack feature? If so, here are the recommended steps to troubleshoot common Jetpack problems.

Before troubleshooting, check that your site is publicly available; Jetpack will not be able to connect to it otherwise! You can learn more about why it’s necessary to have your WordPress.com account connected to Jetpack.

Check for a Jetpack service outage

Is Jetpack having an outage? Check automatticstatus.com for current service status and any scheduled maintenance. If everything there is operational, the problem is most likely specific to your site. Continue with running the Jetpack Debug Tool.

If the status page shows an outage or maintenance that affects Jetpack, wait until it is marked as resolved, then check your site again.

https://automatticstatus.com is the official status page for Jetpack.

Run the Jetpack Debug Tool

The Jetpack Debug Tool (jptools.wordpress.com/debug/) can identify many different causes for connection issues. To verify your Jetpack connection, visit your website, copy the URL from your browser’s address bar, and paste it into the Jetpack Debug. If your connection works and all tests pass you will see the message “Everything looks great!”.

If you get an error, try reconnecting Jetpack using these exact steps:

  1. Log in to the WP Admin dashboard of your site and go to Jetpack → My Jetpack.
  2. At the bottom of the page, click on Site and account connected.
  3. On the modal that shows up, click Disconnect Jetpack.
  4. Follow the rest of the prompts until the disconnection is confirmed complete.
  5. Go to Jetpack → My Jetpack.
  6. Click the Supercharge my site button and complete the connection process.
  7. Check the Jetpack Debug at https://jptools.wordpress.com/debug/ for your site again. If there is still an error, continue checking for other issues listed on this page.

Error messages

Seeing an error message when trying to connect Jetpack or from the Jetpack Debug Tool above? Some examples are:

  • Operation timed out
  • Connection error
  • cURL error 60
  • XML‑RPC is not responding correctly

Visit the Error Messages page to see the most common errors, their causes, and how to resolve them.

Check known issues

Check the Known Issues list for any conflicts. If you are using a plugin or theme listed there, and cannot use an alternative, then Jetpack may not work for you.

Check your xmlrpc.php file

Jetpack needs this file to connect to your website.

Start by checking yourjetpack.blog/xmlrpc.php (replacing “yourjetpack.blog” with your actual domain) in your web browser’s address bar. That page should return the following message: XML-RPC server accepts POST requests only.

The message you see should look exactly the same as written above, without any spaces or line breaks above or below it, and without any other text. Compare yours to this working example.

  • If you see this message, but it is not on a line by itself, a theme or plugin may be displaying extra characters when it shouldn’t. Check for plugin or theme conflicts.
  • If you get a 404 error or “Not Found” message, contact your webhost. They may have security in place that is blocking the XML-RPC file, which can cause issues with Jetpack and other plugins.
  • The XML-RPC file may not be in the root folder of your WordPress install, in which case Jetpack will not be able to connect. Reinstalling the core of WordPress should replace it, or you can ask your host to do so.

WordPress.com requests to your site are being blocked

Jetpack shows this notice when your host’s firewall, web application firewall (WAF), or a security rule blocks WordPress.com from reaching xmlrpc.php on your site:

WordPress.com requests to your site are being blocked, usually by a firewall or security rule. See Site Health for details and next steps.

The notice appears on any WP Admin page. It offers a Visit Site Health link instead of a reconnect option, because reconnecting does not fix a blocked request. Your connection tokens are still valid; the requests carrying them are being stopped before they reach your site.

To resolve it:

  1. Go to Tools → Site Health and review the Jetpack items in the report for the full diagnosis and next steps.
  2. Ask your webhost whether a firewall, WAF, or server rule blocks requests to xmlrpc.php, and ask them to allow requests to xmlrpc.php from Jetpack’s IP addresses.
  3. If you run a security plugin, check whether it blocks xmlrpc.php and add an exception for Jetpack’s IP addresses.

Jetpack rechecks this once a day. The notice clears on its own within about a day after the block is removed. You do not need to disconnect or reconnect Jetpack.

Note that this notice does not appear on WordPress.com-hosted sites.

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:

  1. Deactivate all other plugins and keep Jetpack active.
  2. Try connecting again.
  3. If Jetpack connects, you can turn your plugins back on, one by one, to make sure everything keeps working.

A conflict may cause other issues in addition to not letting Jetpack connect, so check for anything else not working properly after activating each plugin. If you find that a plugin is causing a conflict with Jetpack, please reach out to that plugin’s developers to see if there is a fix to get it working with Jetpack.

Theme issues

If you have a display issue, or the plugin troubleshooting doesn’t help, install and activate one of the default WordPress themes (such as Twenty Twenty Two), then try again. If Jetpack features start working normally, then it means that something in your other theme is likely broken or incompatible, and you should get in touch with that theme’s authors. Be sure to let them know the troubleshooting steps that you’ve already tried.

Site Health

The Site Health section in WP Admin (under Tools → Site Health) provides critical information about your WordPress configuration as well as any other items that may require your attention.

Additionally, Jetpack rechecks its connection to WordPress.com once a day and reports the result in Site Health. If WordPress.com requests to your site are being blocked, Site Health shows the full diagnosis and the next steps, and the result clears within about a day after the block is removed.

Jetpack Connection checks in Site Health

Jetpack adds a set of connection checks to the Site Health report. They carry a Jetpack Connection badge. Failing checks appear at the top of the Status tab with a description and a recommended action. Passing checks are grouped under Passed tests at the bottom of the page.

To review them:

  1. Go to Tools → Site Health in WP Admin.
  2. 2. Open the Status tab.
  3. 3. Look for items badged Jetpack Connection.
  4. 4. Expand Passed tests to see the checks that succeeded.

What the Jetpack Connection results mean

Each failing check shows a message that describes the problem and a recommended next step. Find the message you see in the list below.

Connection and tokens

  • Your site is not connected to WordPress.com — Jetpack has no active connection to WordPress.com. Reconnect your site to WordPress.com.
  • The site token used to authenticate with WordPress.com is missing., Missing token for the connection owner., The site token used to authenticate with WordPress.com could not be validated., or Invalid Jetpack Connection tokens. — The tokens Jetpack uses to authenticate with WordPress.com are missing or WordPress.com no longer accepts them. Common causes are a site migration, a database restore, or a partial disconnection. Reconnect your site to issue new tokens.
  • The user who set up the Jetpack Connection no longer exists on this site. — The connection owner (the user account that connected Jetpack) was deleted. Reconnect your site using a current administrator account.
  • The user (username) who set up the Jetpack Connection is not an administrator. — The connection owner lost the Administrator role. Give that user the Administrator role again, or reconnect your site with a different administrator account.

URL mismatch

  • Your home URL is set as … but your Jetpack Connection lists it as …, Your site URL is set as … but your Jetpack Connection lists it as …, or A URL mismatch was detected between your site and WordPress.com. — The site’s address changed after Jetpack was connected. This happens after a domain change, a switch from http to https, or when a staging copy of the site is connected. Check that the WordPress Address and Site Address under Settings → General are correct, then contact Jetpack support.

Requests blocked by your site

Two different problems share the title Your site is blocking requests from WordPress.com. Read the description under the title to tell them apart. Reconnecting does not fix either one.

  • WordPress.com reached your site but the request was blocked. (sometimes followed by an HTTP status, such as HTTP 403) — A security plugin, firewall, web application firewall (WAF), or server rule rejected WordPress.com’s request to your site’s xmlrpc.php file. Ask your host or security provider to allowlist Jetpack Connection IPs.
  • WordPress.com could not establish a secure connection to your site because your site’s SSL certificate could not be verified. — Your SSL certificate is expired, self-signed, or missing an intermediate certificate. Ask your hosting provider to renew the certificate or complete its certificate chain. See SSL Certificates below for how to check your certificate.

After the block or certificate is fixed, this result clears within about a day.

Server configuration

  • The server port value is unexpected. — Your server reports a port other than 80 or 443. The message includes a line of code, for example define( 'JETPACK_SIGNATURE__HTTPS_PORT', 8443 ). Add that exact line to your wp-config.php file. This check is skipped when your site URL already includes a port number.
  • PHP XML manipulation libraries are not available. — The PHP XML extension is not installed on your server. See The PHP-XML Extension below.

Other connection test failures

  • Connection test failed (sometimes followed by an error code or a status code) — WordPress.com ran its connection test against your site and it failed for a reason not listed above. Reconnect your site to WordPress.com. If the result comes back, contact Jetpack support and include the full message.

Skipped checks

A skipped check is not a failure. Jetpack skips the WordPress.com connection test when:

  • Your site is in Offline Mode or Safe Mode.
  • Your site is not communicating with WordPress.com.
  • An earlier Jetpack Connection check failed. Fix that check first, then reload Site Health.

The connection owner checks are skipped when the site is connected to WordPress.com without a user. That is expected and does not need fixing.

Two skipped results are about timing, not a fault on your site: The test timed out which may sometimes indicate a failure or may be a false failure. and WordPress.com could not complete the connection test. This is usually temporary. Reload Site Health later. If the result keeps appearing, contact Jetpack support.

Specific configurations

Your wp-config.php and .htaccess files

If you or one of your plugins added code to the .htaccess or wp-config.php files, it may have caused a misconfiguration. You can check these guides for more information and typical settings to help revert the files back to their default state: wp-config / htaccess.

The PHP-XML Extension

The PHP on your site needs the XML extension in order to parse XML, which Jetpack needs to properly communicate with your site. Check with your webhost’s customer support team to make sure the PHP-XML extension is installed and active on your server.

The JSON API (REST API)

Jetpack uses XML-RPC and the JSON API (REST API) to communicate with your site. Please ensure that the JSON API is enabled on your site and that authentication is disabled. If you would prefer not to disable authentication on the JSON API for your site, please allowlist the /jetpack/v4/ and /wpcom/v2/ namespaces instead. If you’re not sure how to do this, please contact your webhost’s customer support team for help.

Cloudflare

If you are using Cloudflare on your site, check this guide to make sure Jetpack and Cloudflare are working together properly.

Test your site speed

Your site must initially respond within 5 seconds for the Jetpack connection to work correctly.

You can check your site speed and overall performance with a variety of tools (like GTmetrix or WebPageTest) and follow up with your webhost by showing them the results. They may be able to help improve your site’s response and loading times from there.

SSL Certificates

Your SSL certificate makes sure the traffic on your site is safe and secure. Sometimes they can be misconfigured or expired, which will keep Jetpack from connecting to it. You can check for errors on your SSL certificate with this SSL Checker and test its overall health with this SSL Server Test. It should typically be graded A or A+, and you shouldn’t see any errors.

The most common SSL errors that your webhost must fix are:

  • Self-signed: The certificate was not created by using standard security practices and is considered unsafe
  • Missing chain/intermediate certificate: Some SSL certificates are applied to your site in multiple parts. When one or more are missing in the chain, the security becomes broken and incomplete
  • Expired: Just like a domain, an SSL certificate needs to be renewed each year, or it will expire. Certificate renewals usually happen without you having to do anything, but sometimes automatic systems at your webhost may fail to do so

HTTPS

  • Check that both the SITE_URL and HOME_URL settings under Settings → General in your WP Admin are using https before your domain rather than just http (without the “s”). Sites that use only http are not secure and aren’t using the SSL certificate mentioned above – https loads the certificate properly and will allow Jetpack to connect to it.
  • Also, make sure that all of your site’s traffic routes to https as well. For example, any requests to http://yourjetpack.blog should automatically redirect to https://yourjetpack.blog instead. Your webhost can help make sure that this happens as expected.
  • For more detailed information on troubleshooting SSL issues, please refer to this guide.

Database Errors from Jetpack Sync

Under certain configurations, you may see the following error in your site’s error_log:

[13-Oct-2025 07:58:53 UTC] WordPress database error Commands out of sync;
you can't run this command now for query SELECT option_value FROM wp_options
WHERE option_name = 'jpsq_sync_checkout' made by shutdown_action_hook, 
do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, 
Automattic\Jetpack\Sync\Sender->do_sync, 
Automattic\Jetpack\Sync\Dedicated_Sender::spawn_sync, 
Automattic\Jetpack\Sync\Queue->is_locked, Automattic\Jetpack\Sync\Queue-
get_checkout_id [13-Oct-2025 07:58:53 UTC] WordPress database error 
Commands out of sync; you can't run this command now for query SELECT 
COUNT(*) FROM wp_jetpack_sync_queue WHERE queue_id = 'sync' made by 
shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, 
Automattic\Jetpack\Sync\Sender->do_sync, 
Automattic\Jetpack\Sync\Dedicated_Sender::spawn_sync, 
Automattic\Jetpack\Sync\Queue->size, 
Automattic\Jetpack\Sync\Queue\Queue_Storage_Table->get_item_count

If you are seeing this message, the solution is to add a custom PHP code snippet to your site:

add_action( 'shutdown', 'wordpress_check_database_connection', 0 );
function wordpress_check_database_connection() {
    global $wpdb;

    $wpdb->check_connection();
}

We have instructions on how to do that at:

Developer mode

If you were using Development Mode, check your wp-config.php file and make sure that define('JETPACK_DEV_DEBUG', true); is no longer present.

Server credentials for Jetpack Backup

If you have issues adding your credentials to Jetpack Backup, we recommend contacting your webhost and asking them to provide you with this information so you can then enter it successfully into your Jetpack settings:

  • Credential type (FTP, SFTP, SSH)
  • Server address
  • Port number
  • Server username
  • Server password
  • WordPress full installation path (this is where WordPress is installed on your server)

Reinstall and reconnect Jetpack

Sometimes you need to completely reset your connection between your site and our services. You can follow these instructions to accomplish that.

Contact your webhost

These issues must be addressed by your hosting provider rather than Jetpack support; they are server-related:

  • SSL certificates
  • Changes in IP addresses or domains/URLs
  • Migration from one server to another
  • Site is down or not responding
  • Errors (500 / 502 / 504 / 403)
  • Server resource or memory usage
  • DNS problems
  • Outdated server software (PHP, MySQL, etc.)
  • File and folder permissions
  • Problems that are still occurring even after Jetpack is uninstalled

Still need help?

Please contact support. We’re happy to advise.

In this section