Replies: 1 comment 5 replies
-
So I noticed this when running "npm install"
|
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently running Verdaccio 5.7.1
On my personal computer with open internet, I can run npm install and npm audit with no issues.
I installed Verdaccio on AWS Linux behind our corporate firewall. Had to set environment variable "export NODE_EXTRA_CA_CERTS=/location/of/ca/cert" in order for me to be able to make "npm install --registry http://localhost:4873" to work.
Everything appears to be working except for when running "npm audit --registry http://localhost:4873"
I've tested with and without "strict_ssl: false" and still didn't work.
Directly from the AWS instance hosting Verdaccio, if I do a "npm cache clean --force" and remove package-lock.json and node_modules, I can run "npm audit --registry https://registry.nodejs.org" with no issues. So I know the firewall isn't blocking traffic. It's only when using Verdaccio from the same instance does it not work.
Is there something else I'm missing in the configuration file to make this work with corporate CA cert?
Config.yml
Output from cmd when running npm audit
logfile from /home/ec2-user/.npm/_logs/
Beta Was this translation helpful? Give feedback.
All reactions