WordPress.org

Support

Support » Plugins and Hacks » Jetpack by WordPress.com » [Plugin: Jetpack by WordPress.com] Glitch in Jetpack

[Plugin: Jetpack by WordPress.com] Glitch in Jetpack

  • I cannot seem to connect to WordPress.com using Jetpack. Before even hitting the Connect button, I got the following error message:

    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.

    I try clicking connect again and again, but the same message continues to appear.

Viewing 15 replies - 1 through 15 (of 27 total)
  • Plugin Contributor Andy Peatling

    @apeatling

    Do you have the W3 Total Cache plugin installed? If you do then please deactivate it first then try the connection process again. You can reactivate after you are connected.

    I have tried it on two sites and have gotten that error and this one….

    Your Jetpack has a glitch. Connecting this site with WordPress.com is not possible. This usually means your site is not publicly accessible (localhost).

    Both are on an Ubuntu box and both sites are publicly accessible.

    Any ideas?

    Mine says:

    Your Jetpack has a glitch. Something went wrong that’s never supposed to happen. Guess you’re just unlucky: site_id_invalid

    I’ve tried in both of my websites and I get the same error. No cache plugin installed here.

    Yep, temporarily deactivating W3 Total Cache worked. Thanks!

    Just got an answer from the support team. They changed something and now it’s working — that was FAST.

    Same error as others:

    Your Jetpack has a glitch. Connecting this site with WordPress.com is not possible. This usually means your site is not publicly accessible (localhost).

    The site IS public accessible (http://lekkerhapje.nl) and I currently use other WP.com plugins (Stats and Akismet) without any problems.

    I have the same issue with my site (dogwonder.co.uk) –

    Your Jetpack has a glitch. Connecting this site with WordPress.com is not possible. This usually means your site is not publicly accessible (localhost).

    No instance of cache installed, also Askimet runs fine. However I am running my install on an apache install on a winOS box.

    I have the same problem with my site too (blog.philworld.de).
    Same as error message “dogwonder”:

    Your Jetpack has a glitch. Connecting this site with WordPress.com is not possible. This usually means your site is not publicly accessible (localhost).

    I have deactivated W3 Total Cache and Akismet works.

    Same as error message as the others;

    Your Jetpack has a glitch. Connecting this site with WordPress.com is not possible. This usually means your site is not publicly accessible (localhost).

    I logged a ticket @ jetpack.me/support and they were able to help me solve this. Below their response:

    It looks like your web server is incapable of sending outgoing requests over HTTPS (as opposed to HTTP). Jetpack should be able to detect this inability and work around it. We’ll work on making that check better in the next version of the Jetpack plugin.

    In the meantime, if you are comfortable editing PHP files, you can modify wp-content/plugins/jetpack/jetpack.php.

    On line 1290, change the current:

    if ( $jetpack->use_ssl[$method] ) {

    to the new:

    if ( false && $jetpack->use_ssl[$method] ) {

    I don’t have a cache plugin installed and tried atobias’ workaround – still getting an “unknown” glitch.

    Mine says:

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

    Any suggestions?

    I got that too:

    Your Jetpack has a glitch. Connecting this site with WordPress.com is not possible. This usually means your site is not publicly accessible (localhost).

    My site is publicly accessible and I have deactivated anything that can cause any problems and I tried atobias’ solution but nothing seems to work.

    Any Ideas ?

    For anyone having similar issues:

    1) Check to ensure that any Proxy services you may be using, such as CloudFlare, are temporarily disabled.

    2) Check for any .htaccess UserAgent or IP address blacklist entries (such as those provided by PerishablePress).

    I had this running a Bitnami instance in Amazon EC2. I tried the suggestion listed above by atobias (change line 1290 of the PHP file) and that worked.

    Thanks!

Viewing 15 replies - 1 through 15 (of 27 total)
  • The topic ‘[Plugin: Jetpack by WordPress.com] Glitch in Jetpack’ is closed to new replies.
Skip to toolbar