Do you experience issues when trying to connect your site to your WordPress.com account? Start by checking the following list of error messages, and what you can do to fix them.
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 at least 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 at whois.domaintools.com and make sure that only the updated Name Servers are listed. If your old Name Servers are listed, log in to your DNS manager and remove them.
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]
cURL error 28: Connection timed out after 10000 milliseconds
Your host is limiting concurrent PHP connections. Please confirm with your host that there is no block from their end. Also, please confirm if 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 the steps here.
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. Check your PHP error log (or ask your host to check) to see if there are any notices from around the time this error showed up.
Error code 409 – XML-RPC is not responding correctly
Sites that proxy traffic through Cloudflare or other CDNs might see a 409 in the Debugger Tool.
If you are receiving this error on Jetpack Debugger, and you are using Cloudflare, you should bypass Cloudflare’s features for xmlrpc.php and WP Admin. Details here.
This error message often suggests some kind of caching issue. If you use a caching plugin on your site, try flushing your 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 there were issues making a connection to the site. The request may have timed out or couldn’t complete the initial handshake. Please try re-connecting Jetpack by following the steps here.
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 ensuring that the
options table is writable.
This error is possibly a misconfiguration in Lighttpd. There are some suggestions at this forum thread.
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 should display some XML. In a misconfigured site, both URLs will display “XML-RPC server accepts POST requests only.” Read more on this here.
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. This post discusses how to do that for sites using Nginx and Varnish together.
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.