WordPress.org

Support

Support » Plugins and Hacks » Jetpack by WordPress.com » [Resolved] Problems with Jetpack 2.1.1

[Resolved] Problems with Jetpack 2.1.1

  • I am recently experiencing some problems with Jetpack.

    • WordPress v.3.5
    • Jetpack v.2.1.1
    • Plugins: Akismet v.2.5.7
    • Theme: Twenty Ten
    • Host: Fatcow

    When I try to view Site Stats, I receive the message:

    We were unable to get your stats just now. Please reload this page to try again.

    When a user tries to subscribe with the Blog Subscriptions widget, they receive the message:

    There was an error when subscribing, please try again.

    The admin account is connected to WordPress.com as indicated by the “Connected to WordPress.com” at the top right of the Jetpack page; however, when trying to connect an editor account to the same WordPress.com account, I receive the message:

    Jetpack could not contact WordPress.com: token_http_request_failed. This usually means something is incorrectly configured on your web host.
    SSL connection timeout

    Is this because only one account can be connected to one WordPress.com account?

    I have visited the xmlrpc.php page on my site and receive the message:

    XML-RPC server accepts POST requests only.

    One final question: after I activate something from Jetpack, why can I not deactivate it?

    http://wordpress.org/extend/plugins/jetpack/

Viewing 15 replies - 1 through 15 (of 43 total)
  • Plugin Author Jeremy Herve

    @jeherve

    Jetpack Mechanic

    Could you please try installing the Jetpack Compatibility Plugin so we can see some additional information from your site?

    1) Download the plugin from http://plugins.svn.wordpress.org/jetpack/branches/jetpack-compatibility-test.zip
    2) Upload the plugin to your site via Dashboard -> Plugins -> Add New.
    3) Activate the plugin and go to Plugins -> Jetpack Compatibility Test.
    4) Click the “Select All” button.
    5) Send us the test results via this contact form:
    http://en.support.wordpress.com/contact/?jetpack=needs-service

    One final question: after I activate something from Jetpack, why can I not deactivate it?

    You can deactivate Jetpack modues by following these instructions:
    http://jetpack.me/support/#turn-off-jetpack-modules

    Hi Jeremy,

    Thank you for your response. I have submitted the test results via the contact form.

    I am having the same issue and I am with the same host as the above user. Is this an host issue?

    I’m seeing the same behavior (same host, same theme).

    http://www.gravelbike.com/

    I installed the Jetpack Compatibility plugin and submitted the results to the contact form Jeremy provided. After an hour the Jetpack plugin was fully functional.

    I am now able to access Site Stats and use widgets such as Blog Subscription. I was also able to link the editor account to the same WordPress.com account as the admin.

    I didn’t receive any email response to the compatibility submission so I can’t be sure but I suspect the support team fixed this issue.

    In any case, thanks, Jeremy and the support team!

    I take it back. I’m experiencing the same problem again. Between the time it was working until now, I have made absolutely zero changes anywhere in WordPress or the hosting account yet the problem has returned.

    has anyone tried removing the plugin from their WP and then reinstalling it? You think that may work?

    I contacted fat cow and they really didnt have a solution except changing my theme to a default theme

    Havent tried it yet… how about one of you?

    I tried deactivating and uninstalling and neither approach worked. I even tried applying the Twenty Eleven and Twenty Twelve themes, which also didn’t work.

    I also see this error on occasion:

    User Agent: “Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17”
    Page URL: “http://www.gravelbike.com/wp-admin/admin.php?page=stats&noheader”
    API URL: “http://dashboard.wordpress.com/wp-admin/index.php?noheader=true&proxy&page=stats&blog=24966746&charset=UTF-8&color=fresh&j=1:2.1.1”
    http_request_failed: “Operation timed out after 90001 milliseconds with 0 bytes received”

    Yup, where earlier I received this message:

    We were unable to get your stats just now. Please reload this page to try again.

    I am now seeing:

    We were unable to get your stats just now. Please reload this page to try again. If this error persists, please contact support. In your report please include the information below.
    User Agent: “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17”
    Page URL: “http://seekingshade.com/wp-admin/admin.php?page=stats&noheader”
    API URL: “http://dashboard.wordpress.com/wp-admin/index.php?noheader=true&proxy&page=stats&blog=39980746&charset=UTF-8&color=fresh&j=1:2.1.1”
    http_request_failed: “Operation timed out after 90001 milliseconds with 0 bytes received”

    Plugin Author Jeremy Herve

    @jeherve

    Jetpack Mechanic

    @gravelbikecom @byrdflew Could you also send me the results of the Compatibility test?

    @seekingshadedotcom We’re having a look at the issue, but haven’t found any solution yet. I’ll let you know as soon as I have an update on this.

    Same issue as I originally reported here…

    http://wordpress.org/support/topic/jetpack-stats-timing-out-last-2-days?replies=10

    Just performed the compatibility test and submitted the results.

    I’m also going to provide this link to my Host (fatcow.com) with whom I’ve filed a support ticket re: this issue.

    @jeremy — Just submitted the compatibility results.

    Plugin Author Jeremy Herve

    @jeherve

    Jetpack Mechanic

    @eswrite-wp Thanks for linking the 2 topics.
    I had missed the original topic, as it wasn’t posted in the Jetpack forums.

    I’ll have a look at the compatibility test results you’ve all sent, and keep you posted.

    Same issue for me as well. Submitted compatibility report yesterday.

    Im also on fatcow. Just spoke with a rep with them who confirmed XML-RPC enabled, but couldn’t give a reseon why this happened. I asked if they had recently made policy changes as far as blocking is concerned and her said no. My ticket was then escalated so a “technical specialist” can deal with it.

    My guess is Fatcow screwed something up.

Viewing 15 replies - 1 through 15 (of 43 total)
  • The topic ‘[Resolved] Problems with Jetpack 2.1.1’ is closed to new replies.
Skip to toolbar