# 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:** 16
**Page:** 1

<div class="post-metadata">

### Author: ![hiccup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hiccup/32/141306_2.png) [@hiccup](https://meta.discourse.org/u/hiccup)
#### Post date: [October 1, 2022, 5:51pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/1 "2022-10-01T17:51:29Z")

</div>

> [@Main CSS and mobile style not working after update "2.9.0.beta10"](https://meta.discourse.org/t/main-css-and-mobile-style-not-working-after-update-2-9-0-beta10/240553/5):
>
> The temporary fix is to revert to Beta9

How I can revert?

Thanks

---

<div class="post-metadata">

### Author: ![Alexander](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alexander/32/497634_2.png) [@Alexander](https://meta.discourse.org/u/Alexander)
#### Post date: [October 1, 2022, 6:07pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/2 "2022-10-01T18:07:43Z")

</div>

> [@hiccup](#):
>
> How I can revert?

Normally it is not recommended in my opinion, but the steps would be the following:

In your app.yml, in the version tag (Uncomment the line), replace test-passed with “v2.9.0.beta9” (Corresponds to the tag on GitHub), and rebuild

Although you will have to switch back to test-passed sooner or later

> <https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml#L37>

---

<div class="post-metadata">

### Author: ![hiccup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hiccup/32/141306_2.png) [@hiccup](https://meta.discourse.org/u/hiccup)
#### Post date: [October 1, 2022, 7:18pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/3 "2022-10-01T19:18:43Z")

</div>

Can I use the same steps to downgrade to the “Stable” version?

---

<div class="post-metadata">

### Author: ![Alexander](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alexander/32/497634_2.png) [@Alexander](https://meta.discourse.org/u/Alexander)
#### Post date: [October 1, 2022, 7:23pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/4 "2022-10-01T19:23:30Z")

</div>

Theoretically, yes, but certainly that change could lead to a broken site.

---

<div class="post-metadata">

### Author: ![hiccup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hiccup/32/141306_2.png) [@hiccup](https://meta.discourse.org/u/hiccup)
#### Post date: [October 2, 2022, 12:31pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/5 "2022-10-02T12:31:53Z")

</div>

I appreciate your help,

i tried but it didn’t work

I think I have to wait for an update to solve the BUG

Unfortunately the site without css is so bad user experience

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [October 2, 2022, 12:41pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/6 "2022-10-02T12:41:41Z")

</div>

There’s nothing theoretical here. Migrations **aren’t** reversible.

Downgrades without a backup are **never** an option.

---

<div class="post-metadata">

### Author: ![hiccup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hiccup/32/141306_2.png) [@hiccup](https://meta.discourse.org/u/hiccup)
#### Post date: [October 2, 2022, 1:07pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/7 "2022-10-02T13:07:33Z")

</div>

i have old backup.

So can i downgrades by edit app.yml version to “Stable v2.8.9 ”. and rebuild app ?

is this possible ?

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [October 2, 2022, 2:37pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/8 "2022-10-02T14:37:45Z")

</div>

To avoid any database issues you will need to pinpoint the exact version in the backup and build a fresh instance on that, then restore your database.

The issue here is that you upgraded a production site without testing it first, if your site is important then you need to reduce the risk of these updates by first testing it on a representative staging copy.

---

<div class="post-metadata">

### Author: ![hiccup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hiccup/32/141306_2.png) [@hiccup](https://meta.discourse.org/u/hiccup)
#### Post date: [October 2, 2022, 3:41pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/9 "2022-10-02T15:41:35Z")

</div>

My old backup for “Discourse 2.8.9”  
How to build a fresh instance for 2.8.9?

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [October 2, 2022, 3:48pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/10 "2022-10-02T15:48:09Z")

</div>

Were you previously on `tests-passed` or `beta`?

If you were on `tests-passed` then you need to do as I said above and check your backup for the precise version it was taken at.

---

<div class="post-metadata">

### Author: ![hiccup](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hiccup/32/141306_2.png) [@hiccup](https://meta.discourse.org/u/hiccup)
#### Post date: [October 2, 2022, 4:41pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/11 "2022-10-02T16:41:02Z")

</div>

backup for discourse 2.8.9 - previously on `tests-passed` .

can you tell me the **steps** to build a fresh instance for this backup.

How can install fresh discourse 2.8.9 so i can import my backup latter without risk?

Thanks.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [October 2, 2022, 5:55pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/12 "2022-10-02T17:55:14Z")

</div>

If you were on tests-passed then a fresh 2.8 beta 9 install work won’t work for you, which is why you can’t use `v2.9.0.beta9` as suggested by someone else above. As the name indicates, `tests-passed` is the latest version of merged changes which has passed the requisite suite of tests.

You’re going to need to pin the exact version of Discourse in your app.yml by inspecting your backup file.

If the plugins you use have been updated since the build in your backup then you may also need to pin those versions in the plugin section of your `app.yml`.

---

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

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [October 2, 2022, 6:19pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/14 "2022-10-02T18:19:10Z")

</div>

Right, but it’s from test-passed, not b9 or stable.

> [@hiccup](#):
>
> backup for discourse 2.8.9 - previously on `tests-passed` .

It’s an update which broke compatibility, hence aiming for a known-good configuration.

---

<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:24pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/15 "2022-10-02T18:24:26Z")

</div>

I think he means “my backup is from 2.8.9 and I was previously on tests-passed”  
So if he restores the backup then anything \>= 2.8.9 will do.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [March 23, 2023, 4:16pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/16 "2023-03-23T16:16:46Z")

</div>

2 posts were split to a new topic: [Safe to upgrade via /admin?](https://meta.discourse.org/t/safe-to-upgrade-via-admin/259180)
