# Error 500 how to fix?

**URL:** https://meta.discourse.org/t/error-500-how-to-fix/308264
**Category:** Self-hosting
**Created:** [May 16, 2024, 1:15pm UTC](https://meta.discourse.org/t/error-500-how-to-fix/308264 "2024-05-16T13:15:09Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Abbas\_Muhammad](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/abbas_muhammad/32/380378_2.png) [@Abbas\_Muhammad](https://meta.discourse.org/u/Abbas_Muhammad)
#### Post date: [May 16, 2024, 1:15pm UTC](https://meta.discourse.org/t/error-500-how-to-fix/308264/1 "2024-05-16T13:15:09Z")

</div>

```plaintext
Docker Manager: FAILED TO UPGRADE
#<RuntimeError: RuntimeError>
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:210:in `run'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:101: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.2.0/gems/railties-7.0.8.1/lib/rails/commands/runner/runner_command.rb:43:in `load'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/commands/runner/runner_command.rb:43:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.1/lib/thor/command.rb:28:in `run'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.1/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.1/lib/thor.rb:527:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/command/base.rb:87:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/command.rb:48:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/commands.rb:18:in `<main>'
<internal:/usr/local/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
<internal:/usr/local/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:18:in `<main>'
Spinning up 3 Unicorn worker(s) that were stopped initially

```

i got this error, how do i fix it?

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [May 16, 2024, 1:21pm UTC](https://meta.discourse.org/t/error-500-how-to-fix/308264/2 "2024-05-16T13:21:21Z")

</div>

Are you doing a `.launcher rebuild app` from the command line, or updating from the UI? If the latter, could you try the former?

---

<div class="post-metadata">

### Author: ![Abbas\_Muhammad](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/abbas_muhammad/32/380378_2.png) [@Abbas\_Muhammad](https://meta.discourse.org/u/Abbas_Muhammad)
#### Post date: [May 16, 2024, 1:22pm UTC](https://meta.discourse.org/t/error-500-how-to-fix/308264/3 "2024-05-16T13:22:18Z")

</div>

I just update the discorse from settings ☹ not from the command line

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [May 16, 2024, 1:23pm UTC](https://meta.discourse.org/t/error-500-how-to-fix/308264/4 "2024-05-16T13:23:18Z")

</div>

I think a manual rebuild should sort you out. 🤞

> [@Manually update Discourse and Docker image to latest](https://meta.discourse.org/t/manually-update-discourse-and-docker-image-to-latest/23325):
>
> bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docker container, and the Ubuntu operating system on a self-hosted setup. person_raising_hand Required user level: System Administrator warning SSH access to the server. If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases and newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occa…

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [May 17, 2024, 11:56am UTC](https://meta.discourse.org/t/error-500-how-to-fix/308264/5 "2024-05-17T11:56:31Z")

</div>

It looks like it’s not possible to do this upgrade from the UI and that Discourse\_docker should not attempt to do an upgrade. I’ve at two sites that broke doing the upgrade and this is at least the second one I’ve seen here since the latest release.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [May 17, 2024, 12:20pm UTC](https://meta.discourse.org/t/error-500-how-to-fix/308264/6 "2024-05-17T12:20:48Z")

</div>

I think David has added a message now:

> [@3.3.0.beta2-dev update error](https://meta.discourse.org/t/3-3-0-beta2-dev-update-error/308163/8):
>
> Thanks for the reports! A command line rebuild is indeed the best solution. I’ve prepared [this fix](https://github.com/discourse/docker_manager/pull/215) which will cause a message to be shown to people before they hit ‘update’ in the UI. Edit: now merged