Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

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-cli\node_mod

harmad
Level 1
Level 1

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.

1 Accepted Solution
justin_at_adobe2
Correct answer by
Employee
Employee

@harmad 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)?

View solution in original post

4 Replies
justin_at_adobe2
Employee
Employee

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)

harmad
Level 1
Level 1

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

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

justin_at_adobe2
Correct answer by
Employee
Employee

@harmad 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)?

View solution in original post

harmad
Level 1
Level 1

@justin_at_adobe2  seems like related to company laptop restriction, I am able to get data after connecting to VPN, Thank you