Save time managing and deploying your node.js app

Nodejitsu has joined GoDaddy

We are excited to join GoDaddy to help spearhead their largest Node.js product: Website Builder. Please read our blog post to learn more about customer transition plans and our continued support for Open Source within the node community.

Want to know all the details?
Read the full blog post or read the GoDaddy Announcement.

Improved SSL experience for private npm

About the author

nodejitsu nodejitsu

Other popular posts

- Scaling Isomorphic Javascript Code - Keep a node.js server up with Forever - Package.json dependencies done right
- npm cheat sheet - 6 Must Have Node.js Modules

Last night we deployed shiny new SSL certificates to all machines serving HTTP(S) requests for private npm registries. e.g.:


TLDR? Update your local npm CLI configuration for your private npm registry:

npm config set strict-ssl true  
npm config set ca ""  

The above tells the npm CLI to trust all well-known CAs (Certificate Authorities), such as DigiCert (our CA) in a strict way.

How did it work before?

Up until now our private npm SSL had used the same SSL certificate as our PaaS product matching URLs like:


As some of you might know, multi-level wildcard SSL certificates do not exist so this forced you to set strict-ssl false when making requests.

Anything else?

Nope that's it! Easy right? We've got some bigger features in our pipeline that will be shipping in the next few weeks. April is going to be a big month for us!