a month ago
Hello -
Project zooming-vitality, production, sfo. Postgres unreachable since ~16:53 UTC 2026-06-04. [paste the three symptoms + "already tried" + "not a resource issue: 68% disk, 41% mem" from the ticket]. CLI restart rejected as "not restartable", redeploys fail/stick, backboard API also timing out. Is this a known sfo incident? How do I force the container to boot — is there a way short of redeploying that I'm missing? Thank you
1 Replies
a month ago
Your Postgres volume is intact and in READY state (~66% used), so your data is safe. The latest deployment is in a torn-down state, which explains why normal redeploys and restarts aren't working. Open the Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" - this re-pulls a fresh container image and typically resolves stuck database services where standard redeploys fail.
Status changed to Awaiting User Response Railway • about 1 month ago
25 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 25 days ago