MongoDB: Using `tlsCAFile` fails
See original GitHub issueUsing tlsCAFile
locally always fails with an error message including The system cannot find the file specified. (os error 2)
.
See more details below.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Unable to connect to MongoDB using SSL/TLS
Hi @Takis, @Prasad_Saya I am trying to connect to MongoDB server through mongo client and facing following error: SSL peer certificate ...
Read more >MongoDB 4.4.2 / X509 -> Can't connect with mongo shell!
I am trying to set up a stand alone mongod server using X509 and then ... mongo --tls --tlsCertificateKeyFile Client.cert --tlsCAFile ...
Read more >[M220] Connection issue trying to connect with mongo shell
I am trying to test two different approachs: Run the app's test with pytest. In this case the error message is the following:...
Read more >Cannot connect to mongodb with tls - Connectors & Integrations
I set up a mongod with tls enabled: docker run -d --rm -v ... /etc/ssl/mongo/tls/certs/test.pem --tlsCAFile /etc/ssl/mongo/ca.pem.
Read more >Configure mongod and mongos for TLS/SSL - MongoDB
For instructions on upgrading a cluster currently not using TLS/SSL to using ... or missing certificate files will cause the certificate rotation to...
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
The engines expect a path relative to the .prisma/ folder. Fixing that solves the repro issue. See https://www.prisma.io/docs/concepts/components/prisma-schema/data-sources#securing-database-connections
One remaining issue to investigate is that using the library query engine seems to be using a different working directory and does not work with the file in that position. I’ll keep investigating that one.
I can reproduce this both on Windows and Mac. I wasn’t able connect using either the binary or library.