cbaa8f69-2dcf-43d0-88bd-bc8dc65eb24f

The error you can see is triggered from here:

private setupQueueEvents() {
    this.verificationQueue
      .on('completed', (job) => {
        if ('type' in job.data && job.data.type === 'periodic') {
          console.log('Periodic verification completed');
        } else {
          console.log(`Job ${job.id} completed for user ${(job.data as VerificationJob).userId}`);
        }
      })
      .on('failed', (job, error) => {
        console.error(`Job ${job?.id} failed:`, error);
      })
      .on('error', (error) => {
        console.error('Queue error:', error);
      })
      .on('stalled', (job) => {
        console.warn(`Job ${job?.id} stalled`);
      });
  }

Which means the redis connection is successful when instantiating at the top of the class

have you seen these docs? -

Yes those docs do not help at all

to be honest

My issue is not the Redis connection URL

this.verificationQueue = new Queue('verification', {
redis: {
port: process.env.REDISPORT ? parseInt(process.env.REDISPORT) : 6379,
host: process.env.REDISHOST || 'localhost',
username: process.env.REDISUSER,
password: process.env.REDISPASSWORD,
lazyConnect: true,
},

These configurations do not work with the private network hostname

i already have the family=0 and its fine, but bullmq specifically cannot connect to the internal network hostname:

this.redis = new Redis(process.env.REDIS_URL! + '?family=0', {
maxRetriesPerRequest: null,
enableReadyCheck: false,
});

is redis in the same project?

Yea

I confirmed locally using the public url, code is working fine, internal url doesnt do anything but throw errors. Is there any other private networking i need to setup?

are you trying to connect during build?

Nope, just on startup

i added the sleep 3 also

Ive gone through all the issues related to this nothing seems to work. Should I wipe redis and recreate it or something?

nope, you need to set family to 6

i can try that

still doesnt really affect how the hostname is used tho

yes it does

I'd recommend looking into what the family parameter represents

but im not using the connection string directly for instantiating bullmq queues, you only get to set the host, user pass and port. Ill try 6, but the docs say 0

6 or 0 doesn't matter when on railway

still doesnt change anything

are you useing a very old version of bullmq?

5.34.2

thats the latest, then you arent passing in family 0 / 6 correctly

redis://default:password@redis.railway.internal:6379?family=6

is not right?

maybe bullmq does not respect query params

should family query param be on the host name? I mean theres literally no where in the docs I see you pass in a connection string:

https://docs.bullmq.io/guide/connections

might be a family param we can pass in, looking

const redisUrl = new URL(process.env.REDIS_URL! + '?family=6');

    const redisConfig = {
      port: parseInt(redisUrl.port),
      host: redisUrl.hostname,
      username: redisUrl.username || 'default',
      password: redisUrl.password,
      maxRetriesPerRequest: null,
      enableReadyCheck: false,
      family: 6
    };

    // Initialize Redis connection
    this.redis = new Redis(redisConfig);

    // Initialize Queue
    this.verificationQueue = new Queue('verification', {
      connection: redisConfig,
      defaultJobOptions: {
        attempts: 3,
        backoff: {
          type: 'exponential',
          delay: 1000,
        },
        removeOnComplete: true
      },
    });

Im sure the env vars work just fine now, but this is working. Might be worth adding a section to the docs about adding the family in the config. This isnt fully typed but bullmq doesnt use conn strings so its a bit confusing

good point, ill add a bullmq section under the ioredis section

but im glad you got it solved!

please excuse my frustration lol

thanks for the quick reply

no worries, im frustrated with ioredis too

😭

can't imagine why the devs thought it was a good idea to do an IPv4 only dns lookup

with the amount of help questions asking the same thing over an over i can imagine

Yea must be outdated devs

they forgor about IPv6

we now how a section in our docs for bullmq! -

!s