Error with start Error: connect ETIMEDOUT 192.30.253.113:443

Ionic Framework ionic-v3
1 
$ npm config list
; cli configs
user-agent = "npm/3.8.3 node/v5.10.1 win32 x64"

; userconfig C:\Users\Shanmuga Sundaram\.npmrc
http-proxy = "http://xx.xx.xx.x:8080"
https-proxy = "http://xx.xx.xx.x:8080/"
https.proxy = "http://xx.xx.xx.x:8080"
proxy = "http://xx.xx.xx.x:8080/"
registry = "http://registry.npmjs.org/"
strict-ssl = false

; globalconfig C:\Users\Shanmuga Sundaram\AppData\Roaming\npm\etc\npmrc
strict-ssl = false

; builtin config undefined
prefix = "C:\\Users\\Shanmuga Sundaram\\AppData\\Roaming\\npm"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = C:\wamp64\www\ionic
; HOME = C:\Users\Shanmuga Sundaram
; "npm config ls -l" to show all defaults.



$ ionic start MyIonic2Project tutorial --v2
Creating Ionic app in folder C:\wamp64\www\ionic\MyIonic2Project based on tutorial project
Downloading: https://github.com/driftyco/ionic2-app-base/archive/master.zip
Error with start Error: connect ETIMEDOUT 192.30.253.113:443
    at Object.exports._errnoException (util.js:890:11)
    at exports._exceptionWithHostPort (util.js:913:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1059:14)
Error Initializing app: Error: connect ETIMEDOUT 192.30.253.113:443
 Error: connect ETIMEDOUT 192.30.253.113:443
    at Object.exports._errnoException (util.js:890:11)
    at exports._exceptionWithHostPort (util.js:913:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1059:14)
Caught exception:
 Error: connect ETIMEDOUT 192.30.253.113:443
    at Object.exports._errnoException (util.js:890:11)
    at exports._exceptionWithHostPort (util.js:913:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1059:14)
2

try uninstall the app and if u use -l -c try without

3

The following command works for me thanks,

PROXY=http://xx.xx.xx.x:8080 ionic start --list --v2

1 Like
4

there are many problem, just same i have received, but i am in open network the so i have cleaned my npm cache clean now it’s working fine.

  • npm cache clean
  • set proxy if you are behind the proxy server
  • check for the netwrok block

:slight_smile: