It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to fix 'unable to connect to chromedriver'

I create one capybara test. It works on local machine but at bitbucket pipeline not.

I set port

Capybara.server_port = 9516

but then the capybara test tries to connect to host with port 9516. 


1) Visit back office The admin can sign in Failure/Error: visit(back_office_path) Selenium::WebDriver::Error::WebDriverError: unable to connect to chromedriver # ./spec/features/home_spec.rb:8:in `block (3 levels) in <top (required)>



gem 'capybara', '~> 3.14.0'
gem 'selenium-webdriver', '~> 3.14.1'
gem 'webdrivers', '~> 3.0'



require 'capybara/rspec'
require 'selenium/webdriver'
require 'webdrivers'

Capybara.register_driver(:headless_chrome) do |app|
capabilities =
chromeOptions: { args: %w[headless disable-gpu] }
browser: :chrome,
desired_capabilities: capabilities

Capybara.javascript_driver = :headless_chrome
Webdrivers::Chromedriver.required_version = '2.46'


Do you have some idea about how to solve it?

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket Pipelines

What We Learned When We Researched Open Source Vulnerabilities in 7 Popular Coding Languages

...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...

1,052 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you