Unable to verify leaf signature

Unable to verify leaf signature

I’m using node.js request.js to reach an api. I’m getting this error


All of my credentials are accurate and valid, and the server’s fine. I made the same request with postman.
“url”: domain+”/api/orders/originator/”+id,
“method”: “GET”,
“X-API-KEY”: key
}, function(err, response, body){

This code is just running in an executable script ex. node ./run_file.js, Is that why? Does it need to run on a server?


Solution 1:

Note: the following is dangerous, and will allow API content to be intercepted and modified between the client and the server.

This also worked

process.env['NODE_TLS_REJECT_UNAUTHORIZED'] = '0';

Solution 2:

It’s not an issue with the application, but with the certificate which is signed by an intermediary CA.
If you accept that fact and still want to proceed, add the following to request options:

rejectUnauthorized: false

Full request:

    "rejectUnauthorized": false,
    "url": domain+"/api/orders/originator/"+id,
    "method": "GET",
        "X-API-VERSION": 1,
        "X-API-KEY": key
}, function(err, response, body){

Solution 3:

The Secure Solution

Rather than turning off security you can add the necessary certificates to the chain. First install ssl-root-cas package from npm:

npm install ssl-root-cas

This package contains many intermediary certificates that browsers trust but node doesn’t.

var sslRootCAs = require('ssl-root-cas/latest')

Will add the missing certificates. See here for more info:


Also, See the next answer below

Solution 4:

CoolAJ86’s solution is correct and it does not compromise your security like disabling all checks using rejectUnauthorized or NODE_TLS_REJECT_UNAUTHORIZED. Still, you may need to inject an additional CA’s certificate explicitly.

I tried first the root CAs included by the ssl-root-cas module:


I still ended up with the UNABLE_TO_VERIFY_LEAF_SIGNATURE error. Then I found out who issued the certificate for the web site I was connecting to by the COMODO SSL Analyzer, downloaded the certificate of that authority and tried to add only that one:

  .addFile(__dirname + '/comodohigh-assurancesecureserverca.crt');

I ended up with another error: CERT_UNTRUSTED. Finally, I injected the additional root CAs and included “my” (apparently intermediary) CA, which worked:

  .addFile(__dirname + '/comodohigh-assurancesecureserverca.crt');

Solution 5:

For Create React App (where this error occurs too and this question is the #1 Google result), you are probably using HTTPS=true npm start and a proxy (in package.json) which goes to some HTTPS API which itself is self-signed, when in development.

If that’s the case, consider changing proxy like this:

"proxy": {
  "/api": {
    "target": "https://localhost:5001",
    "secure": false

secure decides whether the WebPack proxy checks the certificate chain or not and disabling that ensures the API self-signed certificate is not verified so that you get your data.

Solution 6:

I had the same issues. I have followed @ThomasReggi and @CoolAJ86 solution and worked well but I’m not satisfied with the solution.

Because “UNABLE_TO_VERIFY_LEAF_SIGNATURE” issue is happened due to certification configuration level.

I accept @thirdender solution but its partial solution.As per the nginx official website, they clearly mentioned certificate should be combination of The server certificate and chained certificates.

enter image description here