Database connection timing out
bshyong
PROOP

a year ago

I've been seeing a database timeout recently. I believe this started happening after I resized my postgres volume to a larger size. Can't figure out how to get this working again.

I'm able to connect remotely with the connection string, so the database does work, but my Railway services can't connect to it.

error snippet

Error: connect ETIMEDOUT fd12:76ac:1bc1::2b:6114:b8c7:5432

Aug 15 00:36:46

at /app/node_modules/pg-pool/index.js:45:11

Aug 15 00:36:46

at processTicksAndRejections (node:internal/process/task_queues:95:5)

Aug 15 00:36:46

at PostgresDriver.acquireConnection (file:///app/node_modules/kysely/dist/esm/dialect/postgres/postgres-driver.js:19:24)

Aug 15 00:36:46

at RuntimeDriver.acquireConnection (file:///app/node_modules/kysely/dist/esm/driver/runtime-driver.js:44:28)

Aug 15 00:36:46

at DefaultConnectionProvider.provideConnection (file:///app/node_modules/kysely/dist/esm/driver/default-connection-provider.js:8:28)

Aug 15 00:36:46

yarn run v1.22.22

Aug 15 00:36:46

$ ponder start

Aug 15 00:36:46

7:36:46 AM INFO build Using Postgres database 'postgres.railway.internal:5432/railway' (from DATABASE_PRIVATE_URL env var)

This is showing when I open the Postgres service

Solved

3 Replies

bshyong
PROOP

a year ago

This is showing when I open the Postgres service


bshyong
PROOP

a year ago

This has been resolved. Somehow the TCP proxy url was removed from the config, which caused the above to show undefined in the UI.

Needed to add a TCP proxy url, and reploy the database service to resolve the issue.


david
EMPLOYEE

a year ago

Thanks for following up with the resolution. Let us know if any other issues come up.


Status changed to Awaiting User Response Railway over 1 year ago


Status changed to Solved brody over 1 year ago


Loading...