# 2.4.0.beta8 update gave me the white page of death
**URL:** https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299
**Category:** Support
**Created:** [December 6, 2019, 7:59pm UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299 "2019-12-06T19:59:57Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@strangecosmos](https://meta.discourse.org/u/strangecosmos)
#### Post date: [December 6, 2019, 7:59pm UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/1 "2019-12-06T19:59:57Z")
I just updated my Discourse at [gradientdescent.co](https://gradientdescent.co/) the same way I always do. ( **Edit:** That is, via the one-click browser upgrade.) There was an error during the 2.4.0.beta8 update. It didn’t complete the first time I attempted the update. I tried it again and the update said it completed successfully, but now the site is bricked. I went into the console on Digital Ocean and rebooted my server. I logged in and restarted the Discourse docker for good measure. But I’m still getting the white page of death.
**Edit:** If you’re having this issue, the best course of action seems to be to use the console/terminal and type in these commands:
```
cd /var/discourse
git pull
./launcher rebuild app
```
If you haven’t already updated to 2.4.0.beta8, avoid using the one-click browser upgrade.
---
### Author:  [@AndreTechExec](https://meta.discourse.org/u/AndreTechExec)
#### Post date: [December 6, 2019, 8:25pm UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/2 "2019-12-06T20:25:28Z")
Same thing just happened to me. I am not sure what to do now.
---
### Author:  [@ravenzachary](https://meta.discourse.org/u/ravenzachary)
#### Post date: [December 6, 2019, 8:38pm UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/3 "2019-12-06T20:38:41Z")
@strangecosmos @AndreTechExec
I ran into problems last night with the upgrade and was able to get around the problems by doing the following steps in order:
1. Revert to a beta7 backup after the beta8 upgrade failure (in my case, a beta7 snapshot in Digital Ocean, I always take a full snapshot before an upgrade)
2. Upgrade the Docker release first from the Admin Upgrade page
3. Reboot the server (not just Discourse, the whole server or virtual machine)
4. Upgrade to beta8 from the command line as follows:
Based on other reports in Meta Discourse, it looks like the Docker update was causing problems and if you did both back-to-back from the one-click installer via the Admin Upgrade page, it failed for people.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [December 6, 2019, 9:20pm UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/4 "2019-12-06T21:20:11Z")
> [@strangecosmos](#):
>
> I updated my Discourse at [gradientdescent.co](https://gradientdescent.co/) the same way I always do. There was an error during the 2.4.0.beta8 update.
Was this via /admin/upgrade or ssh? You don’t tell us which upgrade route you always use.
> [@ravenzachary](#):
>
> cd /var/discourse
> git pull
> ./launcher rebuild app
Did you attempt this prior to reverting to b7, restoring a backup and using admin/upgrade? It’s all that should have been necessary here:
> [@After updating Docker with one-click update, no Versions are showing](https://meta.discourse.org/t/after-updating-docker-with-one-click-update-no-versions-are-shwoing/135219/8):
>
> I just fixed the root cause that made that screen go white. We had an upgrade to our docker manager plugin which was not compatible with older versions of discourse, I added some code to restore compatibility. Unfortunately once that screen goes white your only recourse is: cd /var/discourse ./launcher rebuild app
---
### Author:  [@strangecosmos](https://meta.discourse.org/u/strangecosmos)
#### Post date: [December 6, 2019, 9:27pm UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/5 "2019-12-06T21:27:04Z")
> [@Stephen](#):
>
> Was this via /admin/upgrade or ssh? You don’t tell us which upgrade route you always use.
I used the one-click web interface on /admin/upgrade.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [December 6, 2019, 9:27pm UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/6 "2019-12-06T21:27:37Z")
Ok, as above you didn’t need to revert to b7, a rebuild via SSH would have brought things back in line.
---
### Author:  [@strangecosmos](https://meta.discourse.org/u/strangecosmos)
#### Post date: [December 7, 2019, 12:09am UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/7 "2019-12-07T00:09:37Z")
In the console, I did:
```
cd /var/discourse
git pull
./launcher rebuild app
```
That fixed it. The site is up and running again.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [December 7, 2019, 2:22am UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/8 "2019-12-07T02:22:20Z")
I believe @sam fixed this bug? Do we need a new beta release @sam?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [December 7, 2019, 2:42am UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/9 "2019-12-07T02:42:07Z")
We did fix the bug, but sadly people who experienced it in the last few days and are stuck on a white screen need to do a rebuild
We do not need a new beta as the fix is retroactive
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [December 7, 2019, 10:27pm UTC](https://meta.discourse.org/t/2-4-0-beta8-update-gave-me-the-white-page-of-death/135299/11 "2019-12-07T22:27:25Z")