This seems like a more widespread issue than just the plugin installs as I’m unable to connect to anything on the WordPress sites for blog, RSS, or the Jetpack installer.
Bumping this topic as I’m still struggling with this issue and don’t know where to go from here. The site is externally accessible.
More error messages:
RSS readers have an error as follows:
"RSS Error: WP HTTP Error: Failed connect to wordpress.org:80; No error"
Jetpack gives an error when trying to authorize the connection.
"Jetpack could not contact WordPress.com: token_http_request_failed. This usually means something is incorrectly configured on your web host.
Connection timed out after 5616 milliseconds"
One more bump as this looks like it’s not limited to just plugins or Jetpack. I’ll try and summarize.
WordPress is running on a self-hosted Windows Server 2012 box via IIS, PHP 5.3.28, and MySQL 5.6.15.
I’m getting the following error when I try to check my plugin list (taken from my PHP error log using Debug Bar plugin):
WARNING: C:\*********\wp-includes\update.php:267 - An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.)
The RSS reader on the main page on the wp-admin dashboard throws the following error:
"RSS Error: WP HTTP Error: Failed connect to wordpress.org:80; No error"
When trying to authorize a Jetpack connection, I get the following error:
Jetpack could not contact WordPress.com: token_http_request_failed. This usually means something is incorrectly configured on your web host.
I tried to contact Jetpack support and they told me that it was likely something misconfigured on my server, but I’m lost as to what that could be.
Thanks for any assistance with this one. I’m really lost, so I’d appreciate any fresh eyes you could give.
Hey,
Unfortunately I have already been through those threads, it doesn’t appear to be SSL related at all and I have reset my DNS to point to Google’s DNS (8.8.8.8) as primary with no luck.
I have seen recent issues with jetpack connection to wordpress after migrating to new server from old (not local host).
May be there is something wrong or a bug? Well, I removed jetpack completely and installed it afresh. It worked for me.
There were connection issues before I even installed Jetpack.
You tried a fresh installation? If you use a cache plugin, disable or clear the cache. Things conflict sometimes
No cache plugin, and have started with fresh WP install.
Just for the heck of it, maybe take a look at the Core Control plugin when you get a chance (works fine for me with WP 3.8.1) and see if anything obvious jumps out at you from the Filesystem Access and External HTTP Access pages.
CJ,
Core Control does indeed note that SSH2 transport method is not enabled. I’ve tried to follow directions for installing libssh2 and php_ssh2.dll, but it doesn’t seem to be helping to fix this problem. Do you think this might be the cause of the issue?
Also if you’re running behind a proxy server or firewall or load balancer (or all three) you will likely need to do some network tweaks to allow your server to communicate to the outside world (i.e. for plugin downloads and general WordPress updates).
bem,
I’ve turned off the firewall for testing, and no dice. 🙁 Thanks, though!
Core Control does indeed note that SSH2 transport method is not enabled…
…Do you think this might be the cause of the issue?
I don’t think so.
[edit] The majority of resolutions/suggestions I find in prior discussions seems to be be focused on DNS issues.
Just ball-parking on this:
a) Does cURL indicate it’s an available transport option under Manage Transports on the External HTTP Access page, and everything else on that page is “in the green”?
b) When you test all of the transports available under Manage Transports, do you get a “Successfully retrieved & verified document..” message, or something different?
c) If cURL appears to be working, can you change your symptoms at all by using core control to disable the cURL transport?
