# Backups have started failing due to server time being wrong

**URL:** <https://meta.discourse.org/t/backups-have-started-failing-due-to-server-time-being-wrong/108802>\
**Category:** Product Support\
**Created:** [February 11, 2019, 3:34am 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:** 10

<div class="post-metadata">

**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:** [February 14, 2019, 11:30am UTC](https://meta.discourse.org/t/backups-have-started-failing-due-to-server-time-being-wrong/108802/10 "2019-02-14T11:30:52Z")

</div>

> [@modius](#):
>
> So that was promising… but backup view still dead with the same error. So then I restarted the app:

Argh.

Was dealing with two Discourse forums with similar IPs. Updating the time on one and checking the backups on the other. Looks like both are working now! Huzzah 🙌

AWS has an issue once the server falls out of sync by 5 minutes or more:

Fix for Ubuntu was to reset the clock.

```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

```

---

_[View the full topic](https://meta.discourse.org/t/backups-have-started-failing-due-to-server-time-being-wrong/108802)._
