a year ago
I'm experiencing the ENOTFOUND redis.railway.internal error in my Node.js application, which uses both direct ioredis connections AND Bull queues (not BullMQ). I've followed the documentation for both:
For ioredis:
const redis = new Redis(process.env.REDIS_URL + '?family=0');For Bull (I assumed it would be handled the same way as BullMQ)
const redisURL = new URL(process.env.REDIS_URL!);
queue = new Bull(name, {
redis: {
family: 0,
host: redisURL.hostname,
port: parseInt(redisURL.port || '6379'),
username: redisURL.username || 'default',
password: redisURL.password
}
});(Ref: https://docs.railway.com/reference/errors/enotfound-redis-railway-internal)
However, I'm still getting the same DNS resolution errors. The docs only show examples for BullMQ - is there a different configuration required for Bull specifically? Or is there something else I should check?
Thank you
3 Replies
a year ago
Hello,
What version of Bull are you using? I don't think it uses ioredis, but the Bull version might be old enough to outright not support IPv6 since the private network is IPv6 only.
May be best to switch to bullmq with family 0.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
We switched to bullmq and it solved it. Thanks for the help.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Awesome, yeah from my understanding Bull is unmaintained and likely very outdated.
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved brody • about 1 year ago