webdriver-manager update command throws unhandled error. #239
Comments
|
Are you behind a firewall? This looks like you are trying to do the https call to the selenium-release.storage.googleapis.com or chromedriver.storage.googleapis.com. A good way to test this is browsing to: https://chromedriver.storage.googleapis.com/ If you are behind a proxy, then you should use the following flags: |
cnishina
added
pr: needs author response
status: needs more info
and removed
pr: needs author response
labels
|
I am able to browse: I can see XMLs on hitting above links. C:**>webdriver-manager update --ignore_ssl Error: connect ETIMEDOUT 192.30.253.117:443 Can you please let me know the exact command to ignore ssl and other proxy option you mentioned above. |
|
Any comments? |
|
Hi, I am also facing the same issue. I tried to execute "webriver-manager update" with corporate proxy and without proxy too and I am seeing the same unhandled error event. I tried tracert to the googleapis and the trace was completed without any issues. Node : v6.10.3 PS C:\WINDOWS\system32> webdriver-manager update events.js:160 Error: connect ETIMEDOUT 192.30.253.116:443 Troubleshoot method 1 : I tried to debug the issue by manually installing selenium server jar and chromedriver exe through npm install (npm install -g seleniumxxxxxx.jar and chromedriver). selenium server jar download was successful and to my surprise, chromedriver was throwing the following error. C:\Users\XXXXXXXX\AppData\Roaming\npm\chromedriver -> C:\Users\XXXXXXXX\AppData\Roaming\npm\node_modules\chromedriver\bin
Downloading https://chromedriver.storage.googleapis.com/2.29/chromedriver_win32.zip npm ERR! chromedriver@2.29.0 install: Troubleshoot method 2 : I downloaded the jar and chromedriver exe (3.4.0 jar and 2.29) from cdn urls to selenium folder manually and exceuted "webdriver-manager status" command and got the below output. PS C:\WINDOWS\system32> webdriver-manager status Now I executed "webdriver-manager start" command and getting the same unhandled event error. PS C:\WINDOWS\system32> webdriver-manager start Error: connect ETIMEDOUT 216.58.216.208:443 Could someone look into this issue. |
|
@AdityaDaksha This is a network environment issue. I cannot reproduce your error on my end just with the ignore_ssl flag. @pyalam01 I would ask about your network setup. I have not tried the chromedriver node module. If both are having issues, I would see if you need to pass additional flags if you are behind a corporate proxy. |
|
@cnishina : Yes, I am behind a corporate proxy, so I tried with and without proxy too but no luck. By passing --ignore_ssl flag, here is what I see. |
|
I get the same problem as pyalam01. I am behind corporate proxy and I took the same route of downloading chromedriver_2.29.exe and selenium-server-standalone-3.4.0.jar manually and place them on the selenium folder of protractor\node_modules\webdriver-manager\selenium when trying to update.. Here's the error when I start webdriver-manager |
|
@pyalam01 I had the same issue, but then when I used the proxy switch too, eg webdriver-manager: using global installed version 12.0.6 |
|
@AdityaDaksha see my comment above, replace with your proxy ip and port number |
|
now I'm getting similar to @jnal node:14044) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: response status code is not 200. It was 503 |
|
I am also experiencing what @jnal and @stevegraygh are experiencing. Did either of you find workarounds? After running It hangs for a few minutes after the final update before the rejected promise. |
|
I believe this is related to an issue I'm working through on geckodriver. #257. I haven't had much time to debug this so for now:
This is definitely something around GeckoDriver downloading from Github. I almost have a working test that can duplicate this set up. |
|
I have the same issue, and is caused by our corporate proxy requiring a custom certificate be installed so monitoringcan man in the middle all https requests for "security". |
|
I am facing the same issue as well, anyone found resolution yet? |
|
@stevegraygh Thanks. Both the webdriver-manager update && webdriver-manager start are working fine, when i use them as below. webdriver-manager update --ignore-ssl --proxy http://XXX.XXX.XXX:80 |
|
I am using internal nexus repo and can not get it working. I try to configure ".npmrc" to get it from local path but still face same unhandled error, did i missed anything? chromedriver_filepath=D:\temp/chromedriver/chromedriver_win32.zip |
|
I am running webdriver-manager start under corporate proxy (no internet) and we don't have a proxy provided, we are geeting the same error as below. Is there way to start webdriver-manager without proxy to test an intranet application ? events.js:160 |
|
The command |
|
run your command as administrator may also help :) |
|
in my case, it was because Google has been blocked its web server for my region (Iran). using a proxy fixed it. |
|
I'm also facing the same issue - the proxy blocks access to the resource. I copied appropriate files (web drivers and selenium-server) from the machine that is in different proxy. However it is not resolving my issue. Will it be possible to either:
|
|
Anyone has been able to use webdriver-manager behind a firewall without proxy? |
|
@kedziorm Please try out https://github.com/cnishina/webdriver-manager-replacement. A lot more testing went around how update and start works. Previously I had the start command refresh to update just in case it wasn't fresh. My replacement does not make web calls at all during start. It is currently a work in progress and limited to running |
|
@MichelleGuoFRB I am not sure about your firewall. Wouldn't you just add an exception for trusted URLs? If you try to download one by one (download just ChromDriver |
|
@cnishina Thank you! My bowser can access those URLs, so I will addthose URLs in and try it. Another question is: I tried it from a public computer, it worked all fine without issue, just following Protractor page worked. However, when I put that computer in airplane mode, webdriver-manager doesn't start any more does it need to stay with internet connection in order to start webdriver-manager? |
|
Oh no! I think this is a known bug. Please try out this one instead: https://github.com/cnishina/webdriver-manager-replacement. See the above notes on limitations. I am looking for feedback. If it is broken, I want to fix the replacement. |
|
@cnishina I download the zip and ran install with 'npm i -D Webdriver-manager-replacement' and it finished install. When I tried to run 'webdriver-manager start', I got this error: (node:14088) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory |
|
@MichelleGuoFRB in your script for your project, make sure you are using webdriver-manager-replacement: Then you can do the following: You will also need node 8. |
|
@cnishina thanks. Did you mean like below? Is this part of the conf.js? "scripts": { Would modeJS 10 not good? |
|
That would work too (in the above script code snippet). Sorry I meant to say greater than node 8. Wow, are we on node 10 already? |
|
@cnishina yes the most recent node.js is version 10. I am new to Protractor. I followed the instruction fro protractor page https://www.protractortest.org/#/. It is pretty straight forward to follow. The issue is that step 'webdriver-manager update' had errors since it is trying to access external IPs which my network doesn't allow. I appreciate that you brought webdriver-manager-replacement, but the command 'npm run webdriver-manager-replacement update', it doesn't run. This is Windows environment. Could you provide the procedures for getting webdriver-manager launched on localhost:4444 using webdriver-manager-replacement, which is what the purpose for having webdriver-manager, so protractor can talk to it |
|
In your above script: You should run: |
|
Yes, we can run webdriver-manager without proxy. When you run webdriver start, firstly it would try to update and start. When it tries updating it requires internet. |
|
This worked for me based on above comments: First run: Then: Strangely, it didn't work if I do: |
|
If you are behind Corporate proxy then do below. webdriver-manager update --proxy http://my-proxy.com:8000 --ignore_ssl |
|
I had the exact same problems, not being able to update, having ssl and proxy errors.
|
|
Make sure to check your |
|
Closing this disucssion. webdriver-manager-replacement is now webdriver-manager 13. The original issue has been resolved. |
is there any fix for this for 12.1.7? webdriver-manager 13 is not available yet as far as I can tell. |
|
I was facing a similar issue with the update. When I was scratching my head looking at all possible solutions on online forums, I was doing it sitting it at my office desk using the corporate WiFi. I tried resuming doing it at home using personal WiFi. It worked. So, if you are in the same boat, my suggestion would be to connect it to a non-corporate network and try it. |
|
I'm facing the same issue. I'm behind a corporate network and webdriver-manager update does not work. However when connected to home network it works fine. What needs to be done to get it working in corporate network?? |
|
@cnishina The binaries got downloaded and the selenium server started on 4444. But now when i'm trying to run the test cases
|
and others
C:**>webdriver-manager update
events.js:160
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 172.217.7.16:443
at Object.exports._errnoException (util.js:1022:11)
at exports._exceptionWithHostPort (util.js:1045:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1087:14)
C:**>webdriver-manager version
[19:52:31] I/version - webdriver-manager 12.0.4
C:**>protractor --version
Version 5.1.1
C:**>ng -v
@angular/cli: 1.0.0-rc.1
node: 6.10.0
os: win32 x64
@angular/common: 2.4.9
@angular/compiler: 2.4.9
@angular/core: 2.4.9
@angular/forms: 2.4.9
@angular/http: 2.4.9
@angular/platform-browser: 2.4.9
@angular/platform-browser-dynamic: 2.4.9
@angular/router: 3.4.9
@angular/cli: 1.0.0-rc.1
@angular/compiler-cli: 2.4.9
The text was updated successfully, but these errors were encountered: