search

prrrnd / atom-git-projects

List and open your local Git projects in Atom.
MIT License
37 stars 18 forks source link

Cannot update from 1.8.1 to 1.14.1 - fetch failed https://atom.io/download/atom-shell/nan-1.6.1.tgz #38

Open vtintillier opened 9 years ago

vtintillier commented 9 years ago

I am getting this error log when trying to upgrade.

OS: Windows 7 Atom versions: 0.202.0 and 0.201.0

I tried this both with and without proxy and it does not work in both cases. The only difference is that when used with proxy I get cause=Parse Error instead of cause=connect ECONNREFUSED.

Any idea what could be wrong on my side?

Updating to “git-projects@1.14.1” failed.Hide output…

npm ERR! fetch failed https://atom.io/download/atom-shell/nan-1.6.1.tgz
npm WARN retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=connect ECONNREFUSED
npm ERR! fetch failed https://atom.io/download/atom-shell/nan-1.6.1.tgz
npm WARN retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=connect ECONNREFUSED
npm ERR! fetch failed https://atom.io/download/atom-shell/nan-1.6.1.tgz
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\\Users\\xxxxx\\AppData\\Local\\atom\\app-0.202.0\\resources\\app\\apm\\bin\\\\node.exe" "c:\\Users\\xxxxx\\AppData\\Local\\atom\\app-0.202.0\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\xxxxx\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\xxxxx\\.atom\\.apmrc" "install" "C:\\Users\\xxxxx\\AppData\\Local\\Temp\\d-115428-18184-rqn9qz\\package.tgz" "--target=0.22.0" "--arch=ia32"
npm ERR! node v0.10.35
npm ERR! npm  v2.5.1
npm ERR! code ECONNRESET

npm ERR! network tunneling socket could not be established, cause=connect ECONNREFUSED
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
prrrnd commented 9 years ago

Hi, thanks for reporting your issue. Have you found a way to get it working? It doesn't seem to come from this package.

vtintillier commented 9 years ago

Hi, still no solution found. I tried in a VM at home (so without proxy) but got blocked by #19 as I do not have visual studio.