Troubleshoot Jetpack connection error messages

Understand error messages that may occur when connecting your site to your WordPress.com account, and find steps to fix them.

An error occurred. Please try again.

If you see this generic error message while trying to connect Jetpack, it usually means there is an issue with XML-RPC on your site. Please refer to this guide to resolve any XML-RPC issues, then try to connect Jetpack again.

Couldn’t resolve host

Error details: The Jetpack server was unable to communicate with your site [IXR -32300: transport error: http_request_failed Couldn't resolve host 'example.com']

This typically means that you are trying to connect Jetpack too soon after registering a new domain or making changes to your DNS.

In both cases, you must allow between 24 to 72 hours between your changes and when you try to connect Jetpack.

If you are still seeing this error after 72 hours, check your URL on the Site Profiler, and verify that the A RECORDS and NAME SERVERS are properly set to your new DNS. If you’re unsure of what the A RECORDS and NAME SERVERS of the new DNS should be, please contact your web hosting provider.

Communication error

This error means that Jetpack is having general trouble communicating with WordPress.com.

As a first step, check that xmlrpc.php is properly setup by following this guide.

If the XML-RPC connection is fine, then check that your domain loads only over HTTP or HTTPS, but not both. For help with redirecting HTTP traffic to HTTPS, please contact your host. Once it’s redirected, reconnect the site to Jetpack.

Operation timed out, Connection timed out

There are two common error messages that indicate a timeout has happened. Those are:

Error details: The Jetpack server was unable to communicate with your site [IXR -32300: transport error: http_request_failed Operation timed out after 15001 milliseconds with 0 bytes received]

Or:

cURL error 28: Connection timed out after 10000 milliseconds

Those messages indicate that the hosting provider is limiting concurrent PHP connections. To fix this, please contact your web host to:

• confirm they are not blocking Jepack from their end
• ask whether they are limiting incoming and outgoing connections over XML-RPC

Jetpack needs to be able to send and receive network requests at the same time, which means it needs concurrent PHP processes. Most commonly, asking your host to change the PHP_FCGI_CHILDREN setting to 2 will solve this issue. Once the host confirms they have done this, please try re-connecting Jetpack by following this guide.

Unable to Insert Blog

This error means there’s an issue with the way your site’s URL has been stored in our system. This is something we’ll need to fix on our end. Please get in touch with support for help.

Jetpack encountered an error and was unable to display the Dashboard

This error typically occurs when you have PHP errors configured to be output on the front end of the site. These errors can interfere with the Jetpack API and prevent the dashboard from loading.

The solution is to disable the output of PHP errors on the front end. You can follow this guide to accomplish this. If you’re still experiencing this error after disabling the output of PHP errors, please contact support.

cURL error 60 – SSL: unable to get local issuer certificate

Error details: [http_request_failed] cURL error 60: SSL certificate problem: unable to get local issuer certificate [-10520]

Jetpack is unable to connect because it cannot verify the site’s SSL certificate. Please contact your web host and ask them to configure the site’s server to supply the entire SSL certificate chain. You can use this online tool to check for issues with the certificate chain.

Server error code 500

Error details:string(60) -32301: transport error – HTTP status code was not 200 (500)

This is a server-side error from your web host. You will need to debug the PHP code by checking the PHP error log to see if there are any notices from around the time this error showed up. If you’re unsure on how to debug PHP code, please contact your web hosting provider for assistance.

Error code 409 – XML-RPC is not responding correctly

Sites that proxy traffic through Cloudflare or other CDNs might see an error 409 in the Jetpack Debugger Tool. 

If you are using Cloudflare, please configure it to bypass Cloudflare’s features for xmlrpc.php and WP Admin by following this guide.

Missing_secrets

This error message suggests some kind of caching issue. If you use a caching plugin on your site, try flushing the cache. If that doesn’t help, try to install this small plugin to purge your object cache. Once done, please try re-connecting Jetpack by following the steps here.

Verify secrets missing

Error details: [verify_secrets_missing] Verification secrets not found

This means that the request may have timed out or couldn’t complete the initial handshake. Please try re-connecting Jetpack by following these steps.

Jetpack experienced an issue trying to save options (cannot_save_secrets)

This usually means that the options table in your WordPress database is not writable. If you’re not sure how to check that, you can contact your hosting provider for assistance in ensuring that the options table is writable.

xml_rpc-32601

This error is possibly a misconfiguration in lighttpd. We do not support lighttpd, but you can check out the suggestions in this forum thread.

Note that in a properly set up site, the /xmlrpc.php URL should display “XML-RPC server accepts POST requests only” when accessed in the browser. The /xmlrpc.php?rsd URL should display some XML data. In a misconfigured site, both URLs will display “XML-RPC server accepts POST requests only.” Learn more on this guide.

xml_rpc-32700

If you run WordPress behind Varnish, you may see this message when trying to connect Jetpack to WordPress.com:

Your Jetpack has a glitch. Something went wrong that’s never supposed to happen. Guess you’re just lucky: xml_rpc-32700. Try connecting again.

Some versions of Varnish have a known bug that prevents Varnish from correctly communicating with the webserver via HTTP/1.0. Until the bug is fixed by Varnish, you can try this workaround, which tells Varnish to use HTTP/1.1 instead. If that doesn’t work, you can try temporarily disabling Varnish, connecting Jetpack, then reenabling Varnish.

I received an error message that is not listed on this page.

You can follow our troubleshooting steps to find out more about the issue on your site.