# Backups have started failing due to server time being wrong **URL:** \ **Category:** Product Support\ **Created:** [11.Февраль.2019 03:34:42 UTC](https://meta.discourse.org/t/backups-have-started-failing-due-to-server-time-being-wrong/108802 "2019-02-11T03:34:42Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![modius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/modius/32/108600_2.png) [@modius](https://meta.discourse.org/u/modius)\ **Post date:** [14.Февраль.2019 10:44:52 UTC](https://meta.discourse.org/t/backups-have-started-failing-due-to-server-time-being-wrong/108802/7 "2019-02-14T10:44:52Z")
> [@codinghorror](#): > > Is the server clock time off? Well I tried the following: ```plaintext $ date Thu Feb 14 05:32:16 EST 2019 $ ntpdate ntp.ubuntu.com 14 Feb 05:26:58 ntpdate[12447]: step time server 91.189.91.157 offset -408.660323 sec $ date Thu Feb 14 05:27:02 EST 2019 ``` So that was promising… but backup view still dead with the same error. So then I restarted the app: ```plaintext $ ./launcher restart app + /usr/bin/docker stop -t 10 app app starting up existing container + /usr/bin/docker start app app ``` Still no dice 🎲 🎲 ```plaintext $ reboot The system is going down for reboot NOW! ``` It’s a Digital Ocean droplet running vanilla Ubuntu. Comes back up… still not working and the time offset is gone: ```plaintext $ ntpdate ntp.ubuntu.com 14 Feb 05:36:42 ntpdate[2375]: adjust time server 91.189.91.157 offset -0.001713 sec ``` I was convinced the 5 minute time correction would be key. Is it possible it’s just stuck now? Any other ideas? * * * > [@pfaffman](#): > > Do you have uploads and backups in the same bucket? No. Separate bucket on S3 for backups; set-up unchanged for as long as anyone can remember. * * * > [@gerhard](#): > > Check `/logs` for errors or click on the `/admin/backups.json` link in the error page to get additional details about the error. So I couldn’t find anything interesting in logs on the host but i did look at the Discourse logs and noticed that it reports a slightly different error to the `/admin/bakups.json` ```plaintext Failed to list backups from S3: The difference between the request time and the current time is too large. ``` Notice the extra prefix: **Failed to list backups from S3** --- _[View the full topic](https://meta.discourse.org/t/backups-have-started-failing-due-to-server-time-being-wrong/108802)._