9 months ago
My deployed service (cafe-cms) is linked to a Redis plugin in Railway.
However, even though REDIS_URL is set to the internal address (redis://default:<password>@redis.railway.internal:6379), the service fails to connect with the following error:
> Error: getaddrinfo ENOTFOUND redis.railway.internal
I confirmed the plugin is linked correctly (it shows in the visual diagram), and I can use the same REDIS_URL with the public proxy successfully.
I also created a /ping-redis endpoint inside the deployed app that directly tries to connect — and it fails with the same ENOTFOUND error.
This indicates internal DNS resolution for redis.railway.internal is broken inside the deployment, even though the service is linked.
Please help resolve this or advise if there's a known networking issue.
2 Replies
9 months ago
Hey, most likely your service and Redis plugin aren't actually running in the same Railway environment or project, so the internal DNS redis.railway.internal can't resolve. Double-check that both are linked in the exact same environment. Also make sure you're not overriding the REDIS_URL env var with something else.
In case you are 100% sure they are correctly linked and on the same environment (prod/dev/etc) and project, check if you have any custom DNS settings messing it up, in case everything is checked and there's still a problem, then, even though unlikely, I assume it's a problem on Railway's side, which you can contact them at team@railway.com
6 months ago
Have you checked this page of the documentation? https://docs.railway.com/reference/errors/enotfound-redis-railway-internal