marktab7

Hi Jeremy

So thanks for trying to help. Though I will provide more information for those hosting on GoDaddy.

1) GoDaddy will work with customers directly. Their general help website remains the only authoritative place to get information on what to do. I notice that Jeremy did not reference an official GoDaddy response, and therefore that type of advice needs to be verified with GoDaddy before taking any action. GoDaddy has been hosting for many years, and the various advice circulated outside their website, including on www.ads-software.com, may or may not represent current practice.
2) I am independently working with GoDaddy on an open ticket to resolve this issue. They have looked at my specific account from the inside, and recommended tips to try other than Linux hosting. I will not detail what those steps are since they may or may not represent what other people should do.
3) In my case I will NOT be moving marktab.net to Linux hosting. This acount also hosts dotnetnuke, which is Windows only. Note how you could get into trouble by coming to forums like this where people giving you advice start listing steps to transfer your account to another operating system without considering (or even asking for) the full scope of information. An alternative I therefore have is to find (possibly) another Windows host.

However, I am not done with my debugging tests. I wanted to see what Jeremy, representing Jetpack, would be able to offer. I have more tests to run based on the information I have from the “Core Control” plug-in, which provides advanced information on how plug-ins work with the server. Two obvious tests include whether other plug-ins which have similar connectivity profiles also experience issues. Also, I intend to stand up a new instance of WordPress and see whether that one will similarly have issues with Jetpack.

Jetpack used to work. Also, I noticed that in a recent upgrade of the same software on Linux (this past week) that I was receiving the same message. But that Linux installation was not GoDaddy, but Bluehost. I resolved that error, which was related to the max upload size parameter being set too low. At present the Jetpack zipped installation comes in at over 4 MB.

Finally, I want to give this general question to those having similar problems: ask yourself whether switching operating systems is really worth the value of a single plug-in. Or, would you be better off by finding an alternative plug-in?

I have upgraded to 2.3.5 and WordPress 3.6.

On the requested steps: the debugger does NOT show on my screen as on https://jetpack.me/2013/06/19/jetpack-2-3/. Therefore I am taking a different path.

I discovered that other people have used the “Core Control” plugin to help debug Jetpack. I installed that plugin. I turned on logging. What follows is the log from the request (I obsursed the secret keys):

URL
https://jetpack.wordpress.com/jetpack.register/1/

Method
POST

Result
error

Error Details

http_request_failed Operation timed out after 15008 milliseconds with 0 bytes received

Time Taken
15.188367843628 seconds

HTTP Args

timeout (integer) 15
redirection (integer) 5
httpversion (string) 1.0
user-agent (string) WordPress/3.6; https://marktab.net/datamining
reject_unsafe_urls (boolean) false
blocking (boolean) true
headers Array
(
[Accept] => application/json
)

cookies Array
(
)

compress (boolean) false
decompress (boolean) true
sslverify (boolean) true
stream (boolean) false
filename NULL
limit_response_size NULL

HTTP POST body
Array
(
[siteurl] => https://marktab.net/datamining
[home] => https://marktab.net/datamining
[gmt_offset] => -4
[timezone_string] => America/New_York
[site_name] => MarkTab Data Mining
[secret_1] => XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[secret_2] => XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[site_lang] => en_US
[timeout] => 15
[stats_id] => 11790574
)

HTTP Transports
WP_HTTP_curl

Request Time
2013-08-16 23:44:21 –400

Contemplate:

Your line 268 edit works for me on the plugin version 5.0.8 and WordPress 3.5.2
I commented out my old line with a # and added the new line after

Upgrading from 3.1.8.1 to 3.1.8.2 did NOT work for me with 3.5.1. Thus, I removed 3.1.8.2 and went back to 3.1.8.1, which worked. In my case, the aborted installation was still showing a message on the upgrade screen that a partial install had not completed: I did an entire refresh of WordPress 3.5.1 to respond to that message. Then, I experimented by removing 3.1.8.1 altogether, and manually downloading and installing the unzipped 3.1.8.2 files using FTP. After activation, the plugin worked.

As a best practice: I recommend only upgrading 3.1.8.2 alone, even if other plugins are asking to be upgraded. You could choose to upgrade other plugins first (and maybe you have a reason to do those other upgrades after). However, isolating installation to this one plugin should help debug installation problems.

Though I was able to solve my issue, I believe that others will similarly have problems on this particular 3.1.8.2 version. Do not give up: Please post exactly what is happening in your case, so that you can get your installation working like it does for me. During these installation attempts, keep a copy of 3.1.8.1 to use so that your website still works.

Hello — I had earlier tried to update (unsuccessfully) on several different WordPress installations. I had been trying to make it work on WordPress 3.50 and earlier. However, I recently was successful with Transposh 0.92 and WordPress 3.51.