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 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 # /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 ' /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 ` ' /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 ` ' /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 ` ' Spinning up 1 Unicorn worker(s) that were stopped initially

Perhaps have a look at [imagen] Update problem, do I press the big scary red button? Self-hosting 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?

Hélas… 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

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

[imagen] NateDhaliwal: cd /var/discourse Merci, là il travaille. je reviens quand il a fini

Merci beaucoup c’est réparé ! Pour la prochaine fois et pour les autres utilisateurs, comme il semble que ce soit plus efficace de faire les mises à jour en SSH, quelles commandes effectuer quand l’Amin Panel indique une mise à jour de Docker ET une mise à jour de Discourse ? et dans quel ordre procéder ?

A rebuild upgrades both :slight_smile:

Merci ! Donc en résumé cd /var/discourse sudo git pull sudo ./launcher rebuild app

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.

[imagen] Canapin: I don’t think git pull is necessary, a rebuild performs it. :thinking: I don’t think this is universally true. See for example ‘rebuild app’ failed. looks like pnpm problem It’s also very cheap, so I’m not sure it helps to note that it might not be necessary.

[Resuelto] Discourse se bloqueó durante la actualización

Soporte del producto Instalación

NateDhaliwal (Nate Dhaliwal) 3 Marzo, 2026 11:02 4

Primero debes navegar al directorio de discourse con cd /var/discourse.

Tema		Respuestas	Vistas
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	112242	16 Enero 2025
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2482	26 Noviembre 2021
Problem when updating Discourse Forum Self-hosting unsupported-install	20	2674	29 Junio 2023
Cannot upgrade due to old version of docker Self-hosting	4	1731	19 Junio 2018
Sorry, there was an error updating Discourse. Please check the logs below: Docker Manager: FAILED TO UPGRADE Self-hosting	1	299	18 Mayo 2024

[Resuelto] Discourse se bloqueó durante la actualización

Temas relacionados