# Discourse offline after failed upgrade "bootstrap failed with exit code 5"

**URL:** https://meta.discourse.org/t/discourse-offline-after-failed-upgrade-bootstrap-failed-with-exit-code-5/288193
**Category:** Self-hosting
**Created:** [December 11, 2023, 6:42am UTC](https://meta.discourse.org/t/discourse-offline-after-failed-upgrade-bootstrap-failed-with-exit-code-5/288193 "2023-12-11T06:42:03Z")
**Posts on this page:** 5
**Page:** 2

<div class="post-metadata">

### Author: ![Richie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/richie/32/115110_2.png) [@Richie](https://meta.discourse.org/u/Richie)
#### Post date: [December 11, 2023, 11:22am UTC](https://meta.discourse.org/t/discourse-offline-after-failed-upgrade-bootstrap-failed-with-exit-code-5/288193/21 "2023-12-11T11:22:07Z")

</div>

Thanks for the help and support everyone, we’re back online.

I’ll follow the rsync guide and port everything to new hardware next week, without panicking 😃

---

<div class="post-metadata">

### Author: ![IanLawrence](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ianlawrence/32/120247_2.png) [@IanLawrence](https://meta.discourse.org/u/IanLawrence)
#### Post date: [December 28, 2023, 1:53pm UTC](https://meta.discourse.org/t/discourse-offline-after-failed-upgrade-bootstrap-failed-with-exit-code-5/288193/22 "2023-12-28T13:53:59Z")

</div>

> [@JammyDodger](#):
>
> Did you try `./launcher start app` to try and get the pre-rebuild one back up?

Launching the old image failed because migrations are forward only and irreversible. The latest plan is to build the docker image for discourse locally and push the container to the server

---

<div class="post-metadata">

### Author: ![IanLawrence](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ianlawrence/32/120247_2.png) [@IanLawrence](https://meta.discourse.org/u/IanLawrence)
#### Post date: [December 28, 2023, 5:53pm UTC](https://meta.discourse.org/t/discourse-offline-after-failed-upgrade-bootstrap-failed-with-exit-code-5/288193/23 "2023-12-28T17:53:07Z")

</div>

This worked and we got the server back

---

<div class="post-metadata">

### Author: ![Richie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/richie/32/115110_2.png) [@Richie](https://meta.discourse.org/u/Richie)
#### Post date: [December 28, 2023, 8:32pm UTC](https://meta.discourse.org/t/discourse-offline-after-failed-upgrade-bootstrap-failed-with-exit-code-5/288193/24 "2023-12-28T20:32:27Z")

</div>

Interesting workaround @IanLawrence🤔

Are you suffering the same issues we are with our outdated Ubuntu 18.04.6 server?

---

<div class="post-metadata">

### Author: ![IanLawrence](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ianlawrence/32/120247_2.png) [@IanLawrence](https://meta.discourse.org/u/IanLawrence)
#### Post date: [February 22, 2024, 1:16pm UTC](https://meta.discourse.org/t/discourse-offline-after-failed-upgrade-bootstrap-failed-with-exit-code-5/288193/25 "2024-02-22T13:16:05Z")

</div>

> [@Richie](#):
>
> Are you suffering the same issues we are with our outdated Ubuntu 18.04.6 server?

Yes exactly the same. Upgrade blew up over Christmas holidays on prod server and needed to manage the blast radius

[Previous page](https://meta.discourse.org/t/discourse-offline-after-failed-upgrade-bootstrap-failed-with-exit-code-5/288193.md?page=1)