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…

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

Excepción: Error al inicializar el sitio predeterminado después de la actualización

Soporte Instalación

Falco (Falco) 13 Abril, 2026 18:47 3

Elimina la #rotura #personalización:plugin Multilingual Plugin 🌐 y vuelve a compilar.

3 Me gusta

Tema		Respuestas	Vistas
An upgrade knocked my site offline; how long until it's restored? Self-hosting	16	348	9 Agosto 2025
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	17	1986	26 Noviembre 2021
Site down after upgrade via SSH - how to fix? Self-hosting	4	564	16 Octubre 2023
Upgrade fail, Site down Support	11	1059	11 Abril 2019
Latest site upgrade not working Self-hosting	11	1771	22 Febrero 2022

Excepción: Error al inicializar el sitio predeterminado después de la actualización

Temas relacionados