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…

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

Exception: Failed to initialize site default after upgrade

Support Self-hosting

Falco (Falco) April 13, 2026, 6:47pm 3

Remove the broken Customization > Plugin Multilingual Plugin 🌐 and rebuild.

Topic		Replies	Views
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	383	July 10, 2025
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2061	November 26, 2021
Site down after upgrade via SSH - how to fix? Self-hosting	3	577	September 16, 2023
Upgrade fail, Site down Support	10	1100	March 12, 2019
Latest site upgrade not working Self-hosting	10	1791	February 22, 2022

Exception: Failed to initialize site default after upgrade

Related topics