Support » Fixing WordPress » Jetpack problem: "invalid_signature: The timestamp is too old."

  • I was trying to fix the “Your account is not authorized to view the stats of this blog” issue. Since many people are saying that installing Jetpack ( would fix it, I tried this new plugin.

    First I deactivated Stats, then I installed Jetpack and authorized the Stats module with my account. Everything should be fixed and stats should be up and running again (as far as I’ve read in the forums).

    Now the issue is when I access /wp-admin/admin.php?page=stats on my blog it only shows the following message:

    invalid_signature: The timestamp is too old.

    How can I fix it?

Viewing 15 replies - 1 through 15 (of 15 total)
  • Moderator Michael Adams (mdawaffe)



    Your server’s clock is probably not set correctly. A future version of Jetpack will probably work around this problem. In the meantime, setting your server’s clock to the correct time should fix the issue.

    What’s the URL of your site?

    @ mdawaffe

    My blog is

    Moderator Michael Adams (mdawaffe)



    @tatiane: confirmed. Your server thinks the current time is
    Fri, 18 Mar 2011 16:55:25 GMT
    when it is actually
    Fri, 18 Mar 2011 18:13:50 GMT

    If you don’t know how to update your server’s time, I suggest contacting your host.

    @ mdawaffe

    I seem to be on a dead end now, because support on my host is taking way to long to answer requests. =(

    Is it something I can change on my own? Or do I depend on the host to change some server configuration?

    Moderator Michael Adams (mdawaffe)



    There is probably nothing you can do on your own. We hope to release a new version of the Jetpack plugin next week that will address this issue.

    @ mdawaffe

    In the meantime, I’ll rely only on Google Analytics. Hopefully Stats will be up and running here soon.


    I’ve just updated Jetpack to version 1.1.1, but the problem persists. Message: “invalid_signature: The timestamp is too old.”

    Same issue here. My web host is not very supportive to set the server clock correctly. They keep telling that their servers clock are correct, but it is ~14 minutes older than the official time.

    I was still without site stats from Jetpack because this issue with server timestamp. So I deactivated Jectpack and installed again Stats.

    I decided to try it out just to take the chance, my surprise is that Stats is working just fine now and I can see the visits of Friday (March 18, when the plugin stopped to display info on my dashboard) and of the weekend.

    I’ll stay with Stats until the timestamp issue is solved. It seems that Jetpack is aimed for self-hosted WP blogs.

    Nah, that is just a very interesting coincidence…

    @ lealcy

    I know. I just posted it here because it may help more people to know that the Stats is back. I believe people at are working on that.

    Same error here. invalid_signature: The timestamp is too old.

    Same error, How can i know the know my server’s time?

    @daniel, just create a php script with the code below:

    <?php echo date(‘r’);

    When you run it, it will show you the current server time.

    @lealcy, Thanks I’ll try before write to the hosting company.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Jetpack problem: "invalid_signature: The timestamp is too old."’ is closed to new replies.