3 months ago
I have a web app in NodeJS that is connecting to Redis DB in railway. I have provided the REDISHOST, REDISPORT, REDISUSER and REDISPASSWORD to the app. They are received properly as well. Then I use ioredis package to connect to redis and read/write values. This setup worked fine until today. All of a sudden I'm not able to access the Redis DB from my app. All requests to the DB are timing out. I can see that the DB is up in railway. I'm also able to access the DB via the public url and port provided in Settings. But I'm not able to access the DB via the private network from the app. What could be the reason?
2 Replies
3 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!
3 months ago
Hi there.
Since Redis is reachable via the public URL but not through the private network, this points to a networking or environment setup issue rather than Redis itself.
Here are a few things you can check:
Project setup: Make sure your Node.js app and Redis service are in the same Railway project and private network. Private networking won’t work across different projects.
Connection string: Double‑check that you’re using the private host and port values from Railway settings, not the public ones.
Redeploy: Restarting or redeploying the app can refresh private network connections if they got stuck.
Plan or settings: Confirm that private networking is still enabled for your project. If you recently changed plan or settings, this can affect access.
This doesn’t look like a Redis outage, but rather a private networking issue in the deployment.
Let me know if checking the project/network setup helps narrow it down.