REDIS DATABASE PROBLEM
gadatos
PROOP

5 days ago

I have connection problem witch redis database

[ioredis] Unhandled error event: Error: read ECONNRESET

[ioredis] Unhandled error event: Error: read ECONNRESET

at TCP.onStreamRead (node:internal/stream_base_commons:216:20)
Awaiting User Response

4 Replies

Status changed to Awaiting Railway Response Railway 5 days ago


gadatos
PROOP

5 days ago

my deploument crash, shit hosting


gadatos
PROOP

5 days ago

Does anyone monitor this system at all? Redis is clearly broken and nobody seems to be reacting. Fix it immediately — this is seriously disrupting operations.


gadatos
PROOP

4 days ago

For the last 2 days, I have been experiencing problems with my Redis database and n8n.

The deployment keeps crashing and showing the error: "Deploy Crashed".

Could you please let me know if your company has a support team that can help me resolve this issue????

Registered runner "JS Task Runner" (aCldP-mzGCJz8lgN2D3Z-)

[Redis client] read ECONNRESET

Queue errored

read ECONNRESET

Lost Redis connection. Trying to reconnect in 1s... (0s/10s)

Recovered Redis connection

[Redis client] read ECONNRESET

Lost Redis connection. Trying to reconnect in 1s... (0s/10s)

Recovered Redis connection

[Redis client] read ECONNRESET

Queue errored

read ECONNRESET

Lost Redis connection. Trying to reconnect in 1s... (0s/10s)

Recovered Redis connection

[Redis client] read ECONNRESET

Lost Redis connection. Trying to reconnect in 1s... (0s/10s)

Recovered Redis connection


chandrika
EMPLOYEE

3 days ago

Could you please try redeploy your Redis service in the production environment? It hasn't been redeployed since May 2025, and platform networking updates since then can cause connection resets on long-running database services. A fresh redeploy will restore connectivity. You should also attach an error handler to your ioredis client (e.g. redis.on('error', ...)) so transient connection issues don't crash your process.


Status changed to Awaiting User Response Railway 3 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...