# Discourse Went Down Suddenly. No one can log in

**URL:** https://meta.discourse.org/t/discourse-went-down-suddenly-no-one-can-log-in/272552
**Category:** Self-hosting
**Tags:** two-container
**Created:** [July 23, 2023, 1:27pm UTC](https://meta.discourse.org/t/discourse-went-down-suddenly-no-one-can-log-in/272552 "2023-07-23T13:27:02Z")
**Posts on this page:** 3
**Page:** 2

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [July 24, 2023, 7:25pm UTC](https://meta.discourse.org/t/discourse-went-down-suddenly-no-one-can-log-in/272552/26 "2023-07-24T19:25:10Z")

</div>

Glad to hear it!

> [@WesPenre](#):
>
> Why did this happen in the first place, do you know?

I might make a guess. Presumably according to some instructions, you did this:

> [@WesPenre](#):
>
> ```plaintext
> ./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only
> 
> ```

The meaning of that is to run the bootstrap command, and then - if it is successful - to run the destroy, and then - if that was successful - to run the start. I suspect one of the first two was not successful, and so the start command wasn’t executed.

If you have the transcript for that earlier attempt, that might be informative.

If indeed one of those commands failed, that might indicate that something still needs to be attended to. But at least you are running.

Edit: and yet, I realise now that I have not answered the question, as to why the forum might have gone down in the first place…

---

<div class="post-metadata">

### Author: ![rahim123](https://avatars.discourse-cdn.com/v4/letter/r/df705f/32.png) [@rahim123](https://meta.discourse.org/u/rahim123)
#### Post date: [July 24, 2023, 7:26pm UTC](https://meta.discourse.org/t/discourse-went-down-suddenly-no-one-can-log-in/272552/27 "2023-07-24T19:26:23Z")

</div>

> [@WesPenre](#):
>
> Why did this happen in the first place, do you know?

I would look first at [https://wespenreboards.com/logs](https://wespenreboards.com/logs) and start by focusing on a few entries before the time that it went down. Then try to correlate those log entry times with any out-of-the-ordinary errors in `journalctl --no-pager --since "2023-07-XX" `  
This will help to determine if the Discourse app messed up first or if it went down due to a lower level OS issue.

---

<div class="post-metadata">

### Author: ![WesPenre](https://avatars.discourse-cdn.com/v4/letter/w/4bbf92/32.png) [@WesPenre](https://meta.discourse.org/u/WesPenre)
#### Post date: [July 24, 2023, 7:39pm UTC](https://meta.discourse.org/t/discourse-went-down-suddenly-no-one-can-log-in/272552/28 "2023-07-24T19:39:13Z")

</div>

Thank you!

[Previous page](https://meta.discourse.org/t/discourse-went-down-suddenly-no-one-can-log-in/272552.md?page=1)