a month ago
My project has two Postgres services, and BOTH are crashing:
-
Original Postgres (ID: 52c164ba-aadc-40e1-bbc4-77704794b702)
- Crashed at 19:50:54 UTC
- No error logs before crash
- Has attached volume
-
New Postgres-JpER (ID: f6f4c73a-a811-4128-b4d9-f6f7902c509e)
- Just provisioned, also crashes on startup
- Same silent failure pattern
Backend (rrn-api) deployment fails with:
"PrismaClientInitializationError P1001: Can't reach database server at postgres.railway.internal:5432"
This is NOT a resource limit issue:
- Usage: $1.85 (under $5 credit limit)
- Volume: 0.4 GB average (under 5 GB cap)
The fact that a FRESH Postgres instance also crashes suggests a platform-level networking or container issue, not data corruption.
Project: RRN (21bee5a2-610c-4623-a94c-61ac926299de)
Environment: production (af3f70b2-0f57-4d62-951e-259ddb03731e)
3 Replies
Status changed to Awaiting Railway Response Railway • 26 days ago
25 days ago
Hello , waited all day is anyone home
25 days ago
It looks like the railway up command was run targeting your PostgreSQL service, which replaced the database image with your application code. That's why the original Postgres is crashing and your backend can't connect - it's no longer running PostgreSQL. To fix this, you'll need to reconfigure that service back to the PostgreSQL image and ensure your other services point to it correctly.
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 25 days ago
25 days ago
Change your service source image to ghcr.io/railwayapp-templates/postgres-ssl:18 and Deploy
This will replace the running image with postgres image back