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? [изображение] 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 operati…

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 сломан после неудачного обновления

Поддержка

Adam_Price (Adam Price) 02.Ноябрь.2024 00:31:58 5

Спасибо всем — обновление через командную строку и увеличение размера виртуального диска помогли.

Мы снова в сети, версия 3.4.

Фух.

Тема		Ответов	Просм.
Failed upgrade from 2.9.0.beta14 to 3.1.0.beta Self-hosting	10	1306	25.01.2023
Problems with self-hosted upgrade to 3.x: cannot roll back Self-hosting	14	1374	28.01.2023
Sorry, there was an error updating Discourse. Please check the logs below: Docker Manager: FAILED TO UPGRADE Self-hosting	1	282	18.05.2024
Failed to upgrade 3.1.0 Beta7 to 3.2.0 Beta3 as of 12/31/2023 Self-hosting	4	581	01.01.2024
Error when upgrading Discourse Self-hosting	11	554	12.05.2025

Discourse сломан после неудачного обновления

Связанные темы