What does the "Timestamp expired" response from REST API mean when triggering an event?

Part of Pusher's authentication process is to require your machine's timestamp as part of the request. This is represented as the "auth_timestamp" parameter in the request. For more info, please see: http://pusher.com/docs/rest_api#authentication

If the timestamp is not within the allowed time period the response body will be similar to the following:

Timestamp expired: Given timestamp (2013-06-17T15:39:38Z) not within 600s of server time (2013-06-17T17:09:21Z)

To fix this issue, you will need to:
  • Update your system time to reflect the current date and time
  • Sync your system's clock to a time server to automatically update this in future (Optional)
If required, for more information, see below:


To check the current machine time on your system, please run the date command from the console. Is the output correct?

If not, you can correct the time on your machine by going to your console and using date to modify it. In most cases, you will need to give yourself sudo access on your machine.

$ sudo date MMddhhmmyyyy


MM - Month (two-digit numeric month)
dd - Day (two-digit numeric day i.e. day of month)
hh - Hour
mm - Minutes
yy - Year

So, for example, if we wanted to change the current time to 3:13pm on Sunday 16th June 2013, we would type the following:

$ sudo date 061615132013


Coming soon.
Was this article helpful?
0 out of 0 found this helpful
Haven't found what you were looking for?
Submit a ticket