Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Installing Yeoman behind a corporate proxy server #587

merged 1 commit into from

3 participants


Installing Yeoman through npm behind a corporate proxy server fails in our case, since Yeoman relies on two tarballs which are loaded through HTTPS.

I have configured the proxy and https-proxy settings in npm, yet still npm is not able to download through HTTPS.

Installing Yeoman fails with the following error:

npm ERR! fetch failed
npm ERR! fetch failed

Changing the two tarball URLs in package.json from HTTPS to HTTP fixes this issue for me.


There is a related issue which should fix this problem #551


Thanks for the reply, but I don't think that this will fix it. The issue is not when using Yeoman to install something, in which case Bower is used and would need Proxy support, but during installation of Yeoman itself (through npm). Npm currently fails to download things via HTTPS through our corporate proxy - that's why changing the tarballs' URLs to HTTP in the Yeoman package info fixes this issue for me.

The issue is not related to Bower - more to npm, which's proxy support seems to be spotty.


@nwinkler I'm not against us pulling this in as a quick fix, but can you file a ticket on NPM to get it fixed for real? And link it up here.


Thanks, will do!


I've filed the following issue with NPM: npm/npm#2866

@sindresorhus sindresorhus merged commit 2869983 into yeoman:master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Oct 5, 2012
  1. @nwinkler

    Changed tarball URLs from HTTPS to HTTP to support installation using…

    nwinkler authored
    … npm from behind a corporate proxy
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 2 deletions.
  1. +2 −2 cli/package.json
4 cli/package.json
@@ -33,8 +33,8 @@
"manpages": "./scripts/docs-build"
"dependencies": {
- "grunt": "",
- "yeoman-generators": "",
+ "grunt": "",
+ "yeoman-generators": "",
"bower": "~0.1.0",
"open": "0.0.2",
"rimraf": "~2.0.1",
Something went wrong with that request. Please try again.