• Resolved MoghillPat

    (@moghillpat)


    I’m setting up Jetpack for the first time on a staging site on SiteGround and it won’t connect – never had this problem before as long as the staging site is on the correct domain name.

    I’m not using W3TC and siteground’s caching is switched off.

    Here’s the entire error message:
    Your Jetpack has a glitch. We’re sorry for the inconvenience. Please try again later, if the issue continues please contact support with this message: 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.

    https://wordpress.org/plugins/jetpack/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter MoghillPat

    (@moghillpat)

    I have just tried deleting the staging copy, then installing Jetpack on the main site and activating it, then creating a new staging copy.

    However, when I log into that, Jetpack is disconnected and the error message is exactly the same.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    Can you please use Jetpack’s Debugger module to send us some more information about your site?

    1. Go to Plugins > Add New > Upload, and upload this little plugin to your site:
      https://kraft.im/wp-content/lib/helpers/bkjpdebug.zip
    2. Navigate to Tools->Jetpack Debug
    3. Copy the results.
    4. Send them to us via this contact form:
      http://jetpack.com/contact-support/

    Thanks!

    Thread Starter MoghillPat

    (@moghillpat)

    Thanks Jeremy

    I’ve done that now. Thanks for your help!

    Thread Starter MoghillPat

    (@moghillpat)

    This isn’t resolved by the way. I haven’t heard back from Jetpack support

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    If you contacted us via the support form, you’ll hear back from us very soon! Until then, I’ve marked this thread as resolved to avoid having 2 enquiries open at the same time (here and via email). If you’d rather wait until you hear back from us via email, feel free to change this thread status back to unresolved thanks to the dropdown in the right sidebar here->

    Thread Starter MoghillPat

    (@moghillpat)

    Here’s the solution for anyone else who has this issue with JetPack on staging.

    Thanks to Carolyn for providing it

    Jetpack has checks in place to prevent obvious staging sites from being able to connect Jetpack as most people clone from their live, production site and these checks are to avoid problems. Jetpack saves a blog ID and a token (think user name and password) in the database when you first connect that is unique to specific URL. Cloning a site without disconnecting Jetpack also clones that blog ID and token.

    If you’re cloning a live, active, connected site to a new site, then the new site is trying to interact with WordPress.com using the original site’s information. This can cause a whole slew of issues, both now and down the road, which is why we have these checks in place.

    If you need to test features that rely on the connection, I would recommend enabling Staging Mode for this site:
    https://jetpack.com/support/staging-sites/

    While in Staging Mode, you staging site will act like your production site in virtually all ways except no data is passed up to WordPress.com and you cannot disconnect the staging site (to prevent an issue that would lead to problems with your production site).

    I’ve been trying on and off for a year or so to connect my Jetpack, it was added by my former assistant, despite researching it I can’t see what it brings to my site, anywya willing to give it a shot.

    but getting this message:

    Your Jetpack has a glitch. We’re sorry for the inconvenience. Please try again later, if the issue continues please contact support with this message: 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.

    have checked the comments above but they don’t explain what I have to do, ideas welcome please.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    @adrianwelch 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!

    Even I had the same error but managed to resolve.

    I had put my site on staging server initially but was unable to activate Jetpack.
    So after some research I followed the following steps.

    1) I put my site on the live domain,
    2) Removed the filters for staging & debug mode in wp-config.php.
    3) Activated Jetpack from the dashboard.
    4) Once activated I chose the modules which I required in my site.
    5) Logged out as admin & checked. Voila !

    Even I had the same error but managed to resolve.

    I had put my site on staging server initially but was unable to activate Jetpack.
    So after some research I followed the following steps.

    1) I put my site on the live domain,
    2) Removed the filters for staging & debug mode in wp-config.php.
    3) Activated Jetpack from the dashboard.
    4) Once activated I chose the modules which I required in my site.
    5) Logged out as admin & checked. Voila !

    • This reply was modified 7 years, 3 months ago by kishanphadte. Reason: wanted to delete the comment a it was a double entry
Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Error xml_rpc-32601’ is closed to new replies.