celeroncoder / celeroncoder/notary-API
TypeORM cannot connect to Remote Heroku Postgress Database
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
While connecting to the Heroku Postgres server the connection is refused with an error that SSL is not configured and if SSL: true in config the error is self-signed certificate`.
To Reproduce
Steps to reproduce the behavior:
- Go to the root of the project
- Run
npm run start:prod - Wait for the nest application to be initialized.
- See the error.
Expected behavior
The Server must connect to the Postgres DB with no errors.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Most probably the reason is that the Postgress database hosted on Heroku is configured with ssl-only: true.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the repository root and run npm run start:prod to reproduce the connection failure described for the Heroku Postgres database. Compare the current connection behavior with the reported SSL errors; done means the NestJS application initializes and connects to the database without errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, typescript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100