Your WordPress.com account is not authorized to view the stats of this blog

Mine are broken too still. Has WP had any official word on this?

Mine too. The graph is mostly accurate, but the daily ‘Top Posts and Pages’ are way off. I manually reset my time zone to see if it would wake it up, but it did nothing. It doesn’t give a damn what time zone you’re in, the top posts and pages are immune . .

Well we can’t afford to miss stats with over 10,000 visits a day, i modified the jet-pack to only have the WordPress stats and thats it.
If anybody would like a copy i can email it to you?

Hi All
I faced the same issue and when I fellow the instruction by disabling WPstate and install jetpack I encountered the fellowing error

Jetpack could not contact WordPress.com: register_http_request_failed.
This usually means something is incorrectly configured on your web host.
error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none

please your help needed
Regards,
SaFi

Hi! The problem is resolved. Here is my correspondence with support

> Sorry for my bad english ??
>
> On my WP blog (alekseybaryshev.ru), I installed the plugin
> WordPress.com Stats. I used the API Key from the page
> apikey.wordpress.com. When I clicked on the button “Add blog to
> WordPress.com” i saw a message: “Error from last API Key attempt:
> The owner of that API Key (alekseybaryshev) is not on the access list
> for this blog (12860730). Stats was installed using a different API
> key. The owner of the original key can add users to the access list,
> or you can contact WordPress.com support.”
> Statistics on my blog is not working.
> Please, help me. My account on WordPress.com is alekseybaryshev

I’m sorry about the temporary issue you had viewing your stats.

This issue is now resolved and you should be able to view your stats again.

Please let us know if you still have any issues.

Cheers
—
Peter
WordPress.com | Automattic

On installations where I did nothing but waited stats got fixed by themselves but where I tried Jetpack (which did not work) the Wp stats says now:

The API key “xxxxxxxxxx” belongs to the WordPress.com account “NN”. If you want to use a different account, please enter the correct API key.

The link adds “&action=reset&_wpnonce=xxxxxx” after url and then… nothing.

Sqwer: The issue is NOT fixed. My stats are still hosed. ??

@ PerfectCr: write to support at wordpress dot com, like Sqwer did, and they will fix it.
I also wrote to them yesterday and they responded and mine are now fine (and they also reflect that Support visited my site, so they did do something!)

Not everything came right though, as now the graph is slow to update and shows a lower number of visits than the BlogStats Today’s views (bottom left) show. I have again written to support and will see what they say.

Mine have all gone belly up too

I have 20+ domains and 5 of those are multi-site – I have users screaming at me that they need to see the stats … should I make each of them contact wordpress.com support?

Do I recall correctly that WordPress has 40 million+ self-hosted installs? And how many of those are multi-user multisites? I guess there’ll be no time off at dot com support this side of Christmas?

Esmi – please get a definitive solution from the support teams – this concept of contacting support for manual intervention is not an efficient or acceptable solution. Someone broke the code, therefore someone there needs to fix it as a global solution.

I’m getting the not authorised error in self-hosted blog dashboards, and on dot com, I’m also told the account is not authorised to see the stats for the blogs – this is via the same dot com account that owns the API key for all my blogs. In the dot com account new subscriptions page, all blogs are showing as “not visible” because the API connection appears broken, and there is no way to switch visibility – ergo, they have failed to include auto-switching and account ID to API key association.

How much of this is also to do with the spyware encrypted encoding they inserted into wp-stats a couple of minor versions back for dumping user habits to a third party marketing company? Matt himself confessed to that and said it was needed for “exciting new features” to be placed in WP-Stats, which most people immediately stated they didn’t want – they want the original concept of the plugin – lightweight, fast, with no site delivery overhead. That’s something that went out the window when wordepress/automattic got into bed with the 3rd-party data collators … and probably the cause of all the above complaints about loss of site speed.

Everyone using WP-Stats needs it fixed, and adhering to what it says on the tin (no additional server overhead – that includes losing the 10K of encrypted encoding added to footers).

Yet another colossal muck-up to add to the many perpetrated last year.

Finally, I found how to view the stats for individual domains and sites in my wordpress.com dashboard, and can see stats there, but only for pre-3.1 sites.

All sites upgraded to 3.1 are saying the site API key belongs to a different user, even though they are all under the single dot com user name and API key, which is the same as for the pre-3.1 sites that are still displaying stats.

To me, this makes it absolutely a 3.1 issue (code incompatibility, or deliberate killing of non-jetpack wordpress Stats?) and I’ve stopped all core upgrades until it gets sorted out.

I do not want jetpack – it will interfere with WordBooker, and other facebook and twitter plugins I use – one of them (Social Connections) is even tagged in the pinned thread as incompatible with 3.1

The analogy that comes to mind is trading in your car, and the new car having no dashboard clocks as standard. Adding them might be free for now, but the add-in then includes tracking chips to show where you are and what speed you drive at that report to police HQ, and includes digital road-toll chips that auto-deduct from your bank, etc. It also records who you carry as passengers, where you take them, and how often … which is exactly what the base64 obfuscated QuantCast footer-code did in the last version of wordpress Stats.

This is a serious error by wordepress in my opinion … I thinking I’ll have to switch to google for all my analytics from here on out. At least that’ll provide me with better targeted AdSense placements as well.

Shame, because I did like the original simplicity of wordpress Stats

problem resolved: deactivate WP-stats, install JetPack!

I’ve just this on my other site, and hey presto! It works!

And, I just love Jetpack ??

@katydigg: Great for you. Does not work for me.

@sanapaino: Are you running WP Super Cache plugin?

Jet Pack can fix this issue folks and i have a version with just stats, so its like replacing the stats plugin with another stats plugin!

IF YOU WOULD LIKE A COPY EMAIL ME!

Update – I’ve noticed that the latest updates to jetpack/wpstats that were released yesterday fixed all issues. Thanks WP