Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do you fix UNABLE_TO_GET_ISSUER_CERT_LOCALLY

Prabu N September 17, 2024

I am able to deploy after setting "set NODE_TLS_REJECT_UNAUTHORIZED=0". But during tunnelling, i get below error.

FetchError: request to https://jira/rest/api/3/myself failed, reason: unable to get local issuer certificate at ClientRequest. (webpack://jira-global-page-ui-kit/node_modules/node-fetch/lib/index.mjs:1495:1) at ClientRequest.emit (node:events:531:35) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:511:5) at TLSSocket.emit (node:events:531:35) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { type: 'system', errno: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY', code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY' }

 

It works fine in personal laptop. But not in office laptop (zscaler/firewall might be the reason). But I would like to know how we can resolve this.

I saw there was a suggestion to add NODE_EXTRA_CA_CERTS to env variable I did with a CER file i found under trusted certificates. But still facing same error.

2 answers

0 votes
Abby Maris October 16, 2025

The error "UNABLE_TO_GET_ISSUER_CERT_LOCALLY" in Node.js appears when the system can't verify an SSL certificate because the issuer's certificate (from the certificate authority) isn't found in the local trust store. This means Node.js can't complete the chain of trust needed to confirm the server's identity. It usually happens when the certificate chain is incomplete, the CA isn't trusted locally, or intermediate certificate are missing. To fix it, ensure the full certificate  chain is properly installed and that your system or application trusts the issuing CA. There are many different ways to fix the error which are as follows:- 

1) Temporarily Stop Rigid SSL verification

2) Change the Default Public registry version to HTTP

3) Disable certificate verification altogether

4) Modify the settings of the CA file

I hope it helps!

 

0 votes
vikram
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 22, 2024

Hi @Prabu N 

I think the same as you assume, like the issue you are facing is from zScaler fire wall.

I think you can try the below solution worked for some one else for other software installation. 

https://github.com/orgs/community/discussions/8866

good luck.

Vikram P

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events