# Discourse stuck on "Currently Upgrading"

**URL:** https://meta.discourse.org/t/discourse-stuck-on-currently-upgrading/39072
**Category:** Self-hosting
**Created:** [February 5, 2016, 12:29am UTC](https://meta.discourse.org/t/discourse-stuck-on-currently-upgrading/39072 "2016-02-05T00:29:49Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![amotl](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/amotl/32/109873_2.png) [@amotl](https://meta.discourse.org/u/amotl)
#### Post date: [September 18, 2018, 11:58am UTC](https://meta.discourse.org/t/discourse-stuck-on-currently-upgrading/39072/15 "2018-09-18T11:58:30Z")

</div>

We wanted to inform you that we just ran into this issue for the first time and “`launcher rebuild app`” didn’t help, so we followed the advice from @eviltrout by flushing Redis:

> [@"Currently upgrading" even after a rebuild](https://meta.discourse.org/t/currently-upgrading-even-after-a-rebuild/33557/7):
>
> Had you started an upgrade in the web side before you did it on the command line? I’m just trying to understand how the flag got stuck in that position. The easiest way to unlock it is to flush redis. $ ./launcher enter app $ redis-cli flushall

Hitting the “Reset Upgrade” button sounded too risky for us as it suggests anything would be rolled back, which we didn’t want to do because everything seemed to work flawlessly after the upgrade got applied successfully, as always.

At this place, we want to tell you that every time we hit the “Upgrade Discourse” button, we are again amazed by the shipping and production deployment quality of Discourse. Kudos to the whole team and keep up the spirit!

---

_[View the full topic](https://meta.discourse.org/t/discourse-stuck-on-currently-upgrading/39072)._