a year ago
Error: connect ETIMEDOUT
at Socket.<anonymous> (/app/node_modules/ioredis/built/Redis.js:170:41)
at Object.onceWrapper (node:events:631:28)
at Socket.emit (node:events:517:28)
at Socket._onTimeout (node:net:598:8)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect'
}
Just today I woke up and saw that my RedisBullMQ is failing with my backend which is also deployed. My backend is showing errors that it can't connect to Redis, but my Redis instance is working fine. I thought that maybe the memory was full but I have 32 GB, just in case, I deleted the data that was stored in Redis, did a deploy again and it fixed the problem for 10 seconds, and then it crashed again. Does anyone know what causes this problem?
1 Replies
a year ago
Hello,
Can you please configure your service to connect to Redis via the private network?
You will need this docs page to do that -
https://docs.railway.com/reference/errors/enotfound-redis-railway-internal#using-bullmq
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
7 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 months ago