Update from GUI failed. So I did a commandline update by doing the following: cd /var/discourse ./launcher rebuild app When I try to connect to the site from the browser, I get ‘This site can’t be reached’ error. Thinking that maybe the container has not started, I tried ./launcher start app I get a message saying that the container has already started. I did the following for good measure: ./launcher restart app Still the same problem. The site remains unreachable from browser. I’m not very familiar with docker or discourse. So not even sure where to begin debugging. This is what I get when I do ./launcher logs app x86_64 arch detected. WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml run-parts: executing /etc/runit/1.d/00-fix-var-logs 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 Started runsvdir, PID is 28 ok: run: redis: (pid 40) 0s ok: run: postgres: (pid 36) 0s supervisor pid: 38 unicorn pid: 67 Shutting Down run-parts: executing /etc/runit/3.d/01-nginx ok: down: nginx: 0s, normally up run-parts: executing /etc/runit/3.d/02-unicorn (38) exiting ok: down: unicorn: 0s, normally up run-parts: executing /etc/runit/3.d/10-redis ok: down: redis: 1s, normally up run-parts: executing /etc/runit/3.d/99-postgres ok: down: postgres: 0s, normally up ok: down: cron: 1s, normally up ok: down: nginx: 8s, normally up ok: down: postgres: 1s, normally up ok: down: redis: 8s, normally up ok: down: rsyslog: 0s, normally up ok: down: unicorn: 8s, normally up run-parts: executing /etc/runit/1.d/00-fix-var-logs 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 Started runsvdir, PID is 28 ok: run: redis: (pid 43) 1s ok: run: postgres: (pid 37) 1s supervisor pid: 35 unicorn pid: 67 I would appreciate if somebody could help me get the site up again.

Having trouble getting the site up after update

Vinoth_Deivasigamani (Vinoth) March 26, 2023, 10:55am 2

On a whim, I reran:
./launcher rebuild app

It started working again. I have no idea what went wrong before. But I’m glad it healed.

Topic		Replies	Views
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2484	November 26, 2021
Error while updating discourse installation Self-hosting	9	848	September 13, 2023
Help after updating from ssh site goes down Self-hosting	6	1162	January 30, 2022
Site offline after rebuild (4th Feb 2025) Product Support	16	783	February 6, 2025
Upgrade fail, Site down Product Support	10	1239	March 12, 2019