a year ago
As of last night I noticed that my internal private URLs aren't working anymore. I have a Node app that has private internal URLs to access a Browerless and Postgres instance in my service, but I'm seeing errors such as
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
Error: getaddrinfo ENOTFOUND postgres.railway.internal
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'postgres.railway.internal'
}
Node.js v18.18.2I haven't touched this service in weeks, so not sure what changed last night.
11 Replies
a year ago
can you please switch to v2 here -

I only found this setting on 2 of the 4 services that are running in this project (Postgres and one of the Node apps)
a year ago
that means they are on v2 already, the setting is one way only, you set v2 and the option disappears so you cant go back
Okay, well the secondary node app is now talking to Postgres just fine.
I'm going to restart the primary node app and browserless (both of which were already on v2) and see if the primary node app starts working again
a year ago
sounds good
For future reference, turns out my primary node app needed a small code update due to a downstream dependency (not related to Railway). I'm all good now!
a year ago
awesome
a year ago
!s
Status changed to Solved brody • over 1 year ago