unable to connect to postgres
madmagestudio
PROOP

24 days ago

My postgres cluster seems to be online and running but my application is unable to connect for about a day now.

[ConfigService] Failed to fetch public features, using defaults. Database might be unreachable during build. error: pgpool is not accepting any new connections

I have not changed anything related to the database in the code.

I also am unable to connect using pgAdmin for the same amount of time. I am concerned because I am being asked to log in using 'postgres' user but the password that I thought was correct is not working.

Solved

5 Replies

Railway
BOT

24 days ago

The proxy service logs confirm that pgpool sees all backend nodes as down. Your proxy was last deployed in February, while the primary and replica were both redeployed in the last couple of days. Try redeploying the proxy service so it re-establishes connections to the current backend nodes. For the password issue, after converting to HA the correct credentials are on the proxy (Postgres HA) service's variables tab - make sure you're using those when connecting externally via pgAdmin.


Status changed to Awaiting User Response Railway 24 days ago


Railway

The proxy service logs confirm that pgpool sees all backend nodes as down. Your proxy was last deployed in February, while the primary and replica were both redeployed in the last couple of days. Try redeploying the proxy service so it re-establishes connections to the current backend nodes. For the password issue, after converting to HA the correct credentials are on the proxy (Postgres HA) service's variables tab - make sure you're using those when connecting externally via pgAdmin.

madmagestudio
PROOP

24 days ago

I did the redeploy, it was successful. Still having the same connection issue:

[ConfigService] Failed to fetch public features, using defaults. Database might be unreachable during build. AggregateError:

at async l (.next/server/chunks/[root-of-the-server]__0i74kqv._.js:1:1796)

at async Object.getPublicFeatures (.next/server/chunks/[root-of-the-server]__08lexqv._.js:1:4239)

at async i (.next/server/chunks/[root-of-the-server]__0islpuu._.js:1:3020)

at async u (.next/server/chunks/[root-of-the-server]__0islpuu._.js:1:6789)

at async l (.next/server/chunks/[root-of-the-server]__0islpuu._.js:1:7830) {

code: 'ECONNREFUSED',

Error: connect ECONNREFUSED

Status changed to Awaiting Railway Response Railway 24 days ago


madmagestudio
PROOP

23 days ago

Anyone have thoughts on this? It's been like 2.5 days and I can't connect to postgres. Would be nice to get an answer.


20 days ago

Sorry for the wait. We found that both your primary and replica database containers had exited, which is why the proxy couldn't reach them. We've redeployed both and they should be online and healthy now. Can you confirm connectivity is restored on your end?


Status changed to Awaiting User Response Railway 20 days ago


madmagestudio
PROOP

19 days ago

The site is functional again and I can get into the db. Thank you.


Status changed to Awaiting Railway Response Railway 19 days ago


Status changed to Solved Railway 19 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...