Local self-Hosted install error: access to postgress denied

Self Hosted Retool
1

retool-onpremise-master-api-1 | Failing checking database migrations
retool-onpremise-master-api-1 | /node_modules/sequelize/lib/dialects/postgres/connection-manager.js:131
retool-onpremise-master-api-1 | reject(new sequelizeErrors.ConnectionRefusedError(err));
retool-onpremise-master-api-1 | ^
retool-onpremise-master-api-1 |
retool-onpremise-master-api-1 | ConnectionRefusedError [SequelizeConnectionRefusedError]: connect ECONNREFUSED 127.0.0.1:5432
retool-onpremise-master-api-1 | at Client._connectionCallback (/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:131:24)
retool-onpremise-master-api-1 | at Client._handleErrorWhileConnecting (/node_modules/pg/lib/client.js:305:19)
retool-onpremise-master-api-1 | at Client._handleErrorEvent (/node_modules/pg/lib/client.js:315:19)
retool-onpremise-master-api-1 | at Connection.emit (node:events:514:28)
retool-onpremise-master-api-1 | at Socket.reportStreamError (/node_modules/pg/lib/connection.js:52:12)
retool-onpremise-master-api-1 | at Socket.emit (node:events:514:28)
retool-onpremise-master-api-1 | at emitErrorNT (node:internal/streams/destroy:151:8)
retool-onpremise-master-api-1 | at emitErrorCloseNT (node:internal/streams/destroy:116:3)
retool-onpremise-master-api-1 | at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
retool-onpremise-master-api-1 | parent: Error: connect ECONNREFUSED 127.0.0.1:5432
retool-onpremise-master-api-1 | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
retool-onpremise-master-api-1 | errno: -111,
retool-onpremise-master-api-1 | code: 'ECONNREFUSED',
retool-onpremise-master-api-1 | syscall: 'connect',
retool-onpremise-master-api-1 | address: '127.0.0.1',
retool-onpremise-master-api-1 | port: 5432
retool-onpremise-master-api-1 | },
retool-onpremise-master-api-1 | original: Error: connect ECONNREFUSED 127.0.0.1:5432
retool-onpremise-master-api-1 | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
retool-onpremise-master-api-1 | errno: -111,
retool-onpremise-master-api-1 | code: 'ECONNREFUSED',
retool-onpremise-master-api-1 | syscall: 'connect',
retool-onpremise-master-api-1 | address: '127.0.0.1',
retool-onpremise-master-api-1 | port: 5432
retool-onpremise-master-api-1 | }
retool-onpremise-master-api-1 | }
retool-onpremise-master-api-1 |
retool-onpremise-master-api-1 | Node.js v18.17.1
retool-onpremise-master-api-1 exited with code 1
retool-onpremise-master-api-1 | wait-for-it.sh: waiting 15 seconds for postgres:5432

I edited the pg_hba.conf file to md5 to allow external connections. I am able to login via psql and it is now asking for password when previously it was not. Also, in docker.new file do I have to set the username and password for the RETOOLDB_POSTGRES_DB

Thanks, Venki

2

Hey @venkir1! Are you trying to connect to a PSQL db that you are hosting locally? Can you also share the status of the containers (assuming docker-compose setup) with docker-compose ps? And any logs from the jobs runner container. Thanks

3

any update to this...same issue here

4

Hey @claycurtis44, no update as we never got any response for the above questions. Is this an initial install for you or an update etc? Are you using the docker-compose setup, helm? Is the postgres db locally hosted by you or are you using the containerized postgres? Can you share logs and the status of containers / pods?

5

trying to do a helm self hosted install.

in main.tf file we have
values = [
file("values.yaml"),
]

set {
name = "postgresql.host"
value = module.aurora_cluster_staging.write_endpoint_alias
}

in values.yaml we have
postgresql:
port: "5432"
db: "retool_staging"
# user:
# password:
ssl_enabled: true
# passwordSecretName is the name of the secret where the pg password is stored (can be used instead of password)
# passwordSecretName:
# passwordSecretKey is the key in the k8s secret, default: postgresql-password
# passwordSecretKey:

we keep getting error refused on the db