Same here. Stats just disappeared after the Jetpack upgrade. My site is hosted on : http://www.jonroemer.com/blog/ .
I get the same message as the poster above: “We were unable to get your stats just now. Please try again.” BUT -> this is only on my desktop computer. Mac Pro, OS 10.7.5, Safari 6.0.1.
On my iPhone I can still see my stats via the WordPress iOS App 3.1.4.
Follow up to the above -> the stats cannot be seen via Safari on the iPhone but as I wrote above they can be viewed via the WordPress iOS App 3.1.4.
I am getting the same error after upgrading.
We also have been bit by the “stats not available now” issue post update:
http://glutenfreecanteen.com/
I have the same problem. New update = no stats.
Unravelling Complex Chronic Illness
“We were unable to get your stats just now. Please try again.”
I as well have been getting this since I updated this morning. I am running Multisite and it is the same for all of my sites.
I manually downgraded to 1.2 which I had on my side of the ftp and I ran the automatic upgrade on wordpress through the site. Downgrading brought stats back and they’ve been working all day, for some reason the new plugin is not working correctly with server side for displaying the stats.
Odd that someone reported that it works through an ios app… which I’ve never used. I only view stats through my browsers be it chrome, firefox or opera mobile.
Anyways, you have the option of downgrading or waiting until it’s fixed.
Also having the same issue. As of this morning Jetpack 1.8 is reporting the following error message on two blog sites completely independent of each other, http://aushiker.com and http://btawa.org.au:
We were unable to get your stats just now. Please try again.
Frustrating.
Andrew
Same here.
This is getting to be a bit of a joke – it is the third time in little over 12 months a routine Jetpack update has toasted the stats function.
Don’t they test these things before they release them?
Last time it took several days to fix.
Dumped JetPack 1.8 and gone back to JetPack 1.7. All good now.
Andrew
Also having the same problem..
This bug has been fixed in Jetpack 1.8.1, which is now available at http://wordpress.org/extend/plugins/jetpack/
Thanks Chris. Looks like it works fine.
