Postgres envs
Hey all,
Anyone got postgres working?
I have tried with all variations of our standard connection strings to get a conn to one of our postgres dbs to no avail.
TOKEN_SECRET_KEY=token
DB_CONNECTION=postgres
DB_USERNAME=username
DB_PASSWORD=password
DB_DATABASE=dbname
DB_SSL=true
DB_PORT=port
DB_PATH=postgresql://username:password@host:port/database?sslmode=require
TOKEN_SECRET_KEY=token
DB_CONNECTION=postgres
DB_USERNAME=username
DB_PASSWORD=password
DB_DATABASE=dbname
DB_SSL=true
DB_PORT=port
DB_PATH=host
TOKEN_SECRET_KEY=token
DB_CONNECTION=postgres
DB_USERNAME=username
DB_PASSWORD=password
DB_DATABASE=dbname
DB_SSL=true
DB_PORT=port
DB_PATH=postgresql://host
8 Replies
This is the error
[Nest] 75824 - 02/20/2025, 1:20:22 PM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (1)...
AggregateError [ECONNREFUSED]:
at internalConnectMultiple (node:net:1116:18)
at afterConnectMultiple (node:net:1683:7)
There is not connection request reaching the db
Hello @Classified (C Hilde) it seams that the credentials are not used correctly. Are you using Postgres in local ? If this is the case this is a possible .env file:
Explanation:
-
DB_HOST is the server name: localhost in local or it could be an URL if in remote
- DB_PORT should be a number (default 5432)
- DB_USERNAME and DB_PASSWORD are usually postgres by defaul on local
- DB_SSL was omitted (default false) as there is no SSL certificate on local (set to true if using remote managed DBs)
- DB_PATH is only for SQlite so it should not be specified.
Here is the complete documentation: https://manifest.build/docs/config#database
Let me know how it goes !Configuration | Manifest Docs
Manifest embraces the convention over configuration concept: it assumes several logical situations by default without showing you the setting to keep things as simple as possible.
Ah db_host cheers dude I will give that a shot.
All the other envs I obfuscated for here ;p
On your next doc update you should put db_host in there. 🙂
Oh you are right I forgot it !! Thank you I will add it next week
Yeah no problems dude. You are doing some great work. Dont let a little thing worry you. If you didnt respond on here that would be a pity, but I tried for a bit, in various combos that I normally use, and then sent a post up, for a pretty quick resolution. 🙂 Good work dude. Thank you!
Hey @brunobuddy is there anyway to specify a path to the ssl ca-certificate for the db?
@Classified (C Hilde) not really, what is your use case ? You can activate SSL or not in order to make it work with remote and local DBs but that's it
Our production dbs require ssl and reject non secure connnections. However manifest seems to only use a self signed ca cert when connecting. I don't want to have to inject a cert into the containers or the os (when developing). I would rather just have the ca cert in the project and reference it in config instead.
[Nest] 11528 - 02/25/2025, 1:19:01 PM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (3)...
Error: self-signed certificate in certificate chain
at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34)
at TLSSocket.emit (node:events:520:28)
at TLSSocket._finishInit (node:_tls_wrap:1078:8)
at ssl.onhandshakedone (node:_tls_wrap:864:12)
@Classified (C Hilde) I fixed it ! (works with NeonDB). update the version of manifest to the 4.8.1 with
npm i manifest@latest . In your environment file make sure that you have DB_SSL=true. Let me know if it works !