"You have failed to authenticate with the WordPress.com API"
Simply put, I am unable to use WordPress.com stats. That line shows up when I open the Stats page in dashboard. I’m having a new site for my blog, located here: stoplayingame.com.
Other part of Jetpacks like comments, subscription, contact forms, etc, works though. Only the Stats which is having problems. I have tried deactivated the whole Jetpack plugin, then activated and reconnected again, but the problem remains.
I’ve been trying to Google for solutions, and have found some topics on WordPress support forums. But it seems nobody have the solution for this problem (except by deactivating)
Blog url: http://stoplayingame.com/
The blog I need help with is stoplayingame.com.
I’m sorry for the inconvenience, and I’ll be happy to take a closer look.
Can you take an uncropped screenshot of your Jetpack screen, then upload the image to your Media Library and paste the direct file URLs in your reply to this forum thread? Thanks.
Sure. Here are two screenshots, one from the Jetpack screen, and another is from the Jetpack Site Stats screen:
Thanks! Can you try deactivating Jetpack, download a fresh ZIP file of Jetpack, then upload the Jetpack plugin folder manually via (S)FTP?
Do you mean by that is to replace the old Jetpack files? If yes, okay… I have tried deactivating Jetpack, downloaded the fresh new file, uploaded the plugin via FTP and replaced the old one, but still… it doesn’t work. :/ It still says the same error: “You have failed to authenticate with the WordPress.com API”.
Do you mean by that is to replace the old Jetpack files?
Yes, thanks for giving that a try. :-)
Can you try clearing your browser cache, then sign out and back into your WordPress.com account?
If that doesn’t change things, can you then try an alternate browser to see if you get the same result? You can download the latest browser versions here:
If you get the same result as before, can you try deactivating all other plugins, and temporarily switch to a default theme (like Twenty Eleven or Twenty Twelve) in case it’s a plugin/theme incompatibility?
Okay… have tried cleared the browser cache, tried with different browsers, tried with different computers, all with the latest browsers… also tried deactivating all plugins (except Jetpack) and reverted to default theme.
Still not working. :(
I tried visiting the Stats page on WordPress.com here: http://wordpress.com/#!/my-stats/?unit=1&blog=41715684
Surprisingly, some of the data seems to be recorded. Here’s a screenshot: http://i.imgur.com/eS6zx.png
Oh, and there’s another thing… (sorry, wanted to edit the post but it seems I cannot)
The stats icon on wp-admin global panel (not sure what is its name) seems to be always broken. Here’s a screenshot: http://i.imgur.com/leQUg.png and here’s the image url: http://stoplayingame.com/wp-admin/admin.php?page=stats&noheader&proxy&chart=admin-bar-hours-scale
When I open the image URL, it says the same error:
You have failed to authenticate with the WordPress.com API.Also, the stats smiley also does not seem to appear even when it is not hidden.
This happens on default Twenty Eleven, Twenty Ten, and my custom theme. : /
Are you running the WordPress.com Stats plugin along with Jetpack?
Nope, only the Jetpack…
Okay, thanks for the additional information. I’ll see if our Jetpack developers have any other suggestions, and I’ll be sure to reply back to this forum thread when I hear from them.
Thanks for your patience!
Okay, thank you for your support, I’ll be waiting for it. :)
We’d like to debug something from our end which requires you to try viewing your stats right now to trigger it.
Can you try viewing your stats again?
I’m sorry, I just have got the chance to online…
I tried view my stats, but the same error remains… am I late?
Not at all, we needed you to view your stats so we could trigger something on our end to view the errors. I’ll reply back when I have another update.
Thanks for your patience. I appreciate it.
Can you ask your host if they are blocking Authorization headers on outgoing HTTP/HTTPS requests?
One of our developers wrote a simple test script that uses cURL. If your host supports cURL (it probably does), they can use it to test if Authorization headers are being sent correctly, though I imagine they are fully capable of coming up with their own test.
I’ve just sent the script to the email address linked to your WordPress.com account.
If you are able to upload files to your host (you may or may not be able to), you can run the test yourself by uploading the attached PHP file to some web-accessible directory on your host, then loading the corresponding URL in your web browser. For example, that URL might look something like:
Bryan, I’m sorry for the late reply.
Have just cheked it and I got this:
Warning: curl_exec() has been disabled for security reasons in /home/stopecom/public_html/test-outbound-authorization-headers.php on line 16
I asked the host if it’s possible to enable it, but they said it’s impossible to do that since I’m in a shared hosting… feels like a really dead-end for me.
Could I ask for alternative solutions? :/
Hi there, thanks for letting us know you weren’t able to run the debugging script. I will get back to you with next steps.
Not being able to run the test script isn’t a deal breaker, it just means you’ll need to ask your host for help. Here’s a suggestion on what to ask them:
Hi [My faithful Host],
I’m having trouble with the Jetpack WordPress Plugin created by WordPress.com: http://jetpack.me/
I’ve spoken with their developers, and, so far, their best guess is that the problem because Authorization headers on outbound HTTP/HTTPS requests are being blocked. They’re not sure, though, because I was unable to run a test script they sent me; the test uses curl_exec(), which is disabled on my site.
Are Authorization headers blocked on outgoing HTTP/HTTPS requests? Is there a way for me to test that myself?
Thanks for your help,
If your host is blocking Authorization headers, and they are unwilling to unblock them, Jetpack will unfortunately not work on your host.
If they are not blocking Authorization headers, and the problem is something different, we’ll keep working on a solution.
Sorry for all the hassle,
The topic ‘"You have failed to authenticate with the WordPress.com API"’ is closed to new replies.