Intermittent DNS failures on public proxy (EAI_AGAIN errors)
nstaitman
PROOP

4 months ago

Project ID: 4258071a-aa27-4376-a870-e3cf31d1df58

We're experiencing intermittent DNS resolution failures when connecting to Redis and external services through Railway's public proxy infrastructure:

Error: getaddrinfo EAI_AGAIN shortline.proxy.rlwy.net
Error: getaddrinfo EAI_AGAIN shuttle.proxy.rlwy.net

This affects:
- Redis connections (shortline.proxy.rlwy.net:26494)
- External API calls (sheets.googleapis.com)
- PostgreSQL connections

We attempted to use private networking (redis.railway.internal) but discovered it's IPv6-only and doesn't resolve.

Questions:
1. Are there known DNS issues with shortline.proxy.rlwy.net?
2. Can you enable IPv4 private networking for our Redis service?
3. What's the recommended approach for stable DNS resolution?

Timeline: Errors started appearing Nov 13, continuing through Nov 17.

Solved$20 Bounty

8 Replies

Railway
BOT

4 months ago

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

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


4 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open noahd 4 months ago


4 months ago

Hey,

  1. We're not aware of any DNS issues.

  2. Unfortunately, IPv4 support is only available for newly created environments at this time. If possible, you could create a new environment and migrate your data there.

  3. The DNS resolution should be stable.

Can I know why you can't use the private networking? If you're using IORedis (NodeJS) please see the docs for the setup on it: https://docs.railway.com/guides/private-networking#ioredis


Status changed to Awaiting User Response Railway 4 months ago


Railway
BOT

3 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 3 months ago


passos

Hey,We're not aware of any DNS issues.Unfortunately, IPv4 support is only available for newly created environments at this time. If possible, you could create a new environment and migrate your data there.The DNS resolution should be stable.Can I know why you can't use the private networking? If you're using IORedis (NodeJS) please see the docs for the setup on it: https://docs.railway.com/guides/private-networking#ioredis

nstaitman
PROOP

3 months ago

When I connect through the private url the containers are crashing.

[Redis client] getaddrinfo ENOTFOUND redis.railway.internal
[Redis client] getaddrinfo ENOTFOUND redis


Status changed to Awaiting Conductor Response Railway 3 months ago


nstaitman

When I connect through the private url the containers are crashing. [Redis client] getaddrinfo ENOTFOUND redis.railway.internal[Redis client] getaddrinfo ENOTFOUND redis

3 months ago

Hey, have you added ?family=0 to your Redis connection string when connecting over private networking? This is required when your environment is still IPv6 only for private networking.


Status changed to Awaiting User Response Railway 3 months ago


nstaitman
PROOP

3 months ago

I have added ?family=0 and the server is still crashing. The issue isn't IPv4 vs IPv6 — we're getting ENOTFOUND redis.railway.internal which means DNS resolution is failing entirely. We've confirmed both services are in the same project. Is there something that needs to be enabled for private DNS to work, or is this an older environment that doesn't support private networking?


Status changed to Awaiting Conductor Response Railway 3 months ago


nstaitman

I have added ?family=0 and the server is still crashing. The issue isn't IPv4 vs IPv6 — we're getting ENOTFOUND redis.railway.internal which means DNS resolution is failing entirely. We've confirmed both services are in the same project. Is there something that needs to be enabled for private DNS to work, or is this an older environment that doesn't support private networking?

3 months ago

Hey, no this shouldn't be the case. Have you tried explicitly passing the family argument? Can you share a screenshot of your dashboard and your Redis's networking settings?


Status changed to Awaiting User Response Railway 3 months ago


nstaitman
PROOP

3 months ago

I had the family argument in the environment variables for n8n + workers = 0 when it crashed.

QUEUE_BULL_REDIS_HOST="redis.railway.internal"

QUEUE_BULL_REDIS_PORT="6379"

QUEUE_BULL_REDIS_PASSWORD=""

QUEUE_BULL_REDIS_FAMILY="0"


Status changed to Awaiting Conductor Response Railway 3 months ago


nstaitman

I had the family argument in the environment variables for n8n + workers = 0 when it crashed.QUEUE_BULL_REDIS_HOST="redis.railway.internal"QUEUE_BULL_REDIS_PORT="6379"QUEUE_BULL_REDIS_PASSWORD=""QUEUE_BULL_REDIS_FAMILY="0"

3 months ago

Hey, please don't hardcode the values when reference variables are available. Furthermore, have you tried to specify the dualstack service variable? Please take this configuration from one of the n8n templates on Railway as a reference.

Attachments


Status changed to Awaiting User Response Railway 3 months ago


Railway
BOT

3 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 3 months ago


Loading...