Closed cmpsoares91 closed 7 years ago
I have just come across this too, using yarn
to install rather than npm
, but the same error.
$ yarn
yarn install v0.23.4
info No lockfile found.
.........
error C:\Data\Node\electron-quick-start\node_modules\electron: Command failed.
Exit code: 1
Command: C:\Windows\system32\cmd.exe
Arguments: /d /s /c node install.js
Directory: C:\Data\Node\electron-quick-start\node_modules\electron
Output:
C:\Data\Node\electron-quick-start\node_modules\electron\install.js:47
throw err
^
Error: connect ECONNREFUSED 192.30.253.113:443
at Object.exports._errnoException (util.js:1050:11)
at exports._exceptionWithHostPort (util.js:1073:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1093:14)
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this
command.
Please re run the install command with --verbose
You need to configure your proxy to allow connections to github.com
@zeke that's not the most helpful response - I believe most people running into this issue won't have the admin powers required to make changes to the proxy itself. Better to work out what the missing git, npm or node config settings are.
@voltagex sorry for the brevity. @cmpsoares91 without knowing the particulars of your network setup, the best thing I can recommend is to run npm install
while connected to a network that can access github.com and npmjs.com.
Hi,
I am also facing same issue in my build environment. Is there any solution for this problem. I have no idea about that build host the only info i know about the host is it is linux. Dont have any admin rights on that host.
Thanks Jk
Hello I'm trying to perform
npm install
but this is giving me a connection error:To contextualise we're in a corporate workspace which is under firewall and proxy configurations, thus I've configured our nexus server as the npm registry (it's proxying it and works fine). However, when I try to install the electron dependency it crashes with the error mentioned above.
I have tried some proxy configurations but I don't know why it did not work, I would like to instead try to understand why Electron is trying to reach Github and if it is possible to work around it and work only with the NPM repo?
Best regards, Carlos Soares.