# Reverting version after problematic update

**URL:** <https://meta.discourse.org/t/reverting-version-after-problematic-update/240656>\
**Category:** Self-hosting\
**Created:** [October 1, 2022, 5:51pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656 "2022-10-01T17:51:29Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [October 2, 2022, 6:15pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/13 "2022-10-02T18:15:32Z")

</div>

> [@Stephen](#):
>
> You’re going to need to pin the exact version of Discourse in your app.yml by inspecting your backup file

Not entirely. Any higher version will do. So if your backup was from stable then you can either install `stable` or check out a specific commit (`7647cf6a22aa7f9454123b24262ca04290b4d774` for 2.9.0 beta 9)

---

_[View the full topic](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656)._