node-chromedriver: Version 2.25.3 doesn't install when using proxy

Version 2.21.2 installs without problems.

C:\Users\Public\Documents\CYGWIN\home\MyUser\work2\my_app>npm install chromedriver@2.21.2

> chromedriver@2.21.2 install C:\Users\Public\Documents\CYGWIN\home\MyUser\work2\my_app\node_modules\chromedriver
> node install.js

Downloading http://chromedriver.storage.googleapis.com/2.21/chromedriver_win32.zip
Saving to C:\Users\MyUser\AppData\Local\Temp\chromedriver\chromedriver_win32.zip
Receiving...
Received 788K...
Received 1570K...
Received 2353K...
Received 2537K total.
Extracting zip contents
Copying to target path C:\Users\Public\Documents\CYGWIN\home\MyUser\work2\my_app\node_modules\chromedriver\lib\chrome
driver
Done. ChromeDriver binary available at C:\Users\Public\Documents\CYGWIN\home\MyUser\work2\my_app\node_modules\chromed
river\lib\chromedriver\chromedriver.exe
myapp@0.0.3 C:\Users\Public\Documents\CYGWIN\home\MyUser\work2\my_app
`-- chromedriver@2.21.2

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"an
y"} (current: {"os":"win32","arch":"x64"})

However, on the same system installing version 2.25.3 fails:

C:\Users\Public\Documents\CYGWIN\home\MyUser\work2\my_app>npm install chromedriver@2.25.3
npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to np
m

> chromedriver@2.25.3 install C:\Users\Public\Documents\CYGWIN\home\MyUser\work2\my_app\node_modules\chromedriver
> node install.js

Downloading https://chromedriver.storage.googleapis.com/2.25/chromedriver_win32.zip
Saving to C:\Users\MyUser\AppData\Local\Temp\chromedriver\chromedriver_win32.zip
Receiving...
ChromeDriver installation failed Error with http request: { 'content-type': 'text/html',
  'cache-control': 'no-cache',
  'content-length': '2150',
  'proxy-connection': 'Close' }
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"an
y"} (current: {"os":"win32","arch":"x64"})
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "Q:\\105818.000_NODE_JS_441\\nodejs\\node.exe" "C:\\Users\\MyUser\\AppData\\Roaming\\npm\\node_modules\\np
m\\bin\\npm-cli.js" "install" "chromedriver@2.25.3"
npm ERR! node v4.4.1
npm ERR! npm  v4.0.2
npm ERR! code ELIFECYCLE

npm ERR! chromedriver@2.25.3 install: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the chromedriver@2.25.3 install script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the chromedriver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs chromedriver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls chromedriver
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Public\Documents\CYGWIN\home\MyUser\work2\my_app\npm-debug.log

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 2
  • Comments: 27 (11 by maintainers)

Most upvoted comments

@giggio Setting strict-ssl to false didn’t work me either

Can you please have a look at these:

http://stackoverflow.com/questions/10888610/ignore-invalid-self-signed-ssl-certificate-in-node-js-with-https-request https://github.com/nodejs/node/issues/5258#issuecomment-184762392

Is there any way I can temporarily add

process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

to node-chromedriver’s install.js to test it without having to fork the entire repo and creating a copy of the package in npmjs.org?

Maybe through some option?