error when starting the app locally: unable to get local issuer certificate

[gluckzhang]

In the master branch (https://github.com/cncf/landscape/tree/9255eb96debdb5acc02816a7c88a5a693c9fa839), when I run ./server.js to start up the app locally, I get the following error:

$ ./server.js
Development server running at http://127.0.0.1:8001/
Starting a new build...
node:events:491
      throw er; // Unhandled 'error' event
      ^

Error: unable to get local issuer certificate
    at TLSSocket.onConnectSecure (node:_tls_wrap:1535:34)
    at TLSSocket.emit (node:events:513:28)
    at TLSSocket._finishInit (node:_tls_wrap:949:8)
    at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:730:12)
Emitted 'error' event on ClientRequest instance at:
    at TLSSocket.socketErrorListener (node:_http_client:481:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY'
}

The same error also appears if I run it in a Docker container: make serve-docker.

I searched a bit and tried with export NODE_TLS_REJECT_UNAUTHORIZED=0, and npm config set strict-ssl false. Neither of them worked in my case. Could you give it a check? Thanks!

The node version I use is: v16.17.1.

[kidbai]

Same problem. It's like:

node:events:505
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)
Emitted 'error' event on ClientRequest instance at:
    at TLSSocket.socketErrorListener (node:_http_client:454:9)
    at TLSSocket.emit (node:events:527:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -54,
  code: 'ECONNRESET',
  syscall: 'read'
}

[tegioz]

Hi!

We've recently migrated the CNCF landscape to v2 and this issue probably no longer applies.

Please feel free to reopen if needed 🙂