[ACCEPTED]-unable to connect to chromedriver http://127.0.0.1:9515 (Selenium::WebDriver::Error::WebDriverError)-capybara
I had this issue because of path override 2 with rbenv shim.
It's worth checking where 1 which chromedriver points too.
For me the fix was:
gem uninstall chromedriver-helper and brew install chromedriver
If you using rbenv on linux machine then 5
copy 'chromedriver' to current using ruby 4 versions like below -
cp chromedriver $HOME/.rbenv/versions/2.2.0/bin
Example: cp 3 chromedriver home/abc_user/.rbenv/versions/2.2.0/bin
and 2 then set the permissions like -
chmod +x 1 home/abc_user/.rbenv/versions/2.2.0/bin/chromedriver
Open Terminal: brew link --overwrite chromedriver
0
I have encountered after installation of 4 ansicon1.60 for colourful screen. After 3 uninstalling it by the following command 2 in ansicon directory:
C:\Users\Administrator\Downloads\x64>ansicon.exe -i
after that, i decided 1 not to use ansicon.
If you have rbenv concerns problem, you 1 may try:
$ rbenv rehash
and then run your test again. ;)
ChromeDriver setup in Linux [Ubuntu]
Open Terminal and download Chromedriver 2 using the cmd
$ wget http://chromedriver.storage.googleapis.com/2.7/chromedriver_linux64.zip
$ Unzip chromedriver_linux64.zip
$ cp 1 chromedriver /usr/local/bin
$ chmod +x /usr/local/bin/chromedriver
Do not use ansicon1.60 for colourful screen.
Run 4 cmd /d which starts the command prompt without 3 processing its AutoRun entry, thus bypassing 2 ANSICON. Then you should just be able to 1 do \x64\ansicon -u.
More Related questions
We use cookies to improve the performance of the site. By staying on our site, you agree to the terms of use of cookies.