webdriver-manager update: connect ECONNREFUSED 173.194.221.128:443

[MarkAvreliy]

Hello.

I have a problem with webdriver-manager update:

>webdriver-manager version
[15:18:49] I/version - webdriver-manager 12.0.6
>webdriver-manager update
events.js:163
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED 173.194.221.128: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)

tracert is:

Tracing route to lm-in-f128.1e100.net [173.194.221.128]
over a maximum of 30 hops:

  1     7 ms     5 ms     3 ms  10.233.26.2
  2     2 ms     2 ms     1 ms  145.255.238.129
  3     2 ms     1 ms     1 ms  172.16.98.36
  4     4 ms     4 ms     4 ms  172.16.100.254
  5     4 ms     4 ms     4 ms  172.16.100.252
  6     2 ms     2 ms     1 ms  172.16.100.250
  7     3 ms     3 ms     2 ms  79.142.92.103
  8    31 ms    15 ms    15 ms  193.106.112.103
  9    11 ms    11 ms    12 ms  google-gw.rascom.as20764.net [81.27.254.18]
 10    11 ms    10 ms    11 ms  72.14.233.106
 11    18 ms    18 ms    18 ms  64.233.174.85
 12    27 ms    24 ms    26 ms  74.125.37.253
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23    28 ms    28 ms    28 ms  lm-in-f128.1e100.net [173.194.221.128]

what's wrong? where i have to check a reason? But i think the reason is in outside server (173.194.221.128).

[MarkAvreliy]

now i get problem here Error: connect ECONNREFUSED 172.217.22.176:443
IP address hanges.

[cnishina]

Hmm.... weird. Has webdriver-manager worked for you in the past? What was the last version that worked? Could you try webdriver-manager versions 12.0.3 and 12.0.4? We made some changes around proxy and ignore_ssl and want to rule those out. Thanks!

[MarkAvreliy]

Hello, cnishina.
It's my first time protractor installing.
So i use npm -> protractor install -> webdriver-manager update (for selenium).
I just tried to do step by step as it written here: https://www.youtube.com/watch?v=57134cHJlAs
or here: http://www.protractortest.org/#/tutorial
step: webdriver-manager update
All is the newest one.

[pyalam01]

Hi cnishina : I tried executing webdriver-manager update command with and without ignore_ssl flag on both versions (12.0.3 and 12.0.4) of webdriver-manager and getting "unhandled error event" & "ETIMEDOUT error with different IP addresses. I did a tracert for the displayed IP addresses and request is timing out at destination IP servers.

PS C:\Users\XXXXX\AppData\Roaming\npm> webdriver-manager update
webdriver-manager: using global installed version 12.0.3
[10:30:04] I/file_manager - creating folder C:\Users\XXXXXX\AppData\Roaming\npm\node_modules\webdriver-manager\selenium

events.js:160
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 192.30.253.117:443
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)

PS C:\Users\XXXXX\AppData\Roaming\npm> webdriver-manager update --ignore_ssl
webdriver-manager: using global installed version 12.0.3
events.js:160
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 172.217.6.112:443
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)

PS C:\Users\XXXXXX\AppData\Roaming\npm> webdriver-manager update
webdriver-manager: using global installed version 12.0.4
[10:41:25] I/file_manager - creating folder C:\Users\XXXXX\AppData\Roaming\npm\node_modules\webdriver-manager\selenium

events.js:160
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 172.217.6.112:443
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)

PS C:\Users\XXXXXXX\AppData\Roaming\npm> webdriver-manager update --ignore_ssl
webdriver-manager: using global installed version 12.0.4
[10:42:25] I/http_utils - ignoring SSL certificate
[10:42:25] I/http_utils - ignoring SSL certificate
[10:42:25] I/http_utils - ignoring SSL certificate
events.js:160
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 172.217.6.112:443
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)

Tracert log for the above IP addresses:

C:\Users\XXXXXX>tracert 192.30.253.117
Tracing route to 192.30.253.117 over a maximum of 30 hops
1 1 ms 1 ms 1 ms xxxxxxxxxxxxx.xxxx.com [IP]
2 <1 ms <1 ms <1 ms xxxxxxxxxxxxx.xxxx.com [IP]

3 3 ms 3 ms 3 ms 10.XX.XXX.XX
4 4 ms 3 ms 3 ms xxxxxxxxxxxxx.xxxx.com [IP]
5 4 ms 4 ms 3 ms xxxxxxxxxxxxx.xxxx.com [IP]
6 8 ms 7 ms 8 ms 125.16.224.201
7 41 ms 41 ms 42 ms 182.79.255.22
8 45 ms 44 ms 44 ms xe-0-1-0-9.r00.sngpsi05.sg.bb.gin.ntt.net [116.5
1.27.181]
9 42 ms 43 ms 42 ms ae-10.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.7.
18]
10 234 ms 234 ms 234 ms ae-8.r22.snjsca04.us.bb.gin.ntt.net [129.250.3.4
8]
11 298 ms 298 ms 298 ms ae-7.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.2
38]
12 303 ms 303 ms 303 ms ae-20.r06.asbnva02.us.bb.gin.ntt.net [129.250.2.
133]
13 287 ms 286 ms 287 ms ae-1.a03.asbnva02.us.bb.gin.ntt.net [129.250.5.2
14]
14 272 ms 271 ms 271 ms xe-0-0-24-1.a03.asbnva02.us.ce.gin.ntt.net [128.
241.3.30]
15 * * * Request timed out.
16 * * * Request timed out.
17 263 ms 263 ms 263 ms 192.30.253.117
Trace complete.

C:\Users\XXXXXXX>tracert 172.217.6.112
Tracing route to 172.217.6.112 over a maximum of 30 hops
1 1 ms 1 ms 1 ms xxxxxxxxxxxxx.xxxx.com [IP]
2 <1 ms <1 ms <1 ms xxxxxxxxxxxxx.xxxx.com [IP]
3 3 ms 3 ms 6 ms 10.XX.XX.XX
4 3 ms 3 ms 3 ms xxxxxxxxxxxxx.xxxx.com [IP]
5 5 ms 3 ms 3 ms xxxxxxxxxxxxx.xxxx.com [IP]
6 11 ms 6 ms 8 ms 125.16.224.201
7 25 ms 10 ms 10 ms 182.79.232.169
8 12 ms 12 ms 11 ms 72.14.242.178
9 16 ms 10 ms 11 ms 216.239.56.32
10 44 ms 44 ms 44 ms 216.239.48.227
11 119 ms 119 ms 119 ms 209.85.255.129
12 206 ms 206 ms 206 ms 209.85.142.51
13 209 ms 210 ms 209 ms 72.14.238.84
14 256 ms 256 ms 256 ms 72.14.233.110
15 258 ms 255 ms 255 ms 209.85.251.240
16 * * * Request timed out.
17 252 ms 252 ms 252 ms 108.170.238.91
18 248 ms 248 ms 249 ms 172.217.6.112

Trace complete.

[cnishina]

Could you try the following? Change the /path/to/webdriver-manager/selenium. This could be any folder path. What we are testing is the web calls that webdriver-manager does.

On response retrieval:

curl -o /path/to/webdriver-manager/selenium/chrome-response.xml https://chromedriver.storage.googleapis.com/
curl -o /path/to/webdriver-manager/selenium/standalone-response.xml https://selenium-release.storage.googleapis.com/
curl -o /path/to/webdriver-manager/selenium/gecko-response.json https://api.github.com/repos/mozilla/geckodriver/releases

On download:

curl -o /path/to/webdriver-manager/selenium/chromedriver_2.29.zip https://chromedriver.storage.googleapis.com/2.29/chromedriver_mac64.zip
curl -o /path/to/webdriver-manager/selenium/selenium-server-standalone-3.4.0.jar https://selenium-release.storage.googleapis.com/3.4/selenium-server-standalone-3.4.0.jar
curl -o /path/to/webdriver-manager/selenium/geckodriver-v0.16.1.tar.gz https://github.com/mozilla/geckodriver/releases/download/v0.16.1/geckodriver-v0.16.1-macos.tar.gz

[pyalam01]

@cnishina : All the above web calls are timed out.

[cnishina]

Hmmm.. well, do you have a proxy that you are using? If all the hosts timeout, something must be happening on your end.

[pyalam01]

I tried with and without proxy too, same result. The "unhandled error event" problem with webdriver-manager update and start commands started on May 8th, before that I was able to start and update wendriver-manager and execute my protractor tests successfully. To be precise, until may5th, I didnt experience any issue like this.

[cnishina]

So there was a release on April 24th for 12.0.5 and May 9th there was a release for 12.0.6. So 12.0.5 should work then. Try again 12.0.4 and 12.0.5. Also remove the entire node_modules folder to clear out the webdriver-manager/selenium folder.

[pyalam01]

I uninstalled whole node/npm setup and re-installed protractor globally. Webdriver-manager is installed automatically as a part of protractor module. I ran "webdriver-manager update" command and got "unhandled error event". Now, I executed "webdriver-manager update --ignore_ssl --proxy 'proxyaddress'" and was able to successfully download the binaries.

PS C:\WINDOWS\system32> webdriver-manager update --ignore_ssl --proxy http://proxy----
[15:11:01] I/file_manager - creating folder C:\Users\A591572\AppData\Roaming\npm\node_modules\protractor\node_modules\we
bdriver-manager\selenium
[15:11:01] I/http_utils - ignoring SSL certificate
[15:11:01] I/http_utils - ignoring SSL certificate
[15:11:01] I/http_utils - ignoring SSL certificate
[15:11:03] I/http_utils - ignoring SSL certificate
[15:11:03] I/http_utils - ignoring SSL certificate
[15:11:05] I/http_utils - ignoring SSL certificate
[15:11:07] I/update - chromedriver: unzipping chromedriver_2.29.zip
[15:11:25] I/update - geckodriver: unzipping geckodriver-v0.16.1.zip

PS C:\WINDOWS\system32> webdriver-manager status
[15:13:06] I/status - selenium standalone version available: 3.4.0 [last]
[15:13:06] I/status - chromedriver version available: 2.29 [last]
[15:13:06] I/status - geckodriver version available: v0.16.1 [last]
[15:13:06] I/status - IEDriverServer is not present
[15:13:06] I/status - android-sdk is not present
[15:13:06] I/status - appium is not present

1. I still don't understand, why should we send the proxy flag explicitly in the command when you already have it set in the npm config file ??

2. Now, I executed "webdriver-manager start" command and am getting "unhandled error event with ETIMEDOUT message". I remember reading your comments that we need not have internet/no need of proxy -- inorder to run start command. Could you pls investigate on this and let me know how to resolve this issue.

PS C:\WINDOWS\system32> webdriver-manager start
events.js:163
throw er; // Unhandled 'error' event
^

Error: connect ETIMEDOUT 192.30.253.116: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)

[cnishina]

I am having issues downloading geckodriver from github with a proxy.

Message:
    Error: tunneling socket could not be established, cause=socket hang up
  Stack:
    Error: tunneling socket could not be established, cause=socket hang up
        at ClientRequest.onError (/Users/cnishina/src/proxy-server/node_modules/tunnel-agent/index.js:177:17)
        at ClientRequest.g (events.js:291:16)
        at emitOne (events.js:96:13)
        at ClientRequest.emit (events.js:188:7)
        at Socket.socketOnEnd (_http_client.js:346:9)
        at emitNone (events.js:91:20)
        at Socket.emit (events.js:185:7)
        at endReadableNT (_stream_readable.js:974:12)
        at _combinedTickCallback (internal/process/next_tick.js:74:11)
        at process._tickCallback (internal/process/next_tick.js:98:9)

Could you try:

webdriver-manager update --gecko false --ignore_ssl --proxy http://proxy----

[pyalam01]

Hi - 'update' command downloads selenium, chromedriver, geckodriver binaries if and only if you send @ignoressl and @Proxy flags. I was not having any problem downloading geckodriver with proxy. However, 'webdriver-manager start' command runs chromedriver and selenium server only for the very first time and not later. I verified this by sending ctrl+c - job got terminated and how many ever times I execute 'webdriver-manager start', it shows "unhandled error event". I had to get rid of this error by removing selenium folder, re-download binaries with "update" command and sent start command, as it works for the very first time.

[flyskywhy]

@pyalam01 , no need update before each start, just

touch node_modules/webdriver-manager/selenium/standalone-response.xml
touch node_modules/webdriver-manager/selenium/chrome-response.xml

before each

node_modules/.bin/webdriver-manager start --versions.standalone=3.7.1 --versions.gecko=v0.18.0 --versions.chrome=2.32