Issues with client.getFile

Hi, I have an issue using client.getFile()

return:

Error: socket hang up

This is the complet error code

events.js:72
throw er; // Unhandled 'error' event
^
Error: socket hang up
at createHangUpError (http.js:1472:15)
at CleartextStream.socketCloseListener (http.js:1522:23)
at CleartextStream.EventEmitter.emit (events.js:95:17)
at tls.js:696:10
at process._tickCallback (node.js:415:13)

npm ERR! shrme.co@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the shrme.co@0.0.0 start script.
npm ERR! This is most likely a problem with the shrme.co package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./bin/www
npm ERR! You can get their info via:
npm ERR! npm owner ls shrme.co
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\Program Files\nodejs\node.exe" "c:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! cwd c:\Users\danjavia\Desktop\Danjavia\virtualhost\shrme_co
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! c:\Users\danjavia\Desktop\Danjavia\virtualhost\shrme_co\npm-debug.log
npm ERR! not ok code 0

Start by reproducing the failure in client.getFile() using the reported Windows_NT 6.1.7601 and Node v0.10.26 environment, then inspect the socket hang-up stack trace and npm-debug.log. Confirm the conditions that cause node ./bin/www to exit and document a reproducible fix or a clear explanation of the failure.

Written by the indexing model from the issue text.