npm ERR code UNABLE TO GET ISSUER CERT LOCALLY

Question

I am trying all the ways of creating react application  I have tried with maven and now i am trying with crate-react-app build system from Facebook Incubators   When i tried to run the command create-react-app my-app in npm environment  it worked on my personal system with no issues  But when i tried the same command in my work environment  i have encountered with this error on command prompt  npm ERR  node v6 10 2 npm ERR  npm  v3 10 10 npm ERR  code UNABLE TO GET ISSUER CERT LOCALLY  npm ERR  unable to get local issuer certificate npm ERR  npm ERR  If you need help  you may report this error at  npm ERR       lt https   github com npm npm issues gt

User · Answer

got the below error  PS C  Users chpr Documents GitHub vue-nwjs-hours-tracking gt  npm install vue npm ERR  code UNABLE TO GET ISSUER CERT LOCALLY npm ERR  errno UNABLE TO GET ISSUER CERT LOCALLY npm ERR  request to https   registry npmjs org vue failed  reason  unable to get local issuer certificate npm ERR  A complete log of this run can be found in  npm ERR  C  Users chpr AppData Roaming npm-cache logs 2020-07-29T03 22 40 225Z-debug log PS C  Users chpr Documents GitHub vue-nwjs-hours-tracking gt  PS C  Users chpr Documents GitHub vue-nwjs-hours-tracking gt  npm ERR  C  Users chpr AppData Roaming npm-cache logs 2020-07-29T03 22 40 225Z-debug log  Below command solved the issue  npm config set strict-ssl false

User · Answer

A quick solution from the internet search was npm config set strict-ssl false  luckily it worked  But as a part of my work environment  I am restricted to set the strict-ssl flag to false    Later I found a safe and working solution   npm config set registry http   registry npmjs org      this worked perfectly and I got a success message Happy Hacking  by not setting the strict-ssl flag to false

User · Answer

Changing the NPM repo URL to HTTP works as a quick-fix  but I wanted to use HTTPS   In my case  the proxy at my employer  ZScaler  was causing issues  as it acts as a MITM  causing certification verification issues   I forgot I found a script that helps with this and Git  for cloning GitHub repos via HTTPS had the same issue  and forked it for my use  Basically  it does the following for git   git config --global http proxy http   gateway zscaler net 80  git config --system http proxy http   gateway zscaler net 80    and for Node  it adds proxy http   gateway zscaler net 80  to the end of c  Users  USERNAME npm  npmrc  That solved the issue for me

User · Answer

After trying out every solution I could find    Turning off strict ssl  npm config set strict-ssl false Changing the registry to http instead of https  npm config set registry http   registry npmjs org  Changing my cafile setting  npm config set cafile  path to your cert pem Stop rejecting unknown CAs  set NODE TLS REJECT UNAUTHORIZED 0   The solution that seems to be working the best for me now is to use the NODE EXTRA CA CERTS environment variable which extends the existing CAs rather than replacing them with the cafile option in your  npmrc file  You can set it by entering this in your terminal  NODE EXTRA CA CERTS path to your cert pem  Of course  setting this variable every time can be annoying  so I added it to my bash profile so that it will be set every time I open terminal  If you don   t already have a    bash profile file  create one  Then at the end of that file add export NODE EXTRA CA CERTS path to your cert pem  Then  remove the cafile setting in your  npmrc

User · Answer

The below code worked for me perfectly here make http only instead https   npm config set registry http   registry npmjs org

User · Answer

Trust me  this will work for you        npm config set registry http   registry npmjs org

User · Answer

what may be happening is your company decrypts certain traffic and re-encrypts it with their certificate  which you probably already have in your keychain or trusted root certificates   if you re using node 7 or later I ve found this fix to be compatible with node and node-gyp  for Windows you ll need to do this differently  but you basically just need to add this environment variable    export NODE EXTRA CA CERTS  absolute path to your certificates pem   in Windows you may need to remove the quotes - see comments   the pem file can have multiple certificates  https   nodejs org api cli html cli node extra ca certs file  make sure your certificates are in proper pem format  you need real line breaks not literal  n   I couldn t seem to get it to work with relative paths    or     This fix basically tells npm and node-gyp to use the check against the regular CAs  but also allow this certificate when it comes across it  Ideally you would be able to use your system s trusted certificates  but unfortunately this is not the case

User · Answer

I had this error when I tried to update npm  but had a really old version  1 3 6    installed from yum in AWS Linux   I was able to manually install a newer npm version and everything was remedied

User · Answer

In my case  at some point I set my global config to use a cert that was meant for a project   npm config list   path to global  npmrc NODE EXTRA CA CERTS      certs chain pem    I opened the file  removed the line and npm install worked again

User · Answer

For me the issue was VPN  I disconnected the VPN and  quot npm i quot  command worked with no fail

User · Answer

Had the same error   Looks like it is related to SSL certificates   If you are using NPM for public packages  don t need the security of HTTPS  you can turn off strict SSL key validation with the following command   This might be the simplest fix if you re just looking to install a few publicly available packages one time   npm config set strict-ssl false

[node.js] npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY

Examples related to node.js

Examples related to reactjs

Examples related to npm

Examples related to create-react-app