MongoNetworkError: getaddrinfo ENOTFOUND mongo.railway.internal
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?14 Replies
Project ID:
3b13cbe2-3b70-48df-8799-b43f302ae6bcRailway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
3 seconds is required, not 100ms
Okay, thanks. I'm making the changes and monitoring I would get the error again.
I just added the delay, and still getting the ENOTFOUND error
nixpacks or Dockerfile?
Dockerfile
it might be due to alpine3.18
you are correct, could be a few combined things too
do you know where to find the alpine variable to fix this?
Solution
ENABLE_ALPINE_PRIVATE_NETWORKING=true ?correct
are you also using ioredis?
Yes, I'm initilizing using
family: 0perfect
If I switch node-alpine with the node-slim would that solve most of the networking problems?
yes you can do that or set the service variable you mentioned, whatever works best for you
Okay it seems to be fixed, thanks. We can close this