It’s usually problems with your XML-RPC file, especially since your running on nginx&varnish. Usually fixable by disabling Varnish temporarily. Follow the steps at http://usefulmix.com/wordpress-nginx-varnish-jetpack-xml_rpc-32700-glitch-fix/ and see if that helps.
A thousand thank yous for this fix Patrick, saved me hours of trying to get it working!
We are developing a WordPress multisite to be hosted on our preview server, that is on Amazon EC2 cloud running Ubuntu with varnish cache. For the purpose of development this preview server has been setup as a VirtualHost for my mac environment (with MAMP). I’ve installed the jetpack thru the network admin. But I get the following error while connecting to WP:
Your Jetpack has a glitch. Something went wrong thatβs never supposed to happen. Guess youβre just lucky: xml_rpc-32601
Try connecting again.
Error Details: The Jetpack server could not communicate with your site’s XML-RPC URL. If you have the W3 Total Cache plugin installed, deactivate W3 Total Cache, try to connect to WordPress.com again, reactivate W3 Total Cache, then clear W3 Total Cache’s cache.
I don’t have W3 Total cache, xmplrpc.php works perfectly. I’ve gone thru the glitch-fix document (http://usefulmix.com/wordpress-nginx-varnish-jetpack-xml_rpc-32700-glitch-fix/ ) but not quite sure if it this is the solution for my case.
@raich Can you please use Jetpack’s Debugger module to send us some more information about your site?
1) Go to the Jetpack page in your dashboard.
2) Click on the Debug link appearing at the bottom of the page.
3) Click the link that says “click here to contact Jetpack support.”
4) Fill in the description box and your name and email address.
5) Click the “Contact Support” button.
Thanks!
Hi Jeremy,
I’ve sent an email to Contact Support.
Thanks.
@jeremy,
My Jetpack’s Debugger test results:
TEST RESULTS:
HTTP: PASS
HTTPS: PASS
IDENTITY_CRISIS: PASS
SELF: FAIL
SELF
Array
(
ββββ[headers] => Array
ββββββββ(
ββββββββββββ[server] => nginx
ββββββββββββ[date] => Mon, 17 Nov 2014 18:07:31 GMT
ββββββββββββ[content-type] => text/plain;charset=utf-8
ββββββββββββ[connection] => close
ββββββββββββ[x-pingback] => https://jetpack.wordpress.com/xmlrpc.php
ββββββββββββ[expires] => Wed, 11 Jan 1984 05:00:00 GMT
ββββββββββββ[cache-control] => no-cache, must-revalidate, max-age=60
ββββββββββββ[pragma] => no-cache
ββββββββββββ[x-hacker] => Jetpack Test
ββββββββ)
ββββ[body] => {“error”:”Jetpack not connected”,”error_description”:”We were unable to find a Jetpack instance on your site. Please connect Jetpack to your WordPress.com account from within your WordPress admin.”}
ββββ[response] => Array
ββββββββ(
ββββββββββββ[code] => 400
ββββββββββββ[message] => Bad Request
ββββββββ)
ββββ[cookies] => Array
ββββββββ(
ββββββββ)
ββββ[filename] =>
)
I've the Jetpack in my local (in MAC) plugins directory.
Thanks.
@jeremy Just now I’ve upgraded to jetpack 3.2.1 and it has been installed successfully in the work environment (in mac). But when I go to connect Jetpack with wordpress I still get the same xmlrpc 32601 error.
@jeremy
my .htaccess has very basic entries:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
I’ve sent an email to Contact Support.
Thanks! We’ll check the debug test results and reply very soon!