Support » Plugin: Jetpack - WP Security, Backup, Speed, & Growth » Error code for Jetpack

  • Resolved mat007

    (@mat007)


    Hi !

    I have a proble with Jetpack, it does’nt work anymore. This is the message i get:

    Something which should never happen, happened. Sorry about that. If you try again, maybe it will work. Error code: unknown_user

    Anyone could help with this issue ?

    Thanks a lot !

    Mat

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

Viewing 15 replies - 1 through 15 (of 28 total)
  • Plugin Contributor Richard Archambault

    (@richardmtl)

    Could you post your site URL here, so I can have a look?

    If you want it to remain private, you can also contact us via this contact form:
    http://jetpack.me/contact-support/

    If you contact us through our form, please make sure to include a link to this thread in your message.

    Under the “Sharing Settings” I tried to connect the Tumblr in the jetpack 3.0.2 on WP 3.9.1 and I get this every time:
    “Something which should never happen, happened. Sorry about that. If you try again, maybe it will work.

    Error code: -10520″

    Will this be fixed soon?

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    @rubberboundcop: These errors (-10520) are typically due to an issue related to something on your server side and there’s a number of different reasons for it.

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

    To do so, follow these steps:

    1) Go to the Jetpack page in your dashboard.
    2) Click on “Help” tab in the upper right side of the page and click the link for “Jetpack Debugging Center.”
    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!

    Thank you!

    @brandon,

    I have Godaddy looking into it because all my sites hosted by them have that exact error. I did submit to you as well per your instructions. I also deactivated on the above mentioned site and reactivate it but it will not let me reconnect to Jetpack this error comes up:

    Jetpack could not contact WordPress.com: register_http_request_failed. This usually means something is incorrectly configured on your web host.
    Operation timed out after 15000 milliseconds with 0 bytes received

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    @rubberboundcop

    Thanks. I’m passing this to another engineer here who has been working to track down the source of this issue on GoDaddy. We’ve seen a number of reports about this from other GoDaddy customers over the past few days.

    Cheers!

    Update: the new error when trying to connect to jetpack:

    Your website needs to be publicly accessible to use Jetpack:
    site_inaccessible
    Error Details: The Jetpack server was unable to communicate with your site http://rubberboundcop.com [IXR -32300: transport error: http_request_failed Empty reply from server]

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    Thanks; I’ll send that to him as part of the investigation. It does seem like there’s a server setting that is preventing your server from responding to our servers.

    It has been a few days with no delvopemnt. Where you guys ever able to find out a cause and fix to why all my site hosted with godaddy using jetpack get these error and fail to connect with WordPress?

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    Hi,

    GoDaddy is aware of the issue. Since this is an issue with the GoDaddy’s server configuration, we’re awaiting an update from GoDaddy on detailed information on the recent changes they made.

    I’m afraid there is nothing we can do strictly on Jetpack’s end. The fix will need to be implemented by GoDaddy.

    Was on the phone now everyday for over 5 days with GoDaddy and they can not find what on their end to what would be cause them from blocking the communication from jetpack back to my site. Can you clue them in to what that would be? they can not find anything but you also are not saying what to look for either.

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    We’ve had some of their support folks unable to confirm/see the issue while others acknowledge the issue.

    The most common signs have been entries in the error logs of impacted sites similar to this:

    [fcgid:warn] (32)Broken pipe: [client 76.124.233.2:55432] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function
    [fcgid:warn] [client 76.173.58.122:57932] mod_fcgid: read data timeout in 120 seconds
    [core:error] [client 76.173.58.122:57932] End of script output before headers: admin.php
    [fcgid:warn] (104)Connection reset by peer: [client 199.30.20.227:1570] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function

    Most likely something like this will be in your error log, suggesting there is a misconfig in mod_fcgid.

    One bit of information we’ve had from one individual at GoDaddy said “This upgrade was from our Classic Hosting to Web Hosting” but lacked further technical details.

    For you, perhaps checking your error logs and clueing them into any errors listed there may help speed things along for you personally while we continue our attempts to interface with them.

    I didn’t mean not to give you detailed information, rather say that we’re trying to get this resolved for everyone at once so each person impacted don’t have to spend time directly trying to resolve it.

    Cheers.

    What version of PHP does jetpack activate under? I have 5.4 currently.

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    Whichever is supported by your server. The PHP version on the server hasn’t appeared to have an impact on this issue.

    Our minimal requirement is 5.2.4 (same as WordPress) and have it running of every version between that and the current 5.5 release).

    Seems like both parties do not really care just a lot of figure pointing and NO results going into week number two.

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    Howdy,

    We really care quite a bit, but have to rely on GoDaddy to give us something to work with. The initial request for assistance from them to determine what changes they had made since these reports recently started without a change on our end results in them initially acknowledging something changed, then responding they couldn’t duplicate it so everything is working now.

    We haven’t heard back yet from our latest attempt to reach out to them.

    I appreciate your patience and share in your frustration.

Viewing 15 replies - 1 through 15 (of 28 total)
  • The topic ‘Error code for Jetpack’ is closed to new replies.