# The site is offline when installing the plugin

**URL:** <https://meta.discourse.org/t/the-site-is-offline-when-installing-the-plugin/297627>\
**Category:** Self-hosting\
**Created:** [March 2, 2024, 7:27pm UTC](https://meta.discourse.org/t/the-site-is-offline-when-installing-the-plugin/297627 "2024-03-02T19:27:59Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)\
**Post date:** [March 3, 2024, 9:10am UTC](https://meta.discourse.org/t/the-site-is-offline-when-installing-the-plugin/297627/16 "2024-03-03T09:10:46Z")

</div>

Chat may have things in it that are different than the regular site viewing as I believe it is more real time access vs being able to cache pages.

> [@Jagster](#):
>
> My opinion is that situation where we don’t inform at all downtime for already login users is the biggest single UX-issue in Discourse. Sure I can understand explanations where is comes from very nature of this app, and devs are kind of painted themselves at corner from the very beginning (similar situations like with drafts and few other things), but it doesn’t erase the problem itself

Agreed. Planned announced maintenance imho is best like in the days old of dos based dial up bbses. There was an option to to have a system message warning the planned maintenance shutdown was coming and would sign out users at the designated time. In those days it was typically for doing mail packets between networked bbses.

---

_[View the full topic](https://meta.discourse.org/t/the-site-is-offline-when-installing-the-plugin/297627)._