DocumentDB emulator self signed error
See original GitHub issueWhen trying to use the library with the documentDB emulator the connection fails with:
{ Error: self signed certificate
at Error (native)
at TLSSocket.<anonymous> (_tls_wrap.js:1062:38)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at TLSSocket._finishInit (_tls_wrap.js:586:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:416:38) code: 'DEPTH_ZERO_SELF_SIGNED_CERT' }
I did not find a option to allow self signed certificates for the connection.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Azure CosmosDB REST error creating document
I'm making a pretty bare REST request, so I'm not adding this parameter myself (and I don't even know what header -- presumably...
Read more >Export the Azure Cosmos DB Emulator certificates
Export the Azure Cosmos DB TLS/SSL certificate · Start the Windows Certificate manager by running certlm. · Click on Details then OK. ·...
Read more >Updating Your Amazon DocumentDB TLS Certificates
Instructions for updating CA certificates to use the new CA certificate to create TLS connections in Amazon DocumentDB.
Read more >Connecting to Azure Cosmos DB emulator from RoboMongo
First step I downloaded the Document Db emulator, now it is Azure Cosmos ... And select the Authentication Mode as Self-signed Certificate ....
Read more >How to connecto DBeaver with Db2 using SSL self-signed ...
5 database on Linux, with a self signed certificate. Check your Db2-server db2diag.log, there should be no errors relating to GSK or Gskit...
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
@Hosar yes set NODE_TLS_REJECT_UNAUTHORIZED=0 works too however the problem with that is it will disable tls authorization across your node runtime not for only the https://localhost:8081/ which was intended.
I solved this issue using https on the endpoint https://localhost:8081/ And setting the following when running the script. set NODE_TLS_REJECT_UNAUTHORIZED=0