error 3.3.0 Upgrade Check Failed !

[fdr]

I installed version 3.3.0 but when i go to the admin page (/admin/health-check.php?updated=1)
- 3.3.0 Upgrade Check Failed !

I tried to update site a second time but the error stay.

[xxdex]

Upgrade check failed.. because it's newest version of get simple.. (i think so)

[shawn_a]

Could be anything, actual outage, network issue, curl not enabled.
Do your plugins have links and versions ?

[xxdex]

this is my screen..
i have the same problem
https://dl.dropboxusercontent.com/u/4998.../1_new.jpg

in en:
https://dl.dropboxusercontent.com/u/4998...new_en.jpg

plugins:
https://dl.dropboxusercontent.com/u/4998...new_en.jpg

when i disabled/or enabled one of plugin... it's disappears (yellow "!") but when i click some of link it's reappears.

this trouble was from "install" without any external pluggins

[shawn_a]

So you did not have this issue before upgrading ?
It seems like your plugin api query is working, or its cached.

Did you try flushing cache in settings ?

[xxdex]

its not upgraded... it's a new instalation... i'm was install it (clear install) because i was want to check it (version).. plugins compability, and new good's

[shawn_a]

I am just wondering if this is new to 3.3.0 and if you had success with older versions on the same host etc.

[fdr]

I had no problems with the older version on the same host. (I update this installation)

[topclass99]

My installations also failed but all appears to be OK
The errors listed were all '0705 Not Writable - Error!"
but the folders affected can be written to. Another site passed with the same errors
mine was an update only for admin + index.php

[xxdex]

it's a newest instalation, and older version don't have the same problem in the same hosting/domain/serwer

[topclass99]

My installations also failed but all appears to be OK
The errors listed were all '0705 Not Writable - Error!"
but the folders affected can be written to. Another site passed with the same errors
mine was an update only for admin + index.php

updated the permissions manually and cleared the Caches -- All OK now.

[shawn_a]

Did health check tell you that ?

[shawn_a]

For anyone else, make sure you
Flush Cache in settings
Check health check for any (other) errors.
Check your data/other/logs/error.txt for errors.
Enable debug mode and check for any page errors.

Also try the hints here
http://get-simple.info/forums/showthread.php?tid=5587

[topclass99]

Did health check tell you that ?

If you are referring to me - Yes the permission errors were all logged by health check. When changed to 755 and cleared caches. Errors disappeared and no error reported re:upgarde.

[RobA]

I also had to flush the cache to get rid of this error message.

-Rob A>

[shawn_a]

Yeah failures are now cached so if the API is down your site does not constantly check and fail causing timeouts and slow responses.

Maybe the API was overwhelmed with upgrades and such

Cache age is like 3000 seconds or an hour I think

[Draxeiro]

Yeah failures are now cached so if the API is down your site does not constantly check and fail causing timeouts and slow responses.

Maybe the API was overwhelmed with upgrades and such

Cache age is like 3000 seconds or an hour I think

Guess that is it, when I upgraded yesterday healthcheck indicated the GS was up to date. Checked it earlier today: '3.3.0 Upgrade Check Failed !'

Even though it's obviously on 3.3.0.

Flushed the cache a couple of times like Rob did and the upgrade check is gone again.

[shawn_a]

Thats the version number.
has nothing to do with the check

I guess that could be cleared.

It is not "3.3.0 upgrade check failed"
It is "version 3.3.0, upgrade check failed"

Maybe we can fix that up to be more clear

[snooze]

I had this show up on a local installation of 3.3.1 using a Bitnami MAMP stack. The next day it was gone.

[shawn_a]

The API cache is 11 minutes

[ph0t0]

After upgrading (admin/, index.php, gsconfig.php) from 3.2.3 to 3.3.1 I started to get “Upgrade Check Failed”. I’ve never seen it before. I have only one plugin, i18N Gallery. Errorlog is empty.

Flushing cache removes error, but it keeps coming back.

[shawn_a]

Interesting, it probably timing out.

In configuration.php, try uncommenting
# $api_timeout = 800; // time in ms defaults to 500

let me know if that fixes it or bump it up even more. api calls should not take that long though unless your host is really crappy.

[ph0t0]

Interesting, it probably timing out.

In configuration.php, try uncommenting
# $api_timeout = 800; // time in ms defaults to 500

let me know if that fixes it or bump it up even more. api calls should not take that long though unless your host is really crappy.

"800" did not help, error message came back. Next value?

My host is as good as it was when I used GS 3.2.3 without any errors. Ping is ≈15ms, load is fine.
Nothing else was changed, I only upgraded GS. There are also others having this, starting 3.3.0. It is GS 3.3.x that causes this error, not our unchanged hosts.

[shawn_a]

Here is the thread on how to debug

http://get-simple.info/forums/showthread...6#pid42656

$debugApi = true; // debugging output info to debugLog
$nocache = true; // debugging do not use cache

and debug mode on and post logs

[ph0t0]

Here is the thread on how to debug

http://get-simple.info/forums/showthread...6#pid42656

$debugApi = true; // debugging output info to debugLog
$nocache = true; // debugging do not use cache

and debug mode on and post logs

I'm not a sw developer and have no idea how this mechanism works, so I have one additional question, most likely stupid one.

I have denied user-agent ^curl/ in root .htaccess, it has been there for ages. Could it have effect into this? It was fine with 3.2.3.