ENOTFOUND redis.railway.internal

crinklepackage
HOBBY

7 months ago

I am experiencing a DNS resolution issue (ENOTFOUND) when trying to connect to the Redis service using the internal hostname (redis.railway.internal). Here are the details of my setup and the troubleshooting steps I've already taken:

Environment Setup:

  • Services: wavenotes-api, wavenotes-worker

  • BullMQ

  • Redis Service: Linked to both services above

  • Environment Variables: REDIS_URL is set to redis://default:...@redis.railway.internal:6379

Troubleshooting Steps:

  1. Verified Environment Variables: Confirmed that REDIS_URL and other related variables are correctly set and pointing to redis.railway.internal.

  2. Restarted Services: I have restarted both the wavenotes-api and wavenotes-worker services to ensure there isn't a transient issue affecting connectivity.

  3. Checked Logs: Reviewed logs for any additional network-related errors but found none that provided further insights beyond the ENOTFOUND error.

In addition to the above, I've tried many solutions but continue to get the same error.

Is there anything obvious in our setup that would be causing this?

Solved

9 Replies

brody
EMPLOYEE

7 months ago

Hello,

Have you checked out our documentation on this error? -

https://docs.railway.com/dynamic/reference/errors/enotfound-redis-railway-internal

Best,
Brody

Status changed to Awaiting User Response Railway • 7 months ago

crinklepackage
HOBBY

7 months ago

I have, thanks Brody. I've attached some of our implementation—do you see anything that would create the error?

Attachments

railway-red...

Status changed to Awaiting Railway Response Railway • 7 months ago

brody
EMPLOYEE

7 months ago

Going forward, please do not respond to support with AI written answers, it is insincere.

Either way, from a cursory look, it seems fine.

Are you getting this error locally? or during build or runtime?

Status changed to Awaiting User Response Railway • 7 months ago

crinklepackage
HOBBY

7 months ago

Our API build is successful on Railway, and then during deploy we encounter the error.

RE: ai responses: understood!

Status changed to Awaiting Railway Response Railway • 7 months ago

crinklepackage

Our API build is successful on Railway, and then during deploy we encounter the error. RE: ai responses: understood!

crinklepackage
HOBBY

7 months ago

One other thought:

I had this project set up with a different codebase (that I subsequently rewrote). Is it possible that there's a caching issue?

brody
EMPLOYEE

7 months ago

Nope nothing to do with cache, all signs are pointing to a code issue, you are not setting family to 0 properly.

Please review your code and the documentation provided.

Status changed to Awaiting User Response Railway • 7 months ago

jkogara
PRO

5 months ago

Seeing this issue now after the recent network outage, we're not using the library mentioned in the linked knowledge document and can connect to our redis using the proxy. Please advise.

Status changed to Awaiting Railway Response Railway • 5 months ago

jkogara

Seeing this issue now after the recent network outage, we're not using the library mentioned in the linked knowledge document and can connect to our redis using the proxy. Please advise.

jkogara
PRO

5 months ago

We're using the ruby redis client

echohack
EMPLOYEE

5 months ago

Hi jkogara, can you open a new issue detailing your problem along with steps to reproduce? Thank you.

Status changed to Awaiting User Response Railway • 5 months ago

Status changed to Solved echohack • 5 months ago