MongoNetworkError: getaddrinfo ENOTFOUND mongo.railway.internal

a year ago

I'm getting random errors from my NodeJS express app.
I have added the 100ms before connecting to mongo on the start.
The app connects successfully, and can query the Mongo database, but randomly I get an getaddrinfo ENOTFOUND error, which makes my app unstable.
Any idea about what might be happening?

0 Replies


a year ago

3 seconds is required, not 100ms


a year ago

Okay, thanks. I'm making the changes and monitoring I would get the error again.


a year ago

I just added the delay, and still getting the ENOTFOUND error

1242132655005372400


a year ago

nixpacks or Dockerfile?


a year ago

Dockerfile


a year ago

it might be due to alpine3.18


a year ago

you are correct, could be a few combined things too


a year ago

do you know where to find the alpine variable to fix this?


a year ago

ENABLE_ALPINE_PRIVATE_NETWORKING=true ?


a year ago

correct


a year ago

are you also using ioredis?


a year ago

Yes, I'm initilizing using family: 0


a year ago

perfect


a year ago

If I switch node-alpine with the node-slim would that solve most of the networking problems?


a year ago

yes you can do that or set the service variable you mentioned, whatever works best for you


a year ago

Okay it seems to be fixed, thanks. We can close this