Hey Brandon,
I’m from the Social Media support team. Wanted to follow up on the email correspondence you’ve been having with our host team. Can you follow us on Twitter @GoDaddyHelp and send us a DM with the ticket number you had open? I can get you status update as soon as possible.
^Chris
Sent.
We ended up e-mailing directly an individual at GoDaddy who has a couple of engineers on it. So far, they’ve confirmed that the issue is when a connection is being attempted from Jetpack to the GoDaddy-hosted server, but haven’t made progress past that point.
Thanks.
I’m having the same issue. All of a sudden it would not connect to wordpress.com. Getting the same error
“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”
Please keep us updated. I would love to have my jetpack stats back
Hey Brandon,
Definitely sounds like some progress was made, but the techs confirmed there some more work needed to narrow down the source. Continuing to work on it as diligently as they can. I’ll try to keep you posted as well.
^Chris
This is annoying, a joke at this point see goddady’s latest reply to me on this issue:
Dear Robert,
Thank you for your response. We’ve worked to review this further with our administrative staff and we won’t currently be making changes to our environment. However, we have tested the JetPack plugin through our Managed WordPress plans and we were able to connect without any issues. If you only host WordPress based sites, you may wish to consider migrating your sites to one of those types of plans instead. More information on our Managed WordPress plans can be found through the following link:
What is Managed WordPress?
Please let us know if we can assist you in any other way.
Regards,
Aaron K.
Professional Hosting Services
PS today I tried to connect and got a new error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator and inform them of the time the error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Apache Server at rubberboundcop.com Port 80
I’m sorry to hear about the upsell attempt. Jetpack is one of the top five plugins used on WordPress sites, so I’m confident that they’ll resolve this for all of their users.
On our test account, I’m now able to connect, which the change in your error supports that something changed on their end.
In your site’s error logs, there should be an error logged for an Internal Server Error. The Error Logs are accessible via the GoDaddy control panel. On our test account, it would appear you need to access the Error Logs page and enable logging. Once enabled, you can attempt to connect to Jetpack again, and after it throws the server error, return to the logs to view it.
I’ll be away the rest of the week, but I’m going to ensure my colleague working with GoDaddy will keep you in the loop.
Hey Brandon,
I got word from our techs that their test sites started connecting without any issue with Jetpack. At least one other user I was speaking with over Twitter confirmed working from their end as well.
I’m suggesting anyone else whose recently been seeing this error try clearing the browser cache and retesting. Let me know if there’s any change.
^Chris
Our test account is working now as well. Honestly, I’m not sure what happened. There weren’t any changes on our end and the GoDaddy engineers indicated that nothing changed on their end.
We’re going to reply to a small group of users initially to confirm they can connect before mass-replying to everyone who has contacted us regarding this.
Cheers.
Hey Brandon,
Good idea! I’m also touching base with a few others over Twitter about this. I’ll also be checking for updates on this discussion for a while to be sure all is well.
^Chris
I am now able to connect, YEAHHHHHHHH.
I can only assume that the two parties found what ever was blocking it?
only a week of no stats but now that it is back to working I can live with the missing stats from the time it did not work.
It looks like the connection issue has been resolved. We’ve received numerous replies from users who were previously affected that have now been able to connect. As noted above, if you’re still having trouble I would recommend clearing your browser’s cache, and then trying to reconnect Jetpack. And of course, if you run into any trouble, just give us a shout!
Thanks everyone for your help and patience!
