I am getting the following error below when trying to start webdriver-manager.
It is working yesterday, after restarting it today, I am now getting a certificate error.
I enter --ignore_ssl, added proxy/https-proxy on User Variables and I already tried running the cmd as an administrator.
Error:
C:\Users\<user>\AppData\Roaming\npm>webdriver-manager start --ignore_ssl
events.js:160
throw er; // Unhandled 'error' event
^
Error: unable to get local issuer certificate at Error (native)
at TLSSocket.<anonymous> (_tls_wrap.js:1092:38)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at TLSSocket._finishInit (_tls_wrap.js:610:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38)
When updating, I was able to update successfully without an error.
Fixed in webdriver-manager 12.0.5+:
This was an actual issue with webdriver-manager and was tracked as issue #229. On start, webdriver-manager would check the cache and if the cache was old, it would replace it. The problem identified above is that the ignore_ssl and proxy flags were not being passed.
The real issue is that webdriver-manager start should not be making any web requests. Removing web requests removed the need to pass the ignore_ssl and proxy flags around. So if a user were to test their web app locally on an airplane, starting the selenium server should still work.
Anyway, this has been resolved in PR #232 and we should have a new release (12.0.5) later today.
Update:
webdriver-manager version 12.0.5+ should have this fixed. The latest as of this update is 12.0.6. You can check what version you have installed with webdriver-manager version.
webdriver-manager version
webdriver-manager: using global installed version 12.0.5
[08:18:51] I/version - webdriver-manager 12.0.5
Troubleshooting
Potential errors could include having an old installed global version although you have installed a project dependency with the correct webdriver-manager version.
How do I know start makes no web requests? Well, other than unit tests, I have tried this out by turning off wifi and trying webdriver-manager start. If start fails for you at this point with no internet, please check your version.
webdriver-manager start --ignore_ssl
this will work for you.
Related
I have an Apple M1 using macOS Monterey and I am trying to install MongoDB community latest version. After following the documentation on the website I received this error message (note: I am using a Rosetta terminal because M1 chips do not support homebrew). Does anyone know what is happening with this error? Please help.
What I have tried:
stopping and restarting the service and again it does not work when I then type "mongo" or "mongosh" I get an error to refuse to connect.
I also tried uninstalling and reinstalling many times.
Possible error is the line Already downloaded: /Users/katejohnson/Library/Caches/Homebrew/downloads/5bd79f1c70119d0cda4b01fc074ad77ad00a7e8dfc9b243016157d9ee7009874--mongosh-1.3.1.bottle_manifest.json When I download it (see terminal screenshot)
brew services start mongodb-community#5.0
Bootstrap failed: 5: Input/output error
Try re-running the command as root for richer errors.
Error: Failure while executing; `/bin/launchctl bootstrap gui/501 /Users/katejohnson/Library/LaunchAgents/homebrew.mxcl.mongodb-community.plist` exited with 5.
Terminal screenshot
Restart your macOS. Run brew services start mongodb-community#5.0. It should fix the problem!
The issue is with the .plist file that needs to be present in LaunchAgents directory for launchctl to run mongod service on startup.
While launching conf.js file in protractor its giving below error :
ERROR [OsProcess.checkForError] - org.apache.commons.exec.ExecuteException: Execution failed (Exit value: -559038737. Caused by java.io.IOException: Cannot run program "/usr/local/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_87.0.4280.88" (in directory "."): error=86, Bad CPU type in executable)
https://github.com/angular/webdriver-manager/issues/476
Fix will be available soon this weekend. but you will get a workaround by doing this.
As I badly needed to get unblocked - here is a hacky workaround for anyone in similar situation (only for x86_64 macOS). In node_modules/webdriver-manager/built/lib/files/file_manager.js update fileUrl.url around 166:
add below line
fileUrl.url = fileUrl.url.replace(/_m1/, '')
Was facing the similar issue in MacOs Catalina.
This is how it got resolved for me with below versions :
Option 1 :
Download these :
https://chromedriver.storage.googleapis.com/71.0.3578.33/chromedriver_mac64.zip
https://selenium-release.storage.googleapis.com/3.14/selenium-server-standalone-3.14.0.jar
And made the Selenium server UP with this :
java -Dwebdriver.chrome.driver=./chromedriver_71.0.3578.33 -jar ./selenium-server-standalone-3.141.59.jar -port 4444
Option 2 :
Protractor :
Use the below versions :
webdriver-manager update --versions.chrome=71.0.3578.33
webdriver-manager --versions.chrome=71.0.3578.33 start
Got an Error
"Timed out waiting for driver server to start." After running
webdriver-manager update
Resolved it by downgrading to the previous version of webdriver that was working for you.
Steps:
navigate to node_modules/protractor/node_modules/webdriver-manager/selenium/
check if you can see the last chromedriver that you were using before the update
for my case this is chromedriver_86.0.4240.22
since I still have my previous chromedriver, I just Deleted
chromedriver_87.0.4280.88
chromedriver_87.0.4280.88.zip
in node_modules/protractor/node_modules/webdriver-manager/selenium/update-config.json
I changed all instances of chromedriver_87.0.4280.88 and replaced with chromedriver_86.0.4240.22
Run your tests.
Incase you dont know what was the last version that worked for you, you can try
webdriver-manager update --versions.chrome=86.0.4240.22
or look for a version here
This is what worked for me:
Update the protractor version to current stable version: "protractor": "^7.0.0", npm install was the way to go for me, yours will be similar
Update the webdriver: webdriver-manager update with or without sudo is the right command as stated in other answers
Run the webdriver manager with the current chrome version, this is the command that I use for application: webdriver-manager start --versions.chrome=88.0.4324.96 as my chrome is currently at that version, replace it with your chrome's version (87.0.4280.88 as per the question)
I have this problem for a few day and I have noticed that chromedriver version has been upgraded automaticlly to the 86. So I am guessing I need to downgrade it to 84. But I am not sure. May be I should upgrade something but I do not know what. My webdriver-manager vesrion is "webdriver-manager": "^12.1.7",
Any hints, please?
Try the below command to resolve the webdriver update issue
node node_modules/protractor/bin/webdriver-manager update --versions.chrome=<desired chrome version> --standalone --gecko=false --ignore_ssl
Try this if you want to run on chrome browser.
In protractor sometime gets Error: ”Session not created ” because of not supported/incompatibility driver version for current browser version.
I have tried below steps:
Step 1: Delete selenium folder inside webdriver-manager .
All browser driver should be presented in this folder.
Path: ..\node_modules\protractor\node_modules\webdriver-manager\selenium
Step 2: node node_modules/protractor/bin/webdriver-manager update - This will download all browser driver versions inside selenium folder.
Or else you can update webdriver-manager with specific version you want.
node node_modules/protractor/bin/webdriver-manager update --versions.chrome=XX.X.XXXX.X
I managed to get the latest Yarn v1.13.0 installed on Xubuntu 16 with their curl installation instruction.
Now I'm getting this errors trying to install a project's dependencies.
An expected error occurred:
"https://registry.yarnpkg.com/event-stream/-/event-stream-3.3.6.tgz:
Request failed \"404 Not Found\
Same 'Not Found' message is displayed by the error url.
Seems to be caused by the security issue https://github.com/dominictarr/event-stream/issues/116?utm_content=educational&utm_campaign=2018-11-28&utm_source=email-sendgrid&utm_term=13952972&utm_medium=833442
How do I fix it? How do I find the project deps that use the corrupted version of event-stream?
Seemingly was caused by an older version of Nodemon prolly affected by the security issue above. Updating it to the latest version in package.json seemed to have helped.
I use Modulus.IO to deploy my Meteor app.
When I am on the development environment there is no problem at all, not in the 'meteor' console nor in the browser js console. But when I deploy it to Modulos.IO, this error appears in Modulus:
Error: Can't find npm module 'uglify-js'. Did you forget to call 'Npm.depends' in package.js within the 'minifiers' package?
at Object.Npm.require (/mnt/data/1/programs/server/boot.js:106:17)
at Package (packages/minifiers/minifiers.js:1)
at packages/minifiers.js:307:4
at packages/minifiers.js:317:3
at /mnt/data/1/programs/server/boot.js:155:10
at Array.forEach (native)
at Function._.each._.forEach (/mnt/data/1/node_modules/underscore/underscore.js:79:11)
at /mnt/data/1/programs/server/boot.js:82:5
[2014-05-16T11:48:10.665Z] Application CRASH detected. Exit code 8.
[2014-05-16T11:48:12.326Z] Application restarted.
/mnt/data/1/programs/server/boot.js:186
}).run();
I have no minifiers package installed and no underscore.js as well.
Ok, good news.
That was some error between NPM and Modulus module version.
I've uninstalled NPM, Modulus module and stopped the deploy environment.
Then installed the latest version of NPM and installed the latest version of Modulus module.
Finally, I've made the deploy again and it's everything ok.
Thanks for all the attention.
P.S.: Remember to install Modulus module globally (-g).