개인 플러그인 설치 후 앱이 다시 온라인으로 돌아오지 않음

최근 Discourse 인스턴스에 사설 플러그인을 설치하려고 시도했습니다. Docker를 재시작한 후 서비스가 다시 온라인으로 돌아오지 않았습니다. 여러 번 시도한 결과 다음과 같은 로그가 표시됩니다:

root@discourse:/var/discourse# docker container logs d6aa2ac484b9
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/01-cleanup-web-pids
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
run-parts: executing /etc/runit/1.d/letsencrypt
[Tue Feb 4 07:23:08 PM UTC 2025] Domains not changed.
[Tue Feb 4 07:23:08 PM UTC 2025] Skip, Next renewal time is: 2025-03-17T17:22:01Z
[Tue Feb 4 07:23:08 PM UTC 2025] Add '--force' to force to renew.
[Tue Feb 4 07:23:09 PM UTC 2025] Installing key to: /shared/ssl/forum.get.it.key
[Tue Feb 4 07:23:09 PM UTC 2025] Installing full chain to: /shared/ssl/forum.get.it.cer
[Tue Feb 4 07:23:09 PM UTC 2025] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Tue Feb 4 07:23:09 PM UTC 2025] Reload error for :
[Tue Feb 4 07:23:10 PM UTC 2025] Domains not changed.
[Tue Feb 4 07:23:10 PM UTC 2025] Skip, Next renewal time is: 2025-03-17T17:22:09Z
[Tue Feb 4 07:23:10 PM UTC 2025] Add '--force' to force to renew.
[Tue Feb 4 07:23:11 PM UTC 2025] Installing key to: /shared/ssl/forum.get.it_ecc.key
[Tue Feb 4 07:23:11 PM UTC 2025] Installing full chain to: /shared/ssl/forum.get.it_ecc.cer
[Tue Feb 4 07:23:11 PM UTC 2025] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Tue Feb 4 07:23:12 PM UTC 2025] Reload error for :
Started runsvdir, PID is 534
ok: run: redis: (pid 548) 0s
ok: run: postgres: (pid 544) 0s
nginx: [warn] duplicate extension "wasm", content type: "application/wasm", previous content type: "application/wasm" in /etc/nginx/conf.d/discourse.conf:4
supervisor pid: 547 unicorn pid: 574

…앱을 다시 온라인으로 복구하기 위해 시도한 다른 방법들:

  • 앱 재빌드 (Rebuild the app)
  • ./launcher cleanup 명령을 사용하여 Docker 캐시 정리

이 문제를 경험해 보신 분이나 올바른 해결 방향을 알려주실 수 있는 분이 계시다면 감사하겠습니다.

안녕하세요 @Jacob_Peebles - 가장 가능성 높은 원인은 Site offline after rebuild (4th Feb 2025) - #7 by david 입니다. 다시 리빌드를 실행하면 훨씬 더 잘 작동할 것입니다. 불편을 드려 죄송합니다!

@david 감사합니다. 시도해 보고 결과를 알려드리겠습니다.

@david 님, 작동했습니다!