Unable to connect to remote Postgres DB with ssl=true #2394
Comments
Yup. I was having trouble connecting to an external database from pretty much any database hosting provider (AWS, Heroku, etc). |
Thanks! I was able to test the alpha channel (1.10.0-alpha.24) against the latest stable version (1.8.3). When running I was expecting that deciding to use SSL would have some impact on the resulting
While I also wasn't able to get past this issue when trying to manually enable ssl by changing the |
Thanks a lot for the update, @andrewjmead! We'll soon double check if any changes to |
Reopening this because at the moment there is no documented way to pass the While the CLI asks for |
Yeah. I appears the new |
We are working on this issue from the backend perspective: #2594 This is not released yet but will be soon. We will update this issue with instructions and close it then. Thanks! |
That's awesome. It looks like that would work great with SSL without certs. Thanks for this. |
I can confirm that this is resolved. |
Yup! This is working for me too 😄 |
Confirming is working on my end too 👍 |
Bug Report
Prisma Version 1.8
Issue
It is not currently possible to connect to a remote PostgresDB with ssl=true the option is either ignored or not supported.
Reproduction
run > prisma init
options:
Enter connection details for remote database.
CLI throws error:
Could not connect to database. no pg_hba.conf entry for host "86.128.185.193", user "wctuojjcmucvxh", database "d3bjoonnf7l2sq", SSL off
Expected behavior?
The CLI should connect to the remote database
The text was updated successfully, but these errors were encountered: