vue-cli · tunneling socket could not be established, cause=socket hang up
See original GitHub issuewhen i used vue init webpack demo
it reported this error : " vue-cli · tunneling socket could not be established, cause=socket hang up"
Issue Analytics
- State:
- Created 8 years ago
- Comments:13
Top Results From Across the Web
vue-cli · Failed to download repo vuejs-templates/webpack ...
The reason that works is that you're no longer connecting to the default which uses https , where the SSL is failing due...
Read more >Salesforce DX cli ERROR tunneling socket could not be ...
The cmd window says ERROR: tunneling socket ould not be established, cause=socket hang up. Any guidance would be very much appreciated. November ...
Read more >Error: tunneling socket could not be established, cause ...
Coding example for the question Error: tunneling socket could not be established, cause=socket hang up on running ng e2e Protractor test-angular.js.
Read more >UniversalPackages task fails with socket hang up error behind ...
I will try finding out what changes were made. But I see that web client is not being created to fetch "ArtifactoryTool.exe"; instead...
Read more >npm err! network - You.com | The search engine you control.
npm ERR! code ERR_SOCKET_TIMEOUT npm ERR! network Socket timeout ... ERR! network tunneling socket could not be established, cause=getaddrinfo ENOTFOUND#50.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am still having this problem. I’m using
windows7, vue-cli@2.8.2, npm@5.3.0 and node@8.2.1.
I am behind a corporate proxy and I am able to use npm and git through the proxy. My system environment variables are set as follows
HTTP_PROXY = “http://{IP address}:{port}/” HTTPS_PROXY = “https://{IP address}:{port}/”
The proxy IP and port number in my system environment match the proxy settings I have in my npm config which I verify from the command line with
npm config -g list
and reading bothproxy="http://{IP Address}:{Port}/
andhttps-proxy="https://{IP Address}:{Port}/"
. And yet when I commandvue init webpack vue-xperiment
I receive the error
vue-cli · Failed to download repo vuejs-templates/simple: tunneling socket could not be established, cause=socket hang up
How can I check directly from the command line which proxy settings the vue-cli is trying to use? Because either it isn’t reading from the system environment vars, or else something else is blocking the connection.
For me, I had to make sure the HTTPS_PROXY variable was set. I did it in
~/.zshrc
but you could declare it in~/.bashrc
and then source it, or export it system-wide as well and then open a new terminal window.