Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix Jetpack Connection Errors

Short answer

To fix a Jetpack connection error, run the Jetpack Debug Tool for your site, check that xmlrpc.php returns the exact message “XML-RPC server accepts POST requests only.”, and then disconnect and reconnect Jetpack from Settings → Connectors. If the debug tool still reports a block, ask your host to allow WordPress.com requests to xmlrpc.php. Most errors come from a blocked xmlrpc.php file, a firewall rule, an expired token, or a DNS change.

Key takeaways

  • Jetpack connects your self-hosted site to WordPress.com through xmlrpc.php, so a block on that file breaks the connection.
  • The Jetpack Debug Tool shows “Everything looks great!” when every connection test passes.
  • Disconnecting Jetpack loses no stats or followers, but deleting the plugin resets its settings.
  • After a DNS change, Jetpack advises waiting 24 to 72 hours before you try to connect again.
  • Jetpack rechecks a blocked-request notice once a day, and it clears within about a day after the block is removed.
  • A site must respond within 5 seconds at first for the Jetpack connection to work.

What does a Jetpack connection error mean?

A Jetpack connection error means your site and WordPress.com cannot complete the link that Jetpack needs to work.

Jetpack links a self-hosted WordPress site to a WordPress.com account. Many of its features need that link, so a failed connection can stop stats and backups. Jetpack's fix guide states that Jetpack will not connect to a site that is not publicly available, as of November 2026.

The error can appear in WP Admin, in the Jetpack Debug Tool, or when you try to connect. Starting with Jetpack 16.4, the same messages also appear on the Jetpack Connection card in Settings → Connectors, according to Jetpack's error messages guide. That card needs WordPress 7.0 or later.

What causes Jetpack connection errors most often?

The most common causes are a blocked xmlrpc.php file, a firewall rule, an old token, or a recent site change.

Jetpack connects to WordPress.com through your site's xmlrpc.php file. If a security plugin, a firewall, a web application firewall, or a host rule blocks that file, WordPress.com cannot reach your site. A full list of Jetpack modules is not needed to fix this, but the connection itself must work first.

Other common causes include a changed domain, a move from HTTP to HTTPS, a site restore, or a deleted connection owner. Jetpack's Site Health checks list missing or invalid tokens after a migration or a database restore, as of November 2026.

A password-protected site or a private network can also stop the check, because WordPress.com must load your site to verify it.

How do you check whether Jetpack is really connected?

Run the Jetpack Debug Tool for your site address and read its result before you change anything.

Open the Jetpack Debug Tool, paste your site URL, and run the tests. If your connection works and all tests pass, you will see the message “Everything looks great!”, according to Jetpack's fix guide. That result tells you the link is working at that moment.

Also check WP Admin. Go to Settings → Connectors and look at the Jetpack Connection card.

A “Connection error” or “Needs attention” badge means something is wrong, and Details shows the error. Jetpack also adds connection checks to Tools → Site Health.

Check the status page first if many sites are affected. Automattic Status is the official status page for Jetpack. If it shows an outage, wait until it is marked as resolved, then check your site again.

How do you reconnect Jetpack in the right order?

Disconnect the site, then connect it again from the Jetpack Connection card in Settings → Connectors.

Follow these steps as an administrator, in this order:

  1. Go to Settings → Connectors in WP Admin.
  2. Click the Details button on the Jetpack Connection card.
  3. Click “Disconnect site” at the bottom of the card, then click Disconnect to confirm.
  4. Click Connect on the same card and complete the connection process.
  5. Run the Jetpack Debug Tool for your site again.

Jetpack's reconnect guide gives these exact steps and notes that disconnecting is often the best place to start. When you disconnect Jetpack, no data are lost, including stats and followers, and your settings will be restored when you reconnect.

If the card shows the “Site registered” badge, the site is registered but no account owns the connection. Click Details, then click “Connect account” to link an administrator account.

If a reinstall is needed, deactivate and delete Jetpack from Plugins → Installed Plugins, then install it again from Plugins → Add New. Deleting Jetpack resets its settings.

How do you fix a blocked or broken xmlrpc.php file?

Open your site's xmlrpc.php address in a browser and check that it shows one exact line of text.

Open your own domain followed by /xmlrpc.php in a browser, and look for this message: “XML-RPC server accepts POST requests only.” Jetpack's fix guide states that the message must look exactly the same, with no spaces or line breaks above or below it, and no other text.

Use this table to read the result:

What you seeWhat it meansNext step
Exact message on one linexmlrpc.php responds as expectedTry reconnecting Jetpack
Extra text or blank lines above itA plugin, theme, or wp-config.php file adds outputCheck for plugin or theme conflicts
404 or Not FoundThe file is missing or blockedContact your host
403 or a block pageA firewall or security rule blocks itAsk your host to allow WordPress.com requests

If WordPress.com requests are being blocked, Jetpack shows a notice that says the requests are being blocked, usually by a firewall or security rule. Reconnecting does not fix that notice, because your tokens are still valid and the requests are stopped before they reach your site.

Go to Tools → Site Health, review the Jetpack items, and ask your host to allow requests to xmlrpc.php from Jetpack's IP addresses. Jetpack rechecks this once a day, and the notice clears within about a day after the block is removed.

What do the common Jetpack error messages mean?

Each message points to a different cause, so read the exact words before you pick a fix.

“An error occurred. Please try again.” is the generic message in Jetpack 16.4 and later, and it usually means an XML-RPC problem.

Check xmlrpc.php first, then try to connect again. “Blog Token Validation” means the security token is outdated or invalid, and Jetpack advises deactivating and deleting the plugin, then reinstalling it.

“Couldn't resolve host” usually means you tried to connect too soon after a new domain or a DNS change. Jetpack advises allowing between 24 to 72 hours between your changes and when you try to connect Jetpack, as of November 2026.

If the error is still there after 72 hours, check that your A records and name servers are set to the new DNS.

“Communication error” means Jetpack has general trouble talking to WordPress.com. Check xmlrpc.php first, then check that your domain loads only over HTTP or only over HTTPS, not both.

“Your site asks visitors to log in” means a login prompt stops WordPress.com from loading your site, so turn off password protection or maintenance mode, connect Jetpack, then turn it back on.

“Too many connection attempts” means your site made too many tries, so wait an hour, then connect again. “Unable to Insert Blog” means the site URL was stored in the wrong way on the WordPress.com side, so try again in a few minutes.

The full list is in Jetpack's error messages guide.

How do you fix SSL, DNS and timeout errors?

Fix the certificate, the address, or the server response first, because Jetpack cannot connect through a broken secure link.

For “cURL error 60”, Jetpack cannot verify your site's SSL certificate. Contact your host and ask them to supply the entire SSL certificate chain.

Common faults are a self-signed certificate, a missing intermediate certificate, and an expired certificate. Check that both addresses under Settings → General use https, and that http requests redirect to https.

For a timeout, your site must initially respond within 5 seconds for the Jetpack connection to work, according to Jetpack's fix guide. A slow server can fail the connection test even when the link is working.

Ask your host to check server load and response time, and to confirm that it is not limiting concurrent PHP connections.

Jetpack's error guide states that asking your host to change the PHP_FCGI_CHILDREN setting to 2 will solve many timeout cases. That setting allows Jetpack to send and receive network requests at the same time.

If your server cannot send requests to WordPress.com at all, Jetpack shows a failed outbound HTTP error, and your host must confirm that outbound HTTP and HTTPS requests to WordPress.com are allowed.

What do Jetpack HTTP error codes mean?

A code tells you which side rejected the request, so match the code to the cause below.

Jetpack connects through xmlrpc.php, and when that request fails, the host or WordPress.com returns a numeric status code. These codes can appear in connection errors, in the Jetpack Debug Tool, or in your server logs, according to Jetpack's HTTP code guide.

CodeMeaningFirst fix
400Request was invalid or badly formedCheck Settings → General URLs and clear the cache
401Credentials are missing or wrongLog out and log back in, then try again
403Server refuses the requestAllow Jetpack IP addresses to reach xmlrpc.php
404xmlrpc.php cannot be foundCheck Settings → General URLs and contact your host
429Too many requestsWait, then ask your host to check rate limits
500Server error on your hostCheck the PHP error log and contact your host
502, 503, 504Gateway or upstream server problemWait briefly, then contact your host

A 403 often means a security plugin or a server rule blocks Jetpack, while a 404 often means WordPress is in a subdirectory. A 500 error is a server-side error, so check the PHP error log for entries from the time the error appeared.

If you use Cloudflare, a 409 error can mean Cloudflare is handling xmlrpc.php, so set Cloudflare to bypass its features for xmlrpc.php and WP Admin. Our guide to setting up Cloudflare for WordPress covers the settings that affect this link.

How do you check plugin, theme and REST API conflicts?

Turn off other plugins, test the connection, then turn them back on one at a time.

To rule out a plugin conflict, deactivate all other plugins and keep Jetpack active, then try connecting again. If Jetpack connects, turn your plugins back on, one by one, to find the one that breaks it.

Plugins that block xmlrpc.php, restrict the REST API, or add maintenance mode are known to cause this problem. If you need to turn off a feature rather than remove the plugin, read our guide on how to disable Jetpack modules before you change settings.

For a theme check, install and activate a default WordPress theme, such as Twenty Twenty Two, then try again. If Jetpack starts working, the fault is in your other theme, and you should contact that theme's authors with the steps you tried.

Jetpack uses XML-RPC and the REST API to talk to your site. If a plugin needs login for the REST API, allow the /jetpack/v4/ and /wpcom/v2/ namespaces instead, or turn that plugin off while you test.

Jetpack's fix guide also states that the PHP XML extension must be installed on your server, because Jetpack needs it to parse XML. Ask your host to confirm that the extension is active.

When should you contact your host?

Contact your host when the fault is on the server, not in a setting you can change in WP Admin.

Ask your host for help if xmlrpc.php returns 404 or 403, if the SSL chain is incomplete, or if outbound requests to WordPress.com fail.

Jetpack's fix guide lists SSL certificates, DNS problems, server errors such as 500, 502, and 504, file permissions, and outdated server software as issues your host must address.

A cURL error 28 guide can help you read a timeout, but the host still needs to fix a server-side timeout.

Give your host the exact error text, the time it happened, and the Jetpack Debug Tool result. Ask them to confirm that xmlrpc.php is reachable and that no firewall rule blocks WordPress.com requests.

If the host confirms the server is fine and the error is still there, contact Jetpack support with the full Site Health message.

Before you contact anyone, check that your site URL is correct in Settings → General. A URL mismatch after a domain change, a switch from HTTP to HTTPS, or a staging copy can break the link.

If you are unsure whether Jetpack is worth the effort for your site, read is Jetpack worth it after the connection is fixed, not before.

What mistakes should you avoid?

Do not keep reconnecting without reading the error, and do not delete the plugin before you try a clean reconnect.

  • Do not reconnect again and again after “Too many connection attempts”; wait an hour first.
  • Do not block xmlrpc.php to stop brute-force logins without an exception for WordPress.com, because Jetpack needs that file.
  • Do not leave a maintenance mode plugin on while you connect, because WordPress.com must load your site.
  • Do not change the domain or the HTTP to HTTPS setting and try to connect in the same hour; allow 24 to 72 hours for DNS.
  • Do not ignore Site Health; the Jetpack Connection checks name the exact fault and the next step.
  • Do not delete Jetpack as a first step; deleting resets its settings, while disconnecting keeps them.

Frequently asked questions

Why does Jetpack say my site is not connected after a migration?

A migration or database restore can leave Jetpack with a missing or invalid token, or a URL that no longer matches your site address. Check Settings → General for the correct WordPress Address and Site Address, then disconnect and reconnect Jetpack from Settings → Connectors. That step issues new tokens and links the current address.

Can I fix a Jetpack connection error without deleting the plugin?

Yes, in most cases. Run the Jetpack Debug Tool, check xmlrpc.php, and try a clean disconnect and reconnect first. Deleting the plugin is a later step for a token fault that a reconnect does not fix. Deleting resets Jetpack settings, while disconnecting keeps them, so try the reconnect first.

How long should I wait after a DNS change before connecting Jetpack?

Allow 24 to 72 hours after registering a new domain or changing DNS before you try to connect Jetpack. If the error is still there after 72 hours, check that your A records and name servers point to the new DNS. Your host can confirm the correct records if you are unsure.

Does disconnecting Jetpack delete my stats or followers?

No. Disconnecting Jetpack loses no data, including stats and followers, and your settings will be restored when you reconnect. Stats cannot be collected while Jetpack is disconnected, so a long gap can leave a gap in your stats after you reconnect. Deleting the plugin is different, because it resets your settings.

What should I tell my host when Jetpack will not connect?

Give your host the exact error message, the time it happened, and the Jetpack Debug Tool result. Ask them to check that xmlrpc.php is reachable, that WordPress.com requests are allowed, and that outbound HTTP and HTTPS requests work. Also ask them to check the SSL chain, the PHP XML extension, and any firewall rule that blocks Jetpack.

Sources

  1. Fix Jetpack Issues Jetpack
  2. Troubleshoot Jetpack connection error messages Jetpack
  3. HTTP code guidance for Jetpack sites Jetpack
  4. Reconnect and reinstall Jetpack Jetpack
  5. Known issues Jetpack
  6. Jetpack Debug Tool Jetpack
  7. Automattic Status Automattic
  8. Jetpack – WordPress plugin WordPress.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test