# \[Solved\] Discourse crashed during update

**URL:** https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520
**Category:** Self-hosting
**Created:** [March 3, 2026, 10:46am UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520 "2026-03-03T10:46:30Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![vin100](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vin100](https://meta.discourse.org/u/vin100)
#### Post date: [March 3, 2026, 10:46am UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/1 "2026-03-03T10:46:30Z")

</div>

I don’t undestand what’s happend and what to do.

My Discourse crashed when I did the last update.

Any help would be very appreciated

```plaintext
Waiting for Unicorn to reload...............
Stopping 1 Unicorn worker(s), to free up memory
$ cd /var/www/discourse && git fetch --tags --prune-tags --prune --force
$ cd /var/www/discourse && git reset --hard
HEAD is now at 44bf7b363ac I18N: Update translations (#37404)
$ cd /var/www/discourse && git -c advice.detachedHead=false checkout beta
Previous HEAD position was 44bf7b363ac I18N: Update translations (#37404)
HEAD is now at f863bbf1553 Revert "FIX: Add server-side trust level check for delete all posts (… [backport 2026.2] (#38095)
$ bundle install --retry 3 --jobs 4
Your Ruby version is 3.3.8, but your Gemfile specified ~> 3.4
Docker Manager: FAILED TO UPGRADE
#<RuntimeError: RuntimeError>
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:205:in `run'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:94:in `upgrade'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in <main>'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `fork'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/commands/runner/runner_command.rb:44:in `load'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/commands/runner/runner_command.rb:44:in `block in perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/execution_wrapper.rb:91:in `wrap'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/commands/runner/runner_command.rb:70:in `conditional_executor'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/commands/runner/runner_command.rb:43:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor/command.rb:28:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/command/base.rb:178:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor.rb:538:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/command/base.rb:73:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/command.rb:65:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/command.rb:143:in `with_argv'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/command.rb:63:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.4/lib/rails/commands.rb:18:in `<main>'
/usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `require'
/usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `block (2 levels) in replace_require'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.19.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:18:in `<main>'
Spinning up 1 Unicorn worker(s) that were stopped initially

```

---

<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: [March 3, 2026, 10:57am UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/2 "2026-03-03T10:57:14Z")

</div>

Perhaps have a look at

> [@Update problem, do I press the big scary red button?](https://meta.discourse.org/t/update-problem-do-i-press-the-big-scary-red-button/396452/3):
>
> this doesn’t sound very promising: Your Ruby version is 3.3.8, but your Gemfile specified ~\> 3.4 Docker Manager: FAILED TO UPGRADE I tried ask.discourse after posting and it suggests doing a full rebuild: sudo git pull sudo ./launcher rebuild app yay or nay?

---

<div class="post-metadata">

### Author: ![vin100](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vin100](https://meta.discourse.org/u/vin100)
#### Post date: [March 3, 2026, 11:00am UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/3 "2026-03-03T11:00:08Z")

</div>

Alas…

```plaintext
root@forum:~# sudo git pull
sudo ./launcher rebuild app
fatal: not a git repository (or any of the parent directories): .git
sudo: ./launcher: command not found

```

---

<div class="post-metadata">

### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [March 3, 2026, 11:02am UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/4 "2026-03-03T11:02:47Z")

</div>

You should navigate to the discourse directory first with `cd /var/discourse`.

---

<div class="post-metadata">

### Author: ![vin100](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vin100](https://meta.discourse.org/u/vin100)
#### Post date: [March 3, 2026, 11:04am UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/5 "2026-03-03T11:04:19Z")

</div>

> [@NateDhaliwal](#):
>
> cd /var/discourse

Thanks, it’s working now. I’ll get back to you when it’s finished.

---

<div class="post-metadata">

### Author: ![vin100](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vin100](https://meta.discourse.org/u/vin100)
#### Post date: [March 3, 2026, 11:59am UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/6 "2026-03-03T11:59:23Z")

</div>

Thank you very much, it’s fixed!

For next time and for other users, since it seems more efficient to perform updates via SSH, what commands should be executed when the Admin Panel indicates a Docker update AND a Discourse update? And in what order should we proceed?

---

<div class="post-metadata">

### Author: ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [March 3, 2026, 12:22pm UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/7 "2026-03-03T12:22:25Z")

</div>

A rebuild upgrades both 🙂

---

<div class="post-metadata">

### Author: ![vin100](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vin100](https://meta.discourse.org/u/vin100)
#### Post date: [March 3, 2026, 12:25pm UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/8 "2026-03-03T12:25:13Z")

</div>

Thanks! So in summary

```plaintext
cd /var/discourse
sudo git pull
sudo ./launcher rebuild app

```

---

<div class="post-metadata">

### Author: ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [March 3, 2026, 12:27pm UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/9 "2026-03-03T12:27:47Z")

</div>

~~I don’t think `git pull` is necessary, a rebuild performs it.~~ edit: see ed’s post below

`sudo` isn’t required if you are logged in as root.

You can also run it as a single command: `/var/discourse/launcher rebuild app`.

---

<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: [March 4, 2026, 4:05pm UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/10 "2026-03-04T16:05:08Z")

</div>

> [@Canapin](#):
>
> I don’t think `git pull` is necessary, a rebuild performs it. 🤔

I don’t think this is universally true. See for example  
[‘rebuild app’ failed. looks like pnpm problem](https://meta.discourse.org/t/rebuild-app-failed-looks-like-pnpm-problem/397610)

It’s also very cheap, so I’m not sure it helps to note that it might not be necessary.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [April 3, 2026, 4:05pm UTC](https://meta.discourse.org/t/solved-discourse-crashed-during-update/397520/11 "2026-04-03T16:05:51Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
