Proxy / ECONNRESET issue

[dougajmcdonald]

Hi there,

After installing the trying to run a deployment, my deployment log wigs out and reports a whole series of proxy errors.

E.g.

npm ERR! network read ECONNRESET
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'
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "D:\\Program Files (x86)\\nodejs\\0.12.6\\node.exe" "D:\\Program Files (x86)\\npm\\3.3.9\\node_modules\\npm\\bin\\npm-cli.js" "install" "--no-optional" "--no-bin-links" "ember-cli"
npm ERR! node v0.12.6
npm ERR! npm  v3.3.9
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read

Any thoughts? I can post more info / logs if it helps.

[dougajmcdonald]

In case it helps anyone else who stumbles across this one, I resolved the ECONNRESET issues by changing the node version in the deploy.sh from 0.12.7 to 4.6.0.

I now get issues re: EPERM operation not permitted when doing some symlink stuff:

Build the dist folder
Executing "ember build -prod". This might take a while.
DEPRECATION: Node v0.10.28 is no longer supported by Ember CLI. Please update to a more recent version of Node

Running without elevated rights. Running Ember CLI "as Administrator" increases performance significantly.
The Broccoli Plugin: [Funnel: Funnel: index.html] failed with:
See ember-cli.com/user-guide/#windows for details.

Error: EPERM, operation not permitted 'D:\local\Temp\8d3ed6166d620cf\app'
Build failed.
    at Object.fs.symlinkSync (fs.js:730:18)

I will continue to investigate

[teltploek]

@dougajmcdonald: Did you get closer to a solution to that last one?