Latest Swift framework update

[tasoskouk]

yeap…

i got this: “✕ wp_remote_get() failed. The WooCommerce plugin updater won’t work with your server. Contact your hosting provider. Status code: 500”

so waiting fastcomet.com reply… but why other servers plugins get installed?…

thx

[tasoskouk]

Ed & team hi,

it seems that i encountered a special bug probably in wordpress update script that is related to my domain name hydration.gr
please check the latest reply from senior support staff @ fastcomet.com hosting (long but clear if hope)

hope u can help
thx, tasos

===============================================================================================================

https://my.fastcomet.com/viewticket.php?tid=418704&c=928HOKjz

Hello again,

Thank you for your patience in this matter.

As for the issue — we spent several hours investigating this as we have never experienced this issue before and no other user have ever reported this error despite the fact that there are many posts in different forums from other Woo Commerce users that experienced the same issue. Please find detailed information on the issue below:

First and foremost, the wp_remote_get() function is not blocked on our servers and we do not restrict outgoing http requests in any way. We noticed that the actual error is:

✕ wp_remote_get() failed. The WooCommerce plugin updater won’t work with your server. Contact your hosting provider. Status code: 500

The strange thing about the error is the status code at the end – Error 500. Error 500 means “Internal Server Error”. At first we thought that this is generated by our server but at the end the started to debug the application it self. The Woo Commerce functions and status checks are actually performed in the file:

wp-content/plugins/woocommerce/includes/admin/views/html-admin-page-status-report.php

The exact code is:

—————
// WP Remote Get Check
$posting[‘wp_remote_get’][‘name’] = __( ‘Remote Get’, ‘woocommerce’);
$posting[‘wp_remote_get’][‘help’] = ‘<a href=”#” class=”help_tip” data-tip=”‘ . esc_attr__( ‘WooCommerce plugins may use this method of communication when checking for plugin

updates.’, ‘woocommerce’ ) . ‘”>[?]‘;

$response = wp_safe_remote_get( ‘http://www.woothemes.com/wc-api/product-key-api?request=ping&network=&#8217; . ( is_multisite() ? ‘1’ : ‘0’ ) );

if ( ! is_wp_error( $response ) && $response[‘response’][‘code’] >= 200 && $response[‘response’][‘code’] < 300 ) {
$posting[‘wp_remote_get’][‘success’] = true;
} else {
$posting[‘wp_remote_get’][‘note’] = __( ‘wp_remote_get() failed. The WooCommerce plugin updater won\’t work with your server. Contact your hosting provider.’, ‘woocommerce’ );
—————

Basically, this code performs a call to:

( ‘http://www.woothemes.com/wc-api/product-key-api?request=ping&network=&#8217; . ( is_multisite() ? ‘1’ : ‘0’ ) );

If the response is => 200 & 300 < WooCommerce will report the function wp_remote_get as OK. If the response code is out of this range it will report that the function is not OK as in your case. Based on the error, your site generate response error 500 for this call.

As you can see this is the WooThemes official website and API. If the site is a multisite it uses 1 and if it is not it uses 0. So the WooCommerce is actually performing an API call to the WooThemes site using the following URL:

http://www.woothemes.com/wc-api/product-key-api?request=ping&network=1

We tested the URL if it is reachable from our server on which your account is located and it turned out that when accessed it return code 200 which means that it works perfectly fine and the issue is not related to the server IP or block:

curl -v http://www.woothemes.com/wc-api/product-key-api?request=ping&network=0

[2] 295817
* About to connect() to http://www.woothemes.com port 80 (#0)
* Trying 104.24.12.85… connected
* Connected to http://www.woothemes.com (104.24.12.85) port 80 (#0)
> GET /wc-api/product-key-api?request=ping HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: http://www.woothemes.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Sat, 24 Oct 2015 02:53:41 GMT
< Content-Type: application/json
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=dc843a2b45b10ed93e4f1f77e878378861445655219; expires=Sun, 23-Oct-16 02:53:39 GMT; path=/; domain=.woothemes.com; HttpOnly
< Vary: Accept-Encoding,Cookie
< X-Cacheable: SHORT
< Cache-Control: max-age=600, must-revalidate
< X-Cache: MISS
< X-Cache-Group: normal
< Expires: Wed, 11 Jan 1984 05:00:00 GMT
< Pragma: no-cache
< X-Type: default
< X-Pass-Why:
< Set-Cookie: X-Mapping-fjhppofk=040DC513398F8BAF41A88474493B595F; path=/
< Set-Cookie: gaUserTypeShort=Prospect; expires=Sat, 24-Oct-2015 03:23:40 GMT; path=/
< X-Frame-Options: SAMEORIGIN
< Server: cloudflare-nginx
< CF-RAY: 23a2647ff1412786-FRA
<
* Connection #0 to host http://www.woothemes.com left intact
* Closing connection #0

{“success”:true,”message”:null,”timestamp”:1445655221,”sig”:”secret=null&success=true&message=&timestamp=1445655221″}

When, however, this is executed via the domain name hydration.gr the same api call return error 500. WooThemes uses CloudFlare CDN to process all traffic for their website and

CloudFlare pass error 500 directly to the source of the request which means that if the reply is error 500, it is generated by the WooThemes API.

This make us to believe that the WooCommerce api is not able to process the request from this specific domain: hydration.gr

To prove this we have installed a new wordpress under the same domain name and the error persisted. Then we installed 2 new WordPress installations with WooCommerce on the same server under different domains.

The first WooCommerce install is under our own URL:

http://int.de1.fcomet.com/wp/wp-admin/admin.php?page=wc-status

admin username: admin
admin password: p@ss1234

As you can see the function is reported OK due to the fact that the WooThemes is returning the proper response 200 for this domain. — http://prntscr.com/8uo1n8

Then to prove that the issue is not related to your hosting account we have installed a test WordPress under your primary domain: koukouvitis.net

http://koukouvitis.net/fctest/wp-admin/admin.php?page=wc-status

admin username: admin
admin password: p@ss1234

As you can see the function is reported OK here as well — http://prntscr.com/8uo1rm

Basically, the only domain for which we have been able to recreate the error is hydration.gr and unfortunately, we are not aware why exactly the WooCommerce API return error 500 for this domain name. They might be using the API for some sort of statistics or other tracking which is not able to add this domain in their database or similar activity might be failing. Yet, I can confirm that the issue is not a sever or account related and the function is properly working. Additionally, be advised that this does NOT affect your wordpress or woocommerce functionality in any way. The error is related to the WooThemes api, your wordpress completely capable of checking for updates or installing updates, plugins, themes and etc. Still, if you really would like to dig to the bottom of this, you may contact WooCommerce directly and inform them about the issue, they should be able to check this on their end and provide additional information.

As for the Swift Framework and your Theme, I have updated the theme, downloaded the framework and successfully installed it.Yet, the install via this list:

http://www.hydration.gr/wp-admin/themes.php?page=install-required-plugins&plugin_status=install does not work properly. Please note that we do NOT block this website and the plugins can be successfully downloaded on the server:

———–
root@de1 [/home/koukouvi/public_html/hydration.gr/wp-content/themes/atelier/includes]# wget http://swiftideas.com/extras/plugins/revslider.zip
–2015-10-24 03:27:47– http://swiftideas.com/extras/plugins/revslider.zip
Resolving swiftideas.com… 104.24.3.29, 104.24.2.29
Connecting to swiftideas.com|104.24.3.29|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 5095355 (4.9M) [application/zip]
Saving to: “revslider.zip”

5,095,355 3.79M/s in 1.3s

This might be caused by plugin-includes.php syntax error or similar issue – if you would like us to install these for you, please confirm and we will proceed.

Thank you.

xxx
Senior Support Team
FastComet.com

======================================================================================================================================

hello and thanks for your efforts & reply,

i understand your points and might really be one of those special cases, but this issue is not only related to woocommerce but to any update that is not coming from wordpress.org (or “trusted” domains or …)

if this is true, something is wrong not only related to woocommerce…

a more general script is to blame, used by woo, swift, sliders etc (maybe in wordpress itself) – bcoz none of those can get updated…

so please check on this

thx

[Swift Ideas – Ed]

Hi Tasos,

We use TGM Plugin Activation ( https://github.com/TGMPA/TGM-Plugin-Activation ) , nothing custom – and it seems you are the only one with this issue.

We will keep an eye out for anything, but let us know if WooCommerce gets back to you on the issue – there is nothing we can investigate from our side.

– Ed

[tasoskouk]

This reply has been marked as private.

[3969120a]

so, if our version is

The Swift Framework plugin.

Version 1.63

what do we do?

[Swift Ideas – Ed]

@3969120a – you can update now, the issue is resolved.

– Ed

[Swift Ideas – Ed]

@tasoskouk – nothing on your site would lead to an explanation, so login is irrelevant. We also definitely have no blocks on our end..

– Ed

[3969120a]

thanks Ed

[David Martin – Support]

Thanks Ed.

The update issues are now resolved for anyone coming across this thread. If you do encounter any new issues, please open a new thread.

-David.