Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

update failing with --ignore_ssl in Node 8.12.0

See original GitHub issue

Since updating to Node 8.12.0 / npm 6.4.1, webdriver-manager update --ignore_ssl has been failing for us:

[11:03:04] I/file_manager - creating folder ...\hpc-breadcrumb\node_modules\protractor\node_modules\webdriver-manager\selenium
[11:03:04] I/http_utils - ignoring SSL certificate
[11:03:04] I/config_source - curl -ok ...\hpc-breadcrumb\node_modules\protractor\node_modules\webdriver-manager\selenium\standalone-response.xml https://selenium-release.storage.googleapis.com/
[11:03:04] I/http_utils - ignoring SSL certificate
[11:03:04] I/config_source - curl -ok ...\hpc-breadcrumb\node_modules\protractor\node_modules\webdriver-manager\selenium\chrome-response.xml https://chromedriver.storage.googleapis.com/
[11:03:04] I/http_utils - ignoring SSL certificate
[11:03:04] I/http_utils - ignoring SSL certificate
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TLSWrap.onread (net.js:622:25)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! hpc-breadcrumb@3.0.5 update-webdriver: `webdriver-manager update --ignore_ssl --gecko false`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the hpc-breadcrumb@3.0.5 update-webdriver script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     ...\AppData\Roaming\npm-cache\_logs\2018-10-16T15_03_04_629Z-debug.log

If I switch back to node 8.11.2, it works.

Issue Analytics

State:
Created 5 years ago
Comments:14 (4 by maintainers)

Top GitHub Comments

4reactions

markleppkecommented, Oct 22, 2018

I can confirm if I roll back to Node 8.11.4 it works for me. Unfortunately, our team needs move to 8.12.0.

1reaction

vort3xxxcommented, Oct 16, 2018

If I use --alternate_cdn with a non-https url, it works. All https-based cdns fail with node 8.12.

Note that this fails both inside and outside of my local network, including on Azure Devops hosted build agents running the Visual Studio 2017 hosted container.