16

Since npm dropped support for self signed certs yesterday, I can no longer install any packages from npm running on Windows Azure.

On my local machine I could solve the issue by applying this official fix. However, I couldn't find a way to fix the problem on my site instance. Any ideas?

Improve this question
3
  • Are you using express by chance? I noticed this breaking on the install of express. I updated to allow for any version of express and it resolved the issue. Commented Feb 28, 2014 at 16:18
  • 1
    tried. didn't work. it would be very strange if worked tho. this is a particular issue with npm and their policy change. Commented Feb 28, 2014 at 18:11
  • Yes. It was just dumb luck that my solution worked. Commented Mar 1, 2014 at 1:32

4 Answers 4

Reset to default
11

Since yesterday (Feb 27, 2014) NPM doesn't support self signed certificates anymore: http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more

The solution: either

Upgrade your version of npm

npm update -g

-- or --

Tell your current version of npm to use known registrars

npm config set ca=""

-- or ---

As last resort resolution I don't suggest this for security issues, using SSL is always safer, switch your registry to use HTTP instead of HTTPS:

npm config set registry="http://registry.npmjs.org/"

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

as per description of the problem i have already posted this solution but it only applies to your own installations. Using PaaS services like Azure you don´t have control to npm or the node setup at all.
I should read the description better next time. Sorry. Between you an me a warning of the policy change from NPM would have been great... I guess they will update npm pretty quick on azure, you're not the only one with that issue I'm sure.
Please see my answer for an Azure Web Site workaround.
This command worked for me as I was inside office network--> npm config set registry="registry.npmjs.org"
10

Until we update NPM on Azure, one simple way to work around this is to create a custom deployment script (info here).

Here is a sample repo that demonstrates what to customize: https://github.com/davidebbo-test/AzureNpmCertWorkaround. Specifically, look at this commit, which uses the npm config set ca "" workaround.

If you don't want to deal with generating a custom deployment script using the Azure tool, you can simply grab the .deployment and the deploy.cmd from the test repo, and commit them to the root of your repo.

Improve this answer

Comments

3

You can't run npm install npm -g. npm install being broken is the problem, remember? A good tip from the comments on npm's blog post, worked like a charm:

npm config set strict-ssl false npm install npm -g npm config set strict-ssl true

You may need to use sudo.

Improve this answer

1 Comment

the problem is that we don't have access to the node installation on cloud services like Azure. You just deploy the application without worrying about the backend. You can't run cmds like npm install or config.
0

Error Name: Error: SELF_SIGNED_CERT_IN_CHAIN

Steps to be followed to overcome this error:

1) Update Node.js and npm to its latest version,

2) Run these three commands in a sequence.

 -npm config set strict-ssl false -npm update npm –g -npm config set strict-ssl true

3) Set properties proxy and https-proxy in the npm config using these commands:

 -npm config set proxy “http://<proxy-name>:8080” -npm config set https-proxy “http://<proxy-name>:8080”
Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.