# Discourse stuck on "Currently Upgrading"

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

<div class="post-metadata">

### Author: ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [5 Fevereiro , 2016 04:28 UTC](https://meta.discourse.org/t/discourse-stuck-on-currently-upgrading/39072/6 "2016-02-05T04:28:33Z")

</div>

no need to feel silly… the idea that a rebuild should reset the `Upgrading...` state has come up before:

[https://meta.discourse.org/t/upgrade-currently-upgrading-forever/35850/?u=watchmanmonitor](https://meta.discourse.org/t/upgrade-currently-upgrading-forever/35850/)

and

> [@"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

---

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