Error: (node:13632) UnhandledPromiseRejectionWarning: FetchError: request to https://cloudmanager.adobe.io/api/programs failed, reason: unable to get local issuer certificate at ClientRequest.<anonymous> (C:\Users\ssss\AppData\Local\@adobe\aio- | Community
Skip to main content
H
hv_btm
Level 2
November 11, 2021
Solved

Error: (node:13632) UnhandledPromiseRejectionWarning: FetchError: request to https://cloudmanager.adobe.io/api/programs failed, reason: unable to get local issuer certificate at ClientRequest.<anonymous> (C:\Users\ssss\AppData\Local\@adobe\aio-

  • November 11, 2021
  • 1 reply
  • 2774 views

command --> aio cloudmanager:environment:list-variables

Error:
(node:13632) UnhandledPromiseRejectionWarning: FetchError: request to https://cloudmanager.adobe.io/api/programs failed, reason: unable to get local issuer certificate
at ClientRequest.<anonymous> (C:\Users\ssss\AppData\Local\@adobe\aio-cli\node_modules\node-fetch\lib\index.js:1483:11)
at ClientRequest.emit (events.js:400:28)
at TLSSocket.socketErrorListener (_http_client.js:475:9)
at TLSSocket.emit (events.js:400:28)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:13632) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:13632) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

 

 

Node version: v14.18.1

npm version: 8.1.3

have set the programid, org and environment ids as well.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JustinEd3

@hv_btm This is very odd. Unless there is some kind of man-in-the-middle thing going on (i.e. a proxy server), that error suggests that node/openssl cannot find the DigiCert CA certificate. curl could use a different cacerts file than node; I'm not sure how that works on Windows.

 

Does this reproduce on a different network (same machine)? What about on a different machine (but same network)?

1 reply

J
Adobe Employee
JustinEd3Adobe Employee
Adobe Employee
November 11, 2021

Are you using a proxy server?

 

Does curl https://cloudmanager.adobe.io/api/programs return an SSL error? (it should return a 403 since there's no token, but for this purpose getting a 403 is a good thing)

H
hv_btmAuthor
Level 2
November 11, 2021

@justined3 have not done any proxy settings in local company PC with admin rights.

 getting 403 when doing -- curl https://cloudmanager.adobe.io/api/programs.

J
Adobe Employee
JustinEd3Adobe EmployeeAccepted solution
Adobe Employee
November 11, 2021

@hv_btm This is very odd. Unless there is some kind of man-in-the-middle thing going on (i.e. a proxy server), that error suggests that node/openssl cannot find the DigiCert CA certificate. curl could use a different cacerts file than node; I'm not sure how that works on Windows.

 

Does this reproduce on a different network (same machine)? What about on a different machine (but same network)?

    Terms & ConditionsAccessibility statement

    Loading footer...