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) 4월 13, 2026, 6:47오후 3

broken Customization > Plugin 태그를 제거하고 Multilingual Plugin 🌐 플러그인을 다시 설치하세요.

글		댓글	조회수
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	536	7월 10, 2025
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2267	11월 26, 2021
Site down after upgrade via SSH - how to fix? Self-hosting	3	620	9월 16, 2023
Upgrade fail, Site down Support	10	1131	3월 12, 2019
Latest site upgrade not working Self-hosting	10	1875	2월 22, 2022

예외: 업그레이드 후 사이트 기본값 초기화 실패

Related topics