Attempting to connect to MongoDB (1 retries left)...

MongoDB disconnected, attempting to reconnect...

MongoDB connection error: getaddrinfo ENOTFOUND mongodb.railway.internal

Failed to connect to MongoDB after all retries

Initial MongoDB connection failed: MongooseServerSelectionError: getaddrinfo ENOTFOUND mongodb.railway.internal

at handleConnectionErrors (/app/nodemodules/mongoose/lib/connection.js:816:11)

at NativeConnection.openUri (/app/node_modules/mongoose/lib/connection.js:791:11)

at async file:///app/utils/db.js:97:9 {

reason: TopologyDescription {

type: 'Unknown',

servers: Map(1) { 'mongodb.railway.internal:27017' => [ServerDescription] },

stale: false,

compatible: true,

heartbeatFrequencyMS: 10000,

localThresholdMS: 15,

setName: null,

maxElectionId: null,

maxSetVersion: null,

commonWireVersion: 0,

logicalSessionTimeoutMinutes: null

},

code: undefined

}

Your backend can’t find mongodb.railway.internal because that hostname only works between services inside the same Railway project. If you’re running locally or in a different project, use the public MongoDB URL instead. Make sure both services are in the same project and deployed on Railway for the internal address to work.

Hey all services are in the same project and I'm using a custom URL instead of the default railway one. The setup of that URL is marked as correct so I'm unsure why the db thinks it's not in the same project.

Is there somewhere I should be checking to see where mongodb thinks it is in relation to the backend service?

If you’re still getting ENOTFOUND for mongodb.railway.internal, I'd double-check these:

• Make sure your backend is actually deployed on Railway (not running locally, which the local host might indicate).

• If you’re using a custom domain or URL for MongoDB, which apparently you are, try switching back to the default internal hostname to test.

• Restart both the backend and MongoDB services (sometimes DNS takes a minute to sync up)

• Check your backend’s logs and environment variables at runtime to confirm it’s using the right MONGO_URL.

If it still fails, try connecting to the MongoDB service from a Railway shell in your backend service. If that works, the problem is likely in your app config or how the env vars are loaded.

Please refrain from using AI Answers.

Hey ya they're not local and my backend and frontend use custom domains but not my MongoDB. I've tried the restarts and it seems to know the correct URL it just can't connect to it

Have you tried switching back to the default internal hostname to test the connection?

yup same issue thanks

What about the shell? Try connecting to the DB from there.

I can't find a Terminal in Railway , where might it live? Or should I be using CLI and login to Railway through there and try?

Install the Railway CLI: https://docs.railway.com/guides/cli

Type railway link.

Right click the service and click "Copy SSH Command"

Paste that into your CLI.

cool thanks yeah so the Public URL I can use to connect to it and it returns the db test>
However I can't connect my backend to the db (which are in the same project) using the non public URL

k figured it out the issue was the code was looking for an ipv4 but mongo had an ipv6