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…

[Bild] 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!

Ausnahme: Initialisierung der Standardseite nach dem Upgrade fehlgeschlagen

Unterstützung Installation

Falco (Falco) 13. April 2026 um 18:47 3

Entferne das defekte #Anpassung:Plugin Multilingual Plugin 🌐 und baue es neu auf.

Thema		Antworten	Aufrufe
An upgrade knocked my site offline; how long until it's restored? Self-hosting	16	352	9. August 2025
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	17	1988	26. November 2021
Site down after upgrade via SSH - how to fix? Self-hosting	4	564	16. Oktober 2023
Upgrade fail, Site down Support	11	1059	11. April 2019
Latest site upgrade not working Self-hosting	11	1774	22. Februar 2022

Ausnahme: Initialisierung der Standardseite nach dem Upgrade fehlgeschlagen

Verwandte Themen