a month ago
Hobby plan. Hardware failure yesterday at 14:39 UTC took Postgres down. Railway support confirmed volume in READY state ~5 hours later, but Postgres has not been functional since:
TablePlus connection to public proxy succeeds initially, then drops when querying
Backend service cannot connect at all (timeouts on internal network)
Backend redeploy fails at alembic migration step due to no DB connectivity
Pre-launch app, no backups (Hobby tier). Considering Postgres redeploy but concerned about volume reattach issues seen in recent bounty threads. Has anyone seen this pattern resolve, or is rebuild the only path?
Support ticket already open, no engineer response yet.
1 Replies
a month ago
Your Postgres volume is in READY state with ~216MB of data intact, but the Postgres process has not produced any logs since the volume was remounted at 14:39 UTC on June 3. This means Postgres itself is not starting, which explains both the public proxy drops and the backend connection timeouts. Redeploying the Postgres service from the three-dot menu on the service card is safe here since the volume is attached and in READY state, so your data will persist through the redeploy. If Postgres still does not start after a redeploy, check the new deployment's logs for any startup errors.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 26 days ago