Hey there! We've found the following might help you get unblocked faster:

• 🧵 single port (the primary PORT) for internal networking ?

• 🧵 Solved: Using public url instead of internal dns

• 🧵 Redis using the private connection

If you find the answer from one of these, please let us know by solving the thread!

PFA. Screenshot of error. We have to switch to public URLs to make it work.

Hey, can you show a snippet of how you are accessing your service via private networking? The service that is being accessed via private networking has to listen on IPv6 and has to be referenced with http://${{service.RAILWAY_PRIVATE_DOMAIN}}:${{service.PORT}}, with service being the service's name.

It's a redis instance and i'm using this URL: `${{queue-kv.REDIS_URL}}`.

If your services are in different projects the internal url will not work, you need to use a public one.

In this case, please check out https://docs.railway.com/reference/errors/enotfound-redis-railway-internal, setting the family option to 0 should solve the problem.

all of my services are in the same project only.

tried this as well but it was not working

Please provide a snippet of your code.

Queue KV:

export const queue_kv = new Redis(`${process.env.REDIS_QUEUE_URL}?family=0`, {
  maxRetriesPerRequest: null,
  enableOfflineQueue: true,
  offlineQueue: true,
});

If you’re using ioredis on Railway with private networking, this config works for me:

export const queue_kv = new Redis(process.env.REDIS_QUEUE_URL, {

family: 0,

maxRetriesPerRequest: null,

enableOfflineQueue: true,

});

let me try this as well!

Hey, did you solve the problem?

kulterryan, it's basically an issue that arises when you try to use the INTERNAL URL (which is meant to be used in Railway environment only) outside of Railway (most probably on your local machine). You can refer to this post to get more hold on this issue: https://station.railway.com/questions/backend-service-unable-to-connect-to-pos-22ad5b8c#kjs0

Do let me know if the helps

Any update, kulterryan