Postgres stays sleeping – backend can’t connect, was working before
monarchlavatories
HOBBYOP

22 days ago

Hi,

My Postgres service shows as “Sleeping” in the dashboard and does not wake up. This was working fine for weeks so I don't think it is a setup issue.

  • Backend and frontend are both Online; only Postgres is Sleeping.

  • Backend DATABASE_URL is unchanged (still ${{Postgres.DATABASE_URL}})

  • I’ve tried hitting /health/db repeatedly and redeploying Postgres, but after 23 minutes I aborted the redeploy. Still not waking up.

Has anything changed recently for Postgres sleep/wake behavior on hobby plan?

Solved

1 Replies

brody
EMPLOYEE

22 days ago

https://docs.railway.com/deployments/serverless#caveats

Slept services still consume a slot on Railway's infrastructure, enabling Serverless de-prioritizes your workload and in remote cases, may require a rebuild to re-live the service.

Status changed to Awaiting User Response Railway • 22 days ago

Status changed to Solved monarchlavatories • 22 days ago

Loading...