Plugin API HTTP Error

Same problem here. Deleted that plug-in and now it’s fine again. Thank you for the tips everyone.

Thanks Josh for highlighting this thread on my blog where I had shared a solution for resolving this problem of API HTTP error on WP admin panel.

You may go thru the link mentioned below to get an overview/reason/solution for this problem. Kindly go thru the comment section as well where I have provided some details about the reason for this error.

SOLVED – An Unexpected HTTP Error occurred during the API request on WordPress Backend

Thanks.

No problem, all. I’m glad it helped you, too. But like eight7teen said, the issue obviously lies somewhere else as I’m still unable to search and upload plugins via my dashboard without getting the same error. But for now, as far as I’m concerned, I was looking for a fix and I found one. I had things I needed to write about – and not being able to access my dashboard was irking me. The trick about changing the http.php file from 5 seconds to 30 simply didn’t work for me either.

I tried modifying the http.php file from 5 to 30 , but it didnt help. Someone else found another fix except removing sexybookmarks ? ?? They were so cute, I want them back !

Same thing here

tried the tmp fix in config.php
tried the timout extend fix..

Same thing

WP_Error Object ( [errors] => Array ( [http_request_failed] => Array ( [0] => Empty reply from server ) ) [error_data] => Array ( ) )

An Unexpected HTTP Error occurred during the API request.

When are they gonna solve this ? Don’t they have support / tech guys at wordpress ? Why nobody says anything ? :(:(:(

I had a same problem but i found out solution @ https://netchunks.com/wordpress/an-unexpected-http-error-occurred-during-the-api-request/

Sexybookmarks. That was the culprit on mine. I did do the change in http.php first, then I remembered somewhere while watching the site load on Firefox or something) that Sexybookmarks caused a slight delay while resolving. That was a few days ago and I took a “mental” note.

Then this stupid thing happened and I could not access admin AT ALL! This thread was a lifesaver and convinced me to be a WordPress Forum regular… ??

I left http.php change intact. No harm in leaving it, 5 secs is ridiculously short I think.

Thanks a lot.
The fix worked like a charm for my blog

Neo
Website

Well since the vast majority of you guys can’t seem to comprehend the fact that it’s not technically “SexyBookmarks” that’s causing the issue, I’m going to release another version soon that will remove any and all API usage from the plugin… I’m sure most of you will undoubtedly say “oooh, that fixed it”, but just wait a while… The problem will come back because it’s not caused by sexybookmarks, it’s caused by making use of the API.

The wordpress dashboard uses the API, so it’s hit or miss as to whether or not you’ll see the error. You may see it the next time you browse for a new plugin, or maybe even the next time those nifty boxes full of useless information load up on your dashboard… Just don’t say I didn’t warn you.

if you’ve changed that to 30 or 45 or higher number but still get the error, change it to 0. 0 means that no timeout limit.

'timeout' => apply_filters( 'http_request_timeout', 0),

If by using that way you still get the error, you need to contact your administrator because I think that your server connection is not good.