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.
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 having this error after 72 hours, check your URL at http://whois.domaintools.com/ and make sure that only the proper Name Servers are listed. If your old Name Servers are listed, log in to your DNS manager and remove them.
“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]”
Your host is limiting concurrent PHP connections. Jetpack needs to be able to talk and receive 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.
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.
This error message often suggests some kind of option 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.
This error is possibly a misconfiguration in lighttpd. There are some suggestions at this forum thread: “JetPack Instl issue with SSL and lighttpd“.
In a misconfigured site, both URLs will show “XML-RPC server accepts POST requests only.”
If you run WordPress behind Varnish, you may stumble across 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 which 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+Varnish.
I have a firewall or proxy on my web server. Can you provide me with IP addresses to whitelist?
We aren’t able to provide any IP addresses for Jetpack as they fluctuate. You could try whitelisting *.wordpress.com for both inbound and outbound traffic, as a workaround.
My stats are mixed up or got combined with another site. Can you separate them for me?
We do not offer a way to separate site stats if they get combined. Please do get in touch with us, though, and we will help ensure that your stats remain separated in the future. You can click on the Debug link in the footer of the Jetpack menu in your WordPress dashboard, and you will be able to contact us through that page.
I received an error message that is not listed on this page.
You can follow the troubleshooting steps listed on this page to find out more about the issue on your site.