postgres DNS not resolving
arhammusheer
HOBBYOP

2 years ago

Is this an internal DNS problem? Private url isn't resolving but works with DATABASE_URL

npm WARN config production Use `--omit=dev` instead.

> tasmota-mqtt-subscriber@1.0.0 start

> node dist/index.js

Failed to connect to PostgreSQL Error: getaddrinfo ENOTFOUND postgres.railway.internal

at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26) {

errno: -3008,

code: 'ENOTFOUND',

syscall: 'getaddrinfo',

hostname: 'postgres.railway.internal'

}

npm WARN config production Use `--omit=dev` instead.

> tasmota-mqtt-subscriber@1.0.0 start

> node dist/index.js

12 Replies

arhammusheer
HOBBYOP

2 years ago

560b7a6c-de0e-4e7e-9735-0ae63ba4118a


arhammusheer
HOBBYOP

2 years ago

Nvm fixed


2 years ago

are you on the v2 runtime?


arhammusheer
HOBBYOP

2 years ago

I was on legacy


2 years ago

Legacy runtime is no fun, V2 is where it's at


arhammusheer
HOBBYOP

2 years ago

I'm not sure why it carried over when I changed V2 to legacy on a different project. This expected?


arhammusheer
HOBBYOP

2 years ago

I switched back to V2 now and private networking works now.


2 years ago

it's a per service change, nothing would be carried anywhere


arhammusheer
HOBBYOP

2 years ago

Interesting.

The config defaulted to legacy I believe

I started a project yesterday and switched the deploy to legacy.
Later I deleted the project

Today I started a new project which is this but it started as legacy.


arhammusheer
HOBBYOP

2 years ago

I'll ignore it i guess


arhammusheer
HOBBYOP

2 years ago

thanks


2 years ago

no problem


Loading...