Plan of action

Based on research and analysis, this problem is occuring when the customer is behind ssome infrastructure or security layers like a proxy. The customer must adjust their infrastructure to allow the request to the Magnolia servers. 

So the CLI will be adjusted to detect this situation - and if it does it will print a helpful message to the logs so that the customer knows the likely cause.. See latest comments for details.

Original Description

Hello,

I am unable to install the Magnolia via CLI. Errors added below.

C:\Users\sunoob_k\Documents\HA>mgnl jumpstart
info Using configuration at C:\Users\sunoob_k\AppData\Roaming\npm\node_modules@magnolia\cli\lib\config\mgnl-cli.json
info Using prototypes at C:\Users\sunoob_k\AppData\Roaming\npm\node_modules@magnolia\cli\lib\config\mgnl-cli-prototypes
? What Magnolia would you like to install? magnolia-dx-core-webapp
? Username: skutty
? Password: [hidden]
info No magnolia-version option provided. Will use the latest stable version.
info No path option provided. Will use the default light-modules in the current directory
info C:/Users/sunoob_k/Documents/HA/light-modules does not seem to exist. Path will be created automatically.
ERR! unable to get local issuer certificate
ERR! Error: unable to get local issuer certificate
ERR!     at TLSSocket.onConnectSecure (node:_tls_wrap:1627:34)
ERR!     at TLSSocket.emit (node:events:512:28)
ERR!     at TLSSocket._finishInit (node:_tls_wrap:1038:8)
ERR!     at ssl.onhandshakedone (node:_tls_wrap:824:12)
ERR!
ERR!
ERR! mgnl: 4.0.5 node: v20.4.0 os: win32
ERR! please open an issue including this log on https://jira.magnolia-cms.com/browse/NPMCLI

Regards

Sunoob