Redis service crashing suddenly after months of stable usage with n8n
benjaflow
PROOP

6 months ago

Description:
Hello, I have been running an n8n project on Railway for about 4 months without issues. Suddenly, my Redis service started crashing and the project no longer works.

Details:

  • Service: Redis (used as queue for n8n with EXECUTIONS_MODE=queue)

  • Postgres is configured and working fine

  • Redis was running stable until a few days ago, no changes were made

  • After redeploy, service still crashes and shows CRASHED in Railway dashboard

  • Logs only show that the Redis connection fails or is not reachable

Environment Variables (without secrets):

DB_TYPE="postgresdb"
DB_POSTGRESDB_HOST="${{Postgres.PGHOST}}"
DB_POSTGRESDB_PORT="${{Postgres.PGPORT}}"
DB_POSTGRESDB_USER="${{Postgres.POSTGRES_USER}}"
DB_POSTGRESDB_PASSWORD="${{Postgres.POSTGRES_PASSWORD}}"
DB_POSTGRESDB_DATABASE="${{Postgres.POSTGRES_DB}}"

EXECUTIONS_MODE="queue"
QUEUE_BULL_REDIS_HOST="${{Redis.REDISHOST}}"
QUEUE_BULL_REDIS_PORT="${{Redis.REDISPORT}}"
QUEUE_BULL_REDIS_USERNAME="${{Redis.REDISUSER}}"
QUEUE_BULL_REDIS_PASSWORD="${{Redis.REDIS_PASSWORD}}"

Problem:

  • Redis service shows as CRASHED in production

  • n8n can’t connect to Redis anymore (getaddrinfo ENOTFOUND or connection refused errors)

  • Even after redeploy, the crash persists

Question:
Could this be related to a recent Railway change, Redis config update, or do I need to adjust my variables?
Any guidance would be really helpful pray emoji

$10 Bounty

3 Replies

Railway
BOT

6 months ago


idiegea21
HOBBY

5 months ago

Heyy,

the info here isn’t enough to know why the redis container crashed. Could you share the Redis logs from the Railway dashboard? They should show if it’s running out of memory, hitting a config issue, or something else. That’ll make it easier to see what’s causing the crash.


5 months ago

Hey, please try redeploying your application and Redis service. If all of this doesn't work, you may try enabling IPv4 private networks and see if this solves the the issue (IPv4 private networks are currently behind a feature flag as of right now https://railway.com/account/feature-flags).


Loading...