# Conflicting "out of date" vs "up to date" statuses

**URL:** https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339
**Category:** Support
**Created:** [20 במרץ,‏ 2016,‏ 6:23pm UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339 "2016-03-20T18:23:13Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![markplindsay](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/markplindsay/32/121849_2.png) [@markplindsay](https://meta.discourse.org/u/markplindsay)
#### Post date: [1 במאי,‏ 2016,‏ 1:54am UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/8 "2016-05-01T01:54:01Z")

</div>

`/var/discourse/launcher rebuild app` successfully updated Discourse for me. I am just gonna do it that way from now on.

FWIW, I suspect I have a weird Linode-specific Docker install on my Linode instance. This may or may not be the cause of my inability to update within the Discourse UI, [and some other problems](https://meta.discourse.org/t/jobs-handledexceptionwrapper-wrapped-socketerror-getaddrinfo-name-or-service-not-known/42652/3).

---

_[View the full topic](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339)._