Skip to content
Redis and PostgreSQL unexpectedly sleeping despite Serverless being disabled
wearesparklab
OP

4 hours ago

Hi Railway Support,

I'm running a self-hosted n8n installation on a Hobby workspace, using four services: Primary, Worker, PostgreSQL and Redis.

My n8n services repeatedly crash after losing their PostgreSQL and Redis connections.

Railway's activity history shows that both PostgreSQL and Redis repeatedly go to sleep and resume, even though Serverless/Sleep is disabled for both services.

On 15 November 2026, around 04:34–04:35 UTC:

  • Redis received a SIGTERM shutdown signal.
  • PostgreSQL restarted and performed recovery.
  • n8n reported Redis connection timeouts and PostgreSQL connection failures.
  • The n8n Worker exited because it could not reconnect to Redis.

CPU and memory usage appear low, and my Hobby workspace has not exhausted its included usage credits.

Project: intelligent-spontaneity

Could you please investigate why these services are going to sleep despite the setting being disabled, and whether this is related to Railway's infrastructure or another account-level configuration?

I'd appreciate guidance on resolving this without losing my existing n8n workflows or database data.

Thank you!

Awaiting User Response

1 Reply

Railway
BOT

4 hours ago

Your Postgres and Redis services are both currently sleeping on deployments created on 19 October 2026, while their settings now show Serverless disabled. Serverless takes effect when a deployment creates its container, so a running container keeps the setting it was created with until the service is redeployed, which is consistent with what you are seeing.

Redeploying Postgres first and then Redis will create new containers with the current setting. Both have a persistent volume attached, which is where their data lives, so your n8n workflows and database data remain on those volumes across the redeploy. Once both are running, redeploy Primary and Worker so they reconnect.


Status changed to Awaiting User Response Railway • about 4 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...