Error: P1011: Error opening a TLS connection: Internal error
See original GitHub issueAs a result of: https://prisma.slack.com/archives/CKQTGR6T0/p1605611171317000
I tried migrating my database hosted on Google Cloud SQL and got the following error:
I am not using SSL.
This is the format of the connection string I am using: postgresql://username:password@IP:Port/database
Connecting to the database with psql
with the same connection string works fine.
Prisma version: 2.11.0 (But the error also occurred with 2.10.0) OS: MacOS BigSur
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:18 (6 by maintainers)
Top Results From Across the Web
Error message reference - Prisma
Prisma Client throws a PrismaClientInitializationError exception if something goes wrong when the query engine is started and the connection to the database is ......
Read more >Error message when you connect to SQL Server
The TLS connection request has failed. The attached data contains the server certificate.
Read more >Prisma - Supabase
Connect your Supabase postgres database to your Prisma project. ... that uses PgBouncer for connection pooling, you might see the following error:.
Read more >"Authentication failed for user" when running ... - appsloveworld
I am trying to import a SQL Server database into prisma using to prisma db pull ... Error: P1011: Error opening a TLS...
Read more >(104)Connection reset by peer errors only when accessing ...
If the server has been rebooted, we can always access the quiz edit page first time, but see the error every time after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to resolve this issue by adding:
trustServerCertificate=true;
to the DATABASE_URL
I also bypassed the issue by issuing a new certificate (Create new certificate) and rotating it (Rotate certificate):