Database Connection Refused

[tawihealth]

ISSUE

We’d like to initialize our database; however we’re unable to connect to it despite setting its access to public.

Similar issue was raised here

HOW TO REPRODUCE

[rophilogene (Romaric Philogene)]

Hi @tawihealth ,

Can you please provide more details about the database that you’ve spin up with Qovery? Is it a managed or container version of Postgres? Are you using a cluster type EKS or EC2?

Romaric

[tawihealth]

This is a Container version of PG for our staging environment.

We deployed on EC2(K3S)

[rophilogene (Romaric Philogene)]

You might find this thread interesting for your issue.

Unable to connect to Postgres

Hi @NTS , unfortunately accessing a public database is one of the limitations we have today when using a Sincle EC2 (K3S) type cluster (see the limitations here). We should block any user to select “public” on a database when using a Single EC2 cluster. We will support soon a port-forward option in our CLI to let you connect to any database, no matter their accessibility. In the meantime, you can ssh via our CLI to another application within your environment and connect to the PostgreSQL from …

[tawihealth]

For future reader:

I fixed this by SSH’ing into DB and running the SQL commands; you need the Qovery CLI.
Once logged in,

• Set the context to your DB

• Start the shell - this drops you into the default shell for your DB

• Run your commands

• Remember in its current state your DBs are not publicly reachable, so point your apps to the internal host url.