Error unable to verify the first certificate in nodejs

Question

I m trying to download a file from jira server using an url but I m getting an error  how to include certificate in the code to verify Error   Error  unable to verify the first certificate in nodejs  at Error  native      at TLSSocket  lt anonymous gt    tls wrap js 929 36     at TLSSocket emit  events js 104 17   at TLSSocket  finishInit   tls wrap js 460 8    My Nodejs code   var https   require  https    var fs   require  fs    var options         host   jira example com       path    secure attachment 206906 update xlsx      https get options  function  http res         var data             http res on  data   function  chunk             data    chunk                http res on  end   function               var file   fs createWriteStream  file xlsx            data pipe file

User · Answer

The server you re trying to download from may be badly configured  Even if it works in your browser  it may not be including all the public certificates in the chain needed for a cache-empty client to verify   I recommend checking the site in SSLlabs tool  https   www ssllabs com ssltest   Look for this error      This server s certificate chain is incomplete    And this      Chain issues         Incomplete

User · Answer

GoDaddy SSL CCertificate  I ve experienced this while trying to connect to our backend API server with GoDaddy certificate and here is the code that I used to solve the problem   var rootCas   require  ssl-root-cas latest   create     rootCas    addFile path join   dirname      config ssl gd bundle-g2-g1 crt            will work with all https requests will all libraries  i e  request js  require  https   globalAgent options ca   rootCas    PS   Use the bundled certificate and don t forget to install the library npm install ssl-root-cas

User · Answer

I met very rare case  but hopely it could help to someone  made a proxy service  which proxied requests to another service  And every request s error was  quot unable to verify the first certificate quot  even when i added all expected certificates  The reason was pretty simple - i accidently re-sent also the  quot host quot  header  Just make sure you don t send  quot host quot  header explicitly

User · Answer

I faced this issue few days back and this is the approach I followed and it works for me  For me this was happening when i was trying to fetch data using axios or fetch libraries as i am under a corporate firewall  so we had certain particular certificates which node js certificate store was not able to point to  So for my loclahost i followed this approach  I created a folder in my project and kept the entire chain of certificates in the folder and in my scripts for dev-server package json  i added this alongwith server script so that node js can reference the path   quot dev-server quot  set NODE EXTRA CA CERTS certificates certs-bundle crt  For my servers different environments  I created a new environment variable as below and added it I was using Openshift but i suppose the concept will be same for others as well   quot name quot  NODE EXTRA CA CERTS  quot value quot  certificates certs-bundle crt  I didn t generate any certificate in my case as the entire chain of certificates was already available for me

User · Answer

Another approach to solve this is to use the following module   node extra ca certs mozilla bundle  This module can work without any code modification by generating a PEM file that includes all root and intermediate certificates trusted by Mozilla  You can use the following environment variable  Works with Nodejs v7 3     NODE EXTRA CA CERTS  To generate the PEM file to use with the above environment variable  You can install the module using   npm install --save node extra ca certs mozilla bundle   and then launch your node script with an environment variable   NODE EXTRA CA CERTS node modules node extra ca certs mozilla bundle ca bundle ca intermediate root bundle pem node your script js   Other ways to use the generated PEM file are available at   https   github com arvind-agarwal node extra ca certs mozilla bundle  NOTE  I am the author of the above module

User · Answer

Try adding the appropriate root certificate This is always going to be a much safer option than just blindly accepting unauthorised end points  which should in turn only be used as a last resort  This can be as simple as adding require  https   globalAgent options ca   require  ssl-root-cas latest   create     to your application  The SSL Root CAs npm package  as used here  is a very useful package regarding this problem

User · Answer

This actually solved it for me  from https   www npmjs com package ssl-root-cas     INCORRECT  but might still work  var server   https createServer     key  fs readFileSync  privkey pem    ascii      cert  fs readFileSync  cert pem    ascii      a PEM containing ONLY the SERVER certificate         CORRECT  should always work  var server   https createServer     key  fs readFileSync  privkey pem    ascii      cert  fs readFileSync  fullchain pem    ascii      a PEM containing the SERVER and ALL INTERMEDIATES

User · Answer

This Worked For me    adding agent and  rejectUnauthorized  set to false   x000D   x000D  const https   require  https      Add This x000D  const bindingGridData   async      gt    x000D    const url    your URL-Here   x000D    const request   new Request url    x000D      method   GET   x000D      headers  new Headers   x000D        Authorization   Your Token If Any   x000D         Content-Type    application json   x000D          x000D        Add The Below x000D      agent  new https Agent   x000D        rejectUnauthorized  false  x000D          x000D        x000D    return await fetch request  x000D       then  response  any    gt    x000D        return response json    x000D         x000D       then  response  any    gt    x000D        console log  response is   response   x000D        return response  x000D         x000D       catch  err  any    gt    x000D        console log  This is Error   err   x000D        return  x000D          x000D     x000D   x000D   x000D

User · Answer

You may be able to do this by modifying the request options as below  If you are using a self-signed certificate or a missing intermediary  setting strictSSL to false will not force request package to validate the certificate   var options        host   jira example com      path    secure attachment 206906 update xlsx      strictSSL  false

User · Answer

Another dirty hack  which will make all your requests insecure   process env  NODE TLS REJECT UNAUTHORIZED     0

User · Answer

unable to verify the first certificate  The certificate chain is incomplete   It means that the webserver you are connecting to is misconfigured and did not include the intermediate certificate in the certificate chain it sent to you   Certificate chain  It most likely looks as follows    Server certificate - stores a certificate signed by intermediate  Intermediate certificate - stores a certificate signed by root  Root certificate - stores a self-signed certificate    Intermediate certificate should be installed on the server  along with the server certificate  Root certificates are embedded into the software applications  browsers and operating systems    The application serving the certificate has to send the complete chain  this means the server certificate itself and all the intermediates  The root certificate is supposed to be known by the client   Recreate the problem  Go to https   incomplete-chain badssl com using your browser    It doesn t show any error  padlock in the address bar is green   It s because browsers tend to complete the chain if it   s not sent from the server   Now  connect to https   incomplete-chain badssl com using Node      index js const axios   require  axios     axios get  https   incomplete-chain badssl com      then function  response        console log response           catch function  error        console log error           Logs   Error  unable to verify the first certificate    Solution  You need to complete the certificate chain yourself   To do that     1  You need to get the missing intermediate certificate in  pem format  then    2a  extend Node   s built-in certificate store using NODE EXTRA CA CERTS     2b  or pass your own certificate bundle  intermediates and root  using ca option   1  How do I get intermediate certificate   Using openssl  comes with Git for Windows    Save the remote server s certificate details   openssl s client -connect incomplete-chain badssl com 443 -servername incomplete-chain badssl com   tee logcertfile   We re looking for the issuer  the intermediate certificate is the issuer   signer of the server certificate    openssl x509 -in logcertfile -noout -text   grep -i  issuer    It should give you URI of the signing certificate  Download it   curl --output intermediate crt http   cacerts digicert com DigiCertSHA2SecureServerCA crt   Finally  convert it to  pem   openssl x509 -inform DER -in intermediate crt -out intermediate pem -text   2a  NODE EXTRA CERTS  I m using cross-env to set environment variables in package json file    start    cross-env NODE EXTRA CA CERTS   C   Users  USERNAME  Desktop  ssl-connect  intermediate pem   node index js    2b  ca option  This option is going to overwrite the Node s built-in root CAs   That s why we need to create our own root CA  Use ssl-root-cas   Then  create a custom https agent configured with our certificate bundle  root and intermediate   Pass this agent to axios when making request      index js const axios   require  axios    const path   require  path    const https   require  https    const rootCas   require  ssl-root-cas   create     rootCas addFile path resolve   dirname    intermediate pem     const httpsAgent   new https Agent  ca  rootCas     axios get  https   incomplete-chain badssl com     httpsAgent       then function  response        console log response           catch function  error        console log error           Instead of creating a custom https agent and passing it to axios  you can place the certifcates on the https global agent      Applies to ALL requests  whether using https directly or the request module  https globalAgent options ca   rootCas      Resources    https   levelup gitconnected com how-to-resolve-certificate-errors-in-nodejs-app-involving-ssl-calls-781ce48daded https   www npmjs com package ssl-root-cas https   github com nodejs node issues 16336 https   www namecheap com support knowledgebase article aspx 9605 69 how-to-check-ca-chain-installation https   superuser com questions 97201 how-to-save-a-remote-server-ssl-certificate-locally-as-a-file  How to convert  crt to  pem

User · Answer

I was using nodemailer npm module  The below code solved the issue       tls            do not fail on invalid certs      rejectUnauthorized  false

User · Answer

for   unable to verify the first certificate in nodejs    reject unauthorized is needed   request  method   GET             rejectUnauthorized   false            url   url           headers      Content-Type    application json           function err data body           pipe         fs createWriteStream  file html

User · Answer

You can disable certificate checking globally - no matter which package you are using for making requests - like this     Disable certificate errors globally     ES6 imports  eg typescript      import   as https from  https  https globalAgent options rejectUnauthorized   false  Or    Disable certificate errors globally     vanilla nodejs     require  https   globalAgent options rejectUnauthorized   false  Of course you shouldn t do this - but it s certainly handy for debugging and or very basic scripting where you absolutely don t care about certificates being validated correctly

[node.js] Error: unable to verify the first certificate in nodejs

Examples related to node.js

Examples related to ssl-certificate

Examples related to jira