title: NPM install failing with 502 error
body: <p>This is a rather obscure issue. I have an Angular app that will be running through Codeship for CI. However, when it comes time to run <code>npm install</code> on the Codeship box, npm gives back</p>
  
  <pre><code>-npm ERR! fetch failed https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz
  npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 502
  \npm ERR! fetch failed https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz
  npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 502
  \npm ERR! fetch failed https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz
  npm ERR! Linux 4.2.0-38-generic
  npm ERR! argv "/home/rof/.nvm/versions/node/v4.1.1/bin/node" "/home/rof/.nvm/versions/node/v4.1.1/bin/npm" "install"
  npm ERR! node v4.1.1
  npm ERR! npm  v2.14.4
  
  npm ERR! fetch failed with status code 502
  </code></pre>
  
  <p>This was quite strange, since the <code>npm install</code> worked just fine on my box. My first instinct was that it had to be an issue with the NPM repository, so I grabbed the url for the package(<a href="https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz" rel="noreferrer">https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz</a>) and threw it into a new Chrome tab. Sure enough, the archive downloaded almost instantly. I was confused by this, so I tried the Codeship build again, but got the same results. I decided to SSH into the Codeship box to see if I could access it. I ran </p>
  
  <p><code>curl https://registry.npmjs.org/lodash.templatesettings/-/lodash.templatesettings-2.4.1.tgz</code></p>
  
  <p>and as I expected I got the 502 error. However, when I ran the same command from the terminal on my machine, I got the same result, even though the <code>npm install</code> ran perfectly for me. I wasn't able to find anyone else having this type of an issue, and a 502 seems like a very rare code for the NPM registry to be returning. Any ideas?</p>