I did a bad thing. I inherited a discourse server for my organization. For months now, every time I log in, it has told me there are critical updates that must be installed (3.2.x → 3.3.x). I finally caved, and clicked on the updates in the admin panel. The docker update was fine - that finished…

Have you tried upgrading from the command line? [image] Manually update Discourse and Docker image to latest Self-Hosting bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docker container, and the Ubuntu operating sys…

Can you please try a rebuild on the command line?

As suggested. Every now and then you will want to perform a command line update. Especially when the web interface fails. Most of the time a command line updates will resolve an update issue from the dashboard

Thanks everyone - a command line update and an increase in the virtual disk size did the trick. We’re back online, with 3.4. Phew.

Discourse cassé après une mise à jour échouée

Soutien

Adam_Price (Adam Price) Novembre 2, 2024, 12:31 5

Merci à tous - une mise à jour de la ligne de commande et une augmentation de la taille du disque virtuel ont fait l’affaire.

Nous sommes de retour en ligne, avec la version 3.4.

Ouf.

Sujet		Réponses	Vues
Failed upgrade from 2.9.0.beta14 to 3.1.0.beta Self-hosting	10	1306	Janvier 25, 2023
Problems with self-hosted upgrade to 3.x: cannot roll back Self-hosting	14	1374	Janvier 28, 2023
Sorry, there was an error updating Discourse. Please check the logs below: Docker Manager: FAILED TO UPGRADE Self-hosting	1	282	Mai 18, 2024
Failed to upgrade 3.1.0 Beta7 to 3.2.0 Beta3 as of 12/31/2023 Self-hosting	4	581	Janvier 1, 2024
Error when upgrading Discourse Self-hosting	11	554	Mai 12, 2025

Discourse cassé après une mise à jour échouée

Sujets connexes