# Maintenance page workaround - can this be done?

**URL:** <https://meta.discourse.org/t/maintenance-page-workaround-can-this-be-done/408967>\
**Category:** Self-hosting\
**Tags:** cloudflare\
**Created:** [July 31, 2026, 8:22am UTC](https://meta.discourse.org/t/maintenance-page-workaround-can-this-be-done/408967 "2026-07-31T08:22:23Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![Lilly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lilly/32/575047_2.png) [@Lilly](https://meta.discourse.org/u/Lilly)\
**Post date:** [August 1, 2026, 1:47pm UTC](https://meta.discourse.org/t/maintenance-page-workaround-can-this-be-done/408967/19 "2026-08-01T13:47:06Z")

</div>

i disagree and do think it’s worth the maintenance page. in my experience, when people see the Discoure error page the first thing they do is hit refresh and then they will see the brief maintenance page that will then automatically reload the site when the container swap is complete. it isn’t a lot of work to set up and you only have to do it once. during a rebuild with the dual container configuration, the bootstrap part happens in the background and users can still use the site; it is the container switch over that causes the brief downtime (unlike a standard single container configuration)

server cost and selection is a completely different discussion and should be in another separate topic than setting up a maintenance page.

edit: i see [there is a topic here](https://meta.discourse.org/t/any-cheaper-alternatives-to-hetzner/409037/) and i replied there.

---

_[View the full topic](https://meta.discourse.org/t/maintenance-page-workaround-can-this-be-done/408967)._