wp_remote_get failure – cURL error 28

Hello @lightlycooked
I’m having the same issue, host also seemingly uninterested to resolve
Issue started a couple of days ago suddenly as it worked relatively fine.
I have 4 installations, 2 on the same server and 2 other ones on different servers. The single setups are fine, no wp_remote_get() failures. the 2 on the same server are failing, and it shows in the functionality of some things, where the function is trying to get content from remote servers (i.e woocommerce’s in the addons tab.
I’ve been reading up on this for the last couple of days and I assure you the information is VERY hard to find… aside from the couple of odd posts that mention wp_remote_get() nothing pertains to the situation but it is fair to say it’s server side and I believe it has something to do with HTTP Auth.

Keep us posted if you find a solution, I’ll do the same… I’m going to reattempt contacting my host.
Cheers

Contacted my host, no dice. They claim it’s cURL’s finicky behavior but I think that’s incompetence talking. If it were, my 2 separate installs would be having the same issue…
I did find out that it could be the remote server blocking the requests or having banned the host server’s ip… the latter would make sense if it were one server that’s blocking/banning but it’s definitely something else and IMO it’s from the source rather than destination.

I have a client that is also hosted with the same company. Only differences are, my account is a reseller account and hers is not and her php version is 5.3.x and mine is 5.6.x. It works on her install but not on mine.

I wish there was some kind of error log (other than the error shown in System Status) that I can show my host or some way to use CLI to test a remote connection from Woocommerce.

I found a little script somewhere online that uses wp_remote_get() (outside of WooCommerce). I used this to show my hosting company that this function was not working. Finally they admitted that the “server firewall is blocking the access“. They said they disasbled it and I should double-check on my end. Well, I did double-check and I still see the error.

I do believe that the firewall is the problem, but I also believe that they didn’t actually disable like they say they did. Maybe ask your host to check the server’s firewall.

If anything else comes up, I will updated this post.

So, here’s an update on my issues.

1) server firewall was blocking communication with woocommerce/woothemes domains
2) The version of cURL that was installed on my server did not have support for SNI (server name indication)

My host moved my reseller account and all the sites linked to that account to a server that had everything that I needed. If you do have your host move your site, be sure to look at the woocommerce server requirements and let your host know so that they can accommodate.

I hope this helps. Good luck!