Hello,

It looks like your application crashed because it was unable to communicate with Redis over the public network. Please switch it to the private network.

Hi again,
Thanks for your response @brody.

I’m seeing Private Networking DNS issues for Redis in a single project/environment.

Setup:

- Environment: Production

- Region: Amsterdam (both services)

- Services: Next.js app + Railway Redis

- Postgres internal DNS works: postgres.railway.internal resolves and connects.

- Redis internal DNS does NOT resolve from the app container.

What I tried:

- Using REDIS_URL with internal host shown in Redis → Settings → Networking → Private Networking:

redis://default:<pass>@redis.railway.internal:6379

- Also tried host "redis" (service name) and "redis.railway.internal" directly.

Result:

- App logs: getaddrinfo ENOTFOUND redis.railway.internal (or ENOTFOUND redis)

- Redis is online and reachable via public TCP proxy domain.

- Both services are in same project + same env + same region.

Question:

Is there any known limitation/setting for Redis private DNS on hobby plan, or any required naming convention?

Can you confirm whether redis.railway.internal should resolve from other services in the same project/environment, and if not, what the correct internal hostname should be?

I don't know why but look like the driver networking DNS isn't solvable with just changing it to "redis.railway.internal" so that's why we stay with the public domain.

Thanks!

Have a look at this - https://docs.railway.com/networking/private-networking/library-configuration#ioredis

solved - thanks a lot!