Just noticed that I was due for a discourse update so I performed an update with no issue.
The dashboard notified me that I should disable the footnote plugin and rebuild the app. After doing that, I now get an endless splash screen. (animated dots).
Tried stopping, starting, rebuilding, rebooting … nothing helps. Any thoughts on how to debug / fix would be greatly appreciated.
sudo docker logs app
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 30 Jan 2024 12:27:24 AM UTC] Domains not changed.
[Tue 30 Jan 2024 12:27:24 AM UTC] Skip, Next renewal time is: 2024-03-13T00:35:08Z
[Tue 30 Jan 2024 12:27:24 AM UTC] Add '--force' to force to renew.
[Tue 30 Jan 2024 12:27:24 AM UTC] Installing key to: /shared/ssl/community.acescentral.com.key
[Tue 30 Jan 2024 12:27:24 AM UTC] Installing full chain to: /shared/ssl/community.acescentral.com.cer
[Tue 30 Jan 2024 12:27:24 AM UTC] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Tue 30 Jan 2024 12:27:25 AM UTC] Reload error for :
[Tue 30 Jan 2024 12:27:25 AM UTC] Domains not changed.
[Tue 30 Jan 2024 12:27:25 AM UTC] Skip, Next renewal time is: 2024-03-12T00:35:09Z
[Tue 30 Jan 2024 12:27:25 AM UTC] Add '--force' to force to renew.
[Tue 30 Jan 2024 12:27:25 AM UTC] Installing key to: /shared/ssl/community.acescentral.com_ecc.key
[Tue 30 Jan 2024 12:27:25 AM UTC] Installing full chain to: /shared/ssl/community.acescentral.com_ecc.cer
[Tue 30 Jan 2024 12:27:25 AM UTC] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Tue 30 Jan 2024 12:27:25 AM UTC] Reload error for :
Started runsvdir, PID is 537
ok: run: redis: (pid 549) 0s
ok: run: postgres: (pid 551) 0s
nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /etc/nginx/conf.d/discourse.conf:60
supervisor pid: 548 unicorn pid: 577
I believe that bug should be fixed now, so I don’t think it should be that.
There may be some more detail in your /logs or your browser console that may confirm, but if you’re rebuilding without it then that will answer the question too.
Just in case it’s not, you can also narrow it down by using the different options for safe mode to see if it’s a theme/theme component. And it can also be useful to share a list of your plugins in case anyone can spot one with a known issue.