# Show an error page when rebuild
**URL:** https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204
**Category:** Feature
**Created:** [19 juni 2015 om 11:24 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204 "2015-06-19T11:24:55Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@michael\_solomon](https://meta.discourse.org/u/michael_solomon)
#### Post date: [19 juni 2015 om 11:24 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/1 "2015-06-19T11:24:56Z")
Hi,
When I “./launcher rebuild app” my Discourse and try to enter to my Discourse forum, its shows “502 Bad Gateway” error.
I know it’s just 10 minutes but I think it’s more professional to show to our users a pretty error message when we update our Discourse.
Thanks you,
Miki
P.S: sorry for my lame english. working on it!
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [19 juni 2015 om 23:17 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/2 "2015-06-19T23:17:30Z")
Is this even possible on the standard Docker install @sam or @riking?
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [20 juni 2015 om 00:14 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/3 "2015-06-20T00:14:38Z")
For things like this, we maintain a fully separate one-page website with the same valid SSL certs as our app/site.
When it’s time for maintenance, we point DNS at that server, do our thing, and point it back. Requires a short TTL to make it worthwhile, but that works for us.
I suppose something like that could be done in a separate docker setup on the same host?
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [20 juni 2015 om 03:07 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/5 "2015-06-20T03:07:18Z")
I suppose that the inner NGINX could have a 502 rule to serve a page like this:
```plaintext
The Discourse server is starting up, please wait.....
```
Because if you can see that page at all, it means that the container is running and Unicorn is unreachable.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [20 juni 2015 om 03:14 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/6 "2015-06-20T03:14:51Z")
Yes why don’t you submit that change. Good idea!
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [20 juni 2015 om 03:56 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/7 "2015-06-20T03:56:51Z")
Does not solve much, the issue is that the container must be stopped during rebuild of standalone
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [26 augustus 2015 om 13:57 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/8 "2015-08-26T13:57:30Z")
In my use case, that _would_ help a lot: I use nginx running on the host since I serve multiple subdomains. This already shows a nice message while the container is down – but `bad gateway` still leaks through while the conainer starts up.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [26 augustus 2015 om 14:20 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/9 "2015-08-26T14:20:32Z")
This is a band-aid at best.
If NGINX is serving a 502 at all then any customers using services such as Cloudflare will never see that error, they’ll see the 521 error from Cloudflare.
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [4 december 2025 om 11:36 UTC](https://meta.discourse.org/t/show-an-error-page-when-rebuild/30204/10 "2025-12-04T11:36:01Z")