I recently upgraded a self-hosted instance of Discourse using the ./launcher rebuild app strategy. The rebuild seemed to work, but Discourse itself failed to respond. Using docker logs app gives the following output: run-parts: executing /etc/runit/1.d/00-ensure-links run-parts: executing /etc/runi…

[изображение] jlc: discourse-multilingual Remove the broken Customization > Plugin Multilingual Plugin 🌐 and rebuild.

As suggested in another topic , I tried restarting the Docker service; now Discourse responds, but hangs at the “bouncing dots” without loading the forum. I’m going to poke around in the Docker image and see if the logs there are more informative, although I’m certainly open to suggestions…

That did it; what a relief! Thanks so much, I forgot that Discourse Multilingual was broken!

Исключение: не удалось инициализировать настройки сайта по умолчанию после обновления

Поддержка Самостоятельное хостинг

Falco (Falco) 13.Апрель.2026 18:47:22 3

Удалите broken Customization > Plugin Multilingual Plugin 🌐 и пересоберите.

Тема		Ответов	Просм.
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	417	10.07.2025
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2164	26.11.2021
Site down after upgrade via SSH - how to fix? Self-hosting	3	588	16.09.2023
Upgrade fail, Site down Support	10	1119	12.03.2019
Latest site upgrade not working Self-hosting	10	1811	22.02.2022

Исключение: не удалось инициализировать настройки сайта по умолчанию после обновления

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