2 months ago
My Railway Postgres service shows ACTIVE/SUCCESS, but Railway cannot reach the container. Database UI spins on connecting, Console says “An error occurred connecting to your service,” and restarting returns “Problem processing request.” A redeploy was stuck at “Creating containers” for 19 minutes and was aborted. Both dependent services fail with Prisma P1001 to postgres.railway.internal:5432; Postgres logs show repeated SSL EOF/reset errors. The volume still exists and must not be detached/deleted. Is there an incident or a safe way to restore the service/container attachment?
3 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Yes, this is an incident on our side, not anything with your setup. One of our servers hit a hardware fault and went offline, which is why your Postgres is unreachable and the redeploy hung at creating containers. Your volume and its data are safe and persist through this, so there's nothing you need to change or risk on your end. We're moving the workload onto a healthy machine and are actively on it.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
The reattach is fully complete and it is safe to resume use now. No data has been affected. There is unfortunately a small risk of 2-5 mins downtime in the next 24h as we drain the stacker completely to prevent recurrence. My apologies for this.
2 months ago
That is fine. Thanks guys it seems to work fine again.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved Railway • about 2 months ago