Cert error

Open
#515 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, javascript
Domain
cli, cloud, networking

Research direction

Start by reproducing the documented deploy command with --proxy and the shown self-signed certificate error, then trace where proxy and TLS settings are handled. Done means deployments through a proxy with this certificate setup either succeed or the supported certificate configuration and limitation are clearly documented.

Written by the indexing model from the issue text.

Description

question

When trying to deploy, I keep getting a cert error. I am behind a proxy, which i've specified via --proxy "http://myproxy.com:8080". The error is as follows:

Error: self signed certificate in certificate chain
    at TLSSocket.onConnectSecure (_tls_wrap.js:1051:34)
    at TLSSocket.emit (events.js:189:13)
    at TLSSocket.EventEmitter.emit (domain.js:441:20)
    at TLSSocket._finishInit (_tls_wrap.js:633:8)
  message: 'self signed certificate in certificate chain',
  code: 'NetworkingError',
  region: 'us-east-1',
  hostname: 'lambda.us-east-1.amazonaws.com',
  retryable: true,
  time: 2020-01-13T19:42:16.842Z }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! helloworld@1.0.0 deploy: `node-lambda deploy --configFile .env --proxy http://myproxy.com:8080`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the helloworld@1.0.0 deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\myuser\AppData\Roaming\npm-cache\_logs\2020-01-13T19_42_16_905Z-debug.log
Dominant language
JavaScript
Stars
1.4k
Forks
185
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from motdotla/node-lambda

All issues in motdotla/node-lambda

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.