Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support request: Possibility to change Chromedriver port? #609

Open
jepster opened this issue Mar 12, 2019 · 1 comment
Open

Support request: Possibility to change Chromedriver port? #609

jepster opened this issue Mar 12, 2019 · 1 comment

Comments

@jepster
Copy link

jepster commented Mar 12, 2019

Locally Wraith runs very well for me. I am running the latest Wraith version in my CI pipeline with Docker containers. Is there any chance to change Chromedriver port in settings? Have not found any documentation about that. Because I am getting the following errors from Wraith (see the part with "ERROR: unable to connect to chromedriver 127.0.0.1:9515"):

DEBUG: #################################################
DEBUG: Command run: latest configs/history.yaml
DEBUG: Wraith version: 4.2.3
DEBUG: Ruby version: ruby 2.3.3p222 (2016-11-21) [x86_64-linux-gnu]
DEBUG: ImageMagick: Version: ImageMagick 6.9.7-4 Q16 x86_64 20170114 http://www.imagemagick.org
DEBUG: PhantomJS version: PhantomJS not installed
DEBUG: chromedriver version: chromedriver not installed
DEBUG: CasperJS version: CasperJS not installed
DEBUG: #################################################
Config validated. No serious issues found.
Creating Folders
SAVING IMAGES
ERROR: unable to connect to chromedriver 127.0.0.1:9515
WARN: Using fallback image instead
ERROR: unable to connect to chromedriver 127.0.0.1:9515
WARN: Using fallback image instead
ERROR: unable to bind to locking port 9514 within 45 seconds
WARN: Using fallback image instead
ERROR: unable to bind to locking port 9514 within 45 seconds
WARN: Using fallback image instead
ERROR: unable to connect to chromedriver 127.0.0.1:9515

My Chromedriver is running on port 4444. That's the default one. I find it weird that Wraith is trying to connect to port 9514.

@khana25
Copy link

khana25 commented May 2, 2019

Delete the chrome browser and try to delete the whole 'Google' folder from the following folder: C:\Users<user_name>\AppData\Local\Google and from the following folder: C:\Program Files (x86)\Google and then download a fresh copy of google chrome browser and chromedriver

Hope it will sort out your issues which I had them previously !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants