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) 2026 年 4 月 13 日午後 6:47 3

broken Customization > Plugin Multilingual Plugin 🌐 を削除し、再構築してください。

「いいね！」 3

トピック		返信	表示
An upgrade knocked my site offline; how long until it's restored? Self-hosting	16	348	2025 年 8 月 9 日
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	17	1986	2021 年 11 月 26 日
Site down after upgrade via SSH - how to fix? Self-hosting	4	564	2023 年 10 月 16 日
Upgrade fail, Site down Support	11	1059	2019 年 4 月 11 日
Latest site upgrade not working Self-hosting	11	1771	2022 年 2 月 22 日

例外：アップグレード後のサイトデフォルトの初期化に失敗しました

関連トピック