Problems with Jetpack 2.1.1

  • Resolved seekingshadedotcom

    (@seekingshadedotcom)


    11 years, 3 months ago

    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 - 16 through 30 (of 43 total)
1 2 3
  • GRAVELBIKEcom

    (@gravelbikecom)

    11 years, 3 months ago

    Could you post the link for the Jetpack forum(s)?

    I don’t know if it’s related, but my site’s WordPress stats are now showing zero visitors (which I know is not correct).

    http://wordpress.com/#!/my-stats/

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    11 years, 3 months ago

    @gravelbikecom Jetpack Forums are available here:
    http://wordpress.org/support/plugin/jetpack

    (You can get there from the link in the sidebar on the right of this thread, or by clicking on “Support” on the plugin page:
    http://i.wpne.ws/MNIJ

    I don’t know if it’s related, but my site’s WordPress stats are now showing zero visitors (which I know is not correct).

    If you experience issues connecting Jetpack to WordPress.com, you will have issues with Stats as well.

    Bugsformymasonjar

    (@bugsformymasonjar)

    11 years, 3 months ago

    Same issue, same host- sent in compatibility test results.

    drktcncpt

    (@drktcncpt)

    11 years, 3 months ago

    I am having the same issue with the same host as well, along with the same errors. It was working perfectly a couple of days ago. I’ve sent in my compatibility test results.

    mellownspicy

    (@mellownspicy)

    11 years, 3 months ago

    I am having the same issue for the last two days.Same host as well with the same errors.Have sent my compatibility results.

    eswrite-wp

    (@eswrite-wp)

    11 years, 3 months ago

    OK, no response from Fatcow on my ticket yet… really strange because they usually hop to it. Good to hear others have received a response. I’m beginning to think the issue is on their end.

    GRAVELBIKEcom

    (@gravelbikecom)

    11 years, 3 months ago

    No response to my ticket, either. I actually updated my ticket with a pointer to this forum.

    hephaestus42

    (@hephaestus42)

    11 years, 3 months ago

    I am having the same issue at blue host.

    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 (Windows NT 5.1) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17”
    Page URL: “http://www.hephaestusproject.com/Energy/wp-admin/admin.php?page=stats&noheader”
    API URL: “http://dashboard.wordpress.com/wp-admin/index.php?noheader=true&proxy&page=stats&blog=42460876&charset=UTF-8&color=fresh&j=1:2.1.1”
    http_request_failed: “Operation timed out after 90001 milliseconds with 0 bytes received”

    hephaestus42

    (@hephaestus42)

    11 years, 3 months ago

    More issues with jetpack

    After deactivating and then reactivating site stats it disappeared from the left hand menu bar. It now tells me …

    “To enable all of the Jetpack features you’ll need to connect your website to WordPress.com using the button to the right. Once you’ve made the connection you’ll activate all the delightful features below.”

    When the “Clicking connect to wordpress” button I get the message

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

    eswrite-wp

    (@eswrite-wp)

    11 years, 3 months ago

    Oooh, bluehost also… that now starts pointing at something else. Could it be WordPress.com changed something?

    esmi

    (@esmi)

    11 years, 3 months ago

    Have you asked Bluehost about this?

    nicpedersen

    (@nicpedersen)

    11 years, 3 months ago

    No response to my ticket, either. I actually updated my ticket with a pointer to this forum.

    i did the same!

    Gaye

    (@confettidrop)

    11 years, 3 months ago

    Hi. I’ve been having the same issue for the last two days. It was working fine before that and I haven’t added any new plug ins, so I don’t know what the cause of the problem might be. I also have Fat Cow as a host. Should I go there for support? I’m new to blogging and it’s a miracle I have this site up and running at all. I’m afraid to do anything before I have someone tell me they have a definitive fix. Help! 😉
    Thanks.
    Gaye
    confettidrop.com

    hephaestus42

    (@hephaestus42)

    11 years, 3 months ago

    Just to rule something out. Question for everyone with issues.

    Who is your internet service provider? I am using Comcast in NJ.

    GRAVELBIKEcom

    (@gravelbikecom)

    11 years, 3 months ago

    ISP: forethought.net (via CenturyLink) in CO.

Viewing 15 replies - 16 through 30 (of 43 total)
1 2 3
  • The topic ‘Problems with Jetpack 2.1.1’ is closed to new replies.