How to Fix Your Jetpack has a glitch for xml_rpc-32601

Posted on November 19, 2015 @ 3:39 am

Tags: , , ,

2 Comments

Last updated on December 26th, 2015 at 10:35 pm

Just recently I was contacted by a client of mine who's using our Managed WordPress Hosting Services, she told me that a Jetpack glitch disconnected her WordPress.com account.
She also reported that she received the following warning:

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

Repairing xml_rpc-32601 Jetpack glitch

1This the default solution provided by Jetpack itself and its combined with the usage of W3 Total Cache. If you use this cache plugin then its suggested to disable it, try to connect to Jetpack with your WordpRess.com account and once you do re-enable W3TC. You can also try to clear your cache instead of disabling W3TC.

2JetPack has a list of plugins that conflicts with, check it out and see if you have any of those plugins installed on your site. Then disable them and try to connect, finally re-enable them and check if you are still connected with JetPack service.

3Follow Deborah's advice at WordPress.org Jetpack forum for the xmlrpc-32601 ERROR - can't connect to wp.com topic by temporarily renaming your .htaccess to .htaccess-old.
As Deborah mentions:

This will temporarily stop your custom permalinks from working, as well as disable any other code that may have been inserted by plugins into your .htaccess file.

Then try to connect to Jetpack. If you succeed rename your .htaccess-old back to .htaccess.

By the way Deborah Beckett is an Automattic Happiness Engineer.

4This is another .htaccess approach. If you have a heavily edited .htaccess its suggested to create a backup and then create a new using WP default .htaccess rules. Then try to connect to your Jetpack account and if you succeed you can restore back your original .htaccess.

5You can also try to debug your original .htaccess and see which rules conflict with xmlrpc.php which is used by Jetpack. First of all you need to make sure that the following urls are working on your site:

a. http://yoursite.com/xmlrpc.php
This is what you should be getting: XML-RPC server accepts POST requests only.

b. http://yoursite.com/xmlrpc.php?rsd
When you visit this url you should be getting an xml tree as follows:
This XML file does not appear to have any style information associated with it. The document tree is shown below.

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<rsd xmlns="http://archipelago.phrasewise.com/rsd" version="1.0">
<service>
<engineName>WordPress</engineName>
<engineLink>http://wordpress.org/</engineLink>
<homePageLink>http://yoursite.com</homePageLink>
<apis>
<api name="WordPress" blogID="1" preferred="true" apiLink="http://yoursite.com/xmlrpc.php"/>
<api name="Movable Type" blogID="1" preferred="false" apiLink="http://yoursite.com/xmlrpc.php"/>
<api name="MetaWeblog" blogID="1" preferred="false" apiLink="http://yoursite.com/xmlrpc.php"/>
<api name="Blogger" blogID="1" preferred="false" apiLink="http://yoursite.com/xmlrpc.php"/>
</apis>
</service>
</rsd>

If you get different results then open your .htaccess and remove some of the rules found in there, save it and reload xmlrpc.php urls.
Repeat until you find the conflicting .htaccess rules.

Do you need some more help in repairing this Jetpack glitch?

Contact Us and Get a Free Quote

Makis Mourelatos

WordPress Security Engineer at FixMyWP
WC Athens 2016 co-organizer, WP Support and Security Aficionado, Wannabe Kitesurfer.

Comments (2)

Leave a Reply

Your email address will not be published. Required fields are marked *