19 days ago
I have deployed a redis instance and celery worker within the same project and environment but am running into errors in the deploy logs.
[2026-02-26 03:41:16,050: ERROR/MainProcess] consumer: Cannot connect to redis://default:**@redis.railway.internal:6379//: Error -2 connecting to
redis.railway.internal:6379. Name or service not known..
Trying again in 2.00 seconds... (1/100)
[2026-02-26 03:41:18,223: ERROR/MainProcess] consumer: Cannot connect to redis://default:**@redis.railway.internal:6379//: Error -2 connecting to
redis.railway.internal:6379. Name or service not known..
Trying again in 4.00 seconds... (2/100)
[2026-02-26 03:41:22,399: ERROR/MainProcess] consumer: Cannot connect to redis://default:**@redis.railway.internal:6379//: Error -2 connecting to
redis.railway.internal:6379. Name or service not known..
Trying again in 6.00 seconds... (3/100)
[2026-02-26 03:41:28,577: ERROR/MainProcess] consumer: Cannot connect to redis://default:**@redis.railway.internal:6379//: Error -2 connecting to
redis.railway.internal:6379. Name or service not known..
Trying again in 8.00 seconds... (4/100)
[2026-02-26 03:41:36,755: ERROR/MainProcess] consumer: Cannot connect to redis://default:**@redis.railway.internal:6379//: Error -2 connecting to
redis.railway.internal:6379. Name or service not known..
Trying again in 10.00 seconds... (5/100)
Is anyone else having similar issues?
5 Replies
Status changed to Awaiting Railway Response Railway • 19 days ago
19 days ago
Yes, it is. If I use the public URL for troubleshooting, it connects fine. I’d prefer to use the private network URL though.
19 days ago
In your Redis service settings, change the private networking URL to be lowercase redis if it's uppercase Redis.
Then redeploy both services and see if that fixes it.
19 days ago
I saw the other posts mentioning that and already tried it. It looks like Railway already fixed that issue as my private network name was already lowercase. I changed it anyway and redeployed all my projects and still have the same issue.
19 days ago
I discovered the issue and it was entirely on my part. It was my first time using Railway and I was clicking on 'New' from the homepage for each service. This made them in separate projects. I thought because they were all in the same account that they could talk to each other. I've rebuilt my environment by clicking 'New' and using empty project, and then clicking 'Create' from within it to build the services. Private networking is working properly now.
Thank you @0x5b62656e5d for your suggestions and helping me out.
Status changed to Solved spectretek • 19 days ago