a month ago
i cant deploy, i get this error, it was working. i just did one change and everything stopped i rolled back no luck.
looks like infra issue
errno: -110,
/app/node_modules/pg-pool/index.js:45
Error.captureStackTrace(err)
code: 'ETIMEDOUT',
^
syscall: 'connect',
AggregateError [ETIMEDOUT]:
at /app/node_modules/pg-pool/index.js:45:11
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async initDB (/app/server.js:126:5) {
code: 'ETIMEDOUT',
[errors]: [
Error: connect ETIMEDOUT fd12:88bb:ace2:1:5000:87:c2af:471b:5432
address: 'fd12:88bb:ace2:1:5000:87:c2af:471b',
at createConnectionError (node:net:1651:14)
port: 5432
at Timeout.internalConnectMultipleTimeout (node:net:1710:38)
},
at listOnTimeout (node:internal/timers:596:11)
Error: connect ETIMEDOUT 10.175.71.27:5432
at process.processTimers (node:internal/timers:529:7) {
at createConnectionError (node:net:1651:14)
at afterConnectMultiple (node:net:1681:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '10.175.71.27',
port: 5432
}
]
}
Node.js v22.11.0
npm warn config production Use --omit=dev instead.
2 Replies
a month ago
Your app is connecting to Postgres using raw IP addresses rather than the private DNS hostname, and the Postgres service appears to be running fine. This typically happens when the Postgres service was redeployed and received new internal IP addresses, but your app's connection string still references the old IPs. Check that your DATABASE_URL (or equivalent connection variable) uses the railway.internal hostname via reference variables instead of hardcoded IPs, and try redeploying both services.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your app is connecting to Postgres using raw IP addresses rather than the private DNS hostname, and the Postgres service appears to be running fine. This typically happens when the Postgres service was redeployed and received new internal IP addresses, but your app's connection string still references the old IPs. Check that your DATABASE_URL (or equivalent connection variable) uses the `railway.internal` hostname via [reference variables](https://docs.railway.com/guides/variables#reference-variables) instead of hardcoded IPs, and try redeploying both services.
a month ago
it is sorted, something wrong in USA region, i moved the app to Asia it worked.. i checked the varaiable for db, it is not pointing to ip, it is internal name only.
. thank you for your time.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved brody • about 1 month ago