cuprite: Can't connect to running Chrome browser session

Environment: macOS 10.13.6 Google Chrome 71.0.3578.98 cuprite 0.4.0 ruby 2.5.0

When running with the following options and already launched Google Chrome:

Capybara.register_driver :cuprite_head do |app|
  Capybara::Cuprite::Driver.new(app, {
    headless: false
  })
end

it raises

RuntimeError:
    Chrome process did not produce websocket url within 1 seconds

It seems Cuprite can’t connect to running Chrome instance, since it outputs Opening in existing browser session instead valid ws url that could be connected to

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 20 (9 by maintainers)

Commits related to this issue

Fix #48 Can't connect to running Chrome browser session — committed to rubycdp/cuprite by route 5 years ago
Fix #48 Can't connect to running Chrome browser session — committed to rubycdp/cuprite by route 5 years ago
Fix #48 Can't connect to running Chrome browser session — committed to saikumar-everest/cuprite by route 5 years ago

Most upvoted comments

Thanks, I sorted it with the following change in my Dockerfile

RUN wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \
  && echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list \
  && apt-get update -qqy \
  && apt-get -qqy install google-chrome-stable \
  && rm /etc/apt/sources.list.d/google-chrome.list \
  && rm -rf /var/lib/apt/lists/* /var/cache/apt/* \
  && sed -i 's/"$HERE\/chrome"/"$HERE\/chrome" --no-sandbox/g' /opt/google/chrome/google-chrome

gregoryduckworth on Feb 12, 2019

@smarquez1

BROWSER_PATH=/path/to/browser bundle exec rspec`

or pass it when instantiating a driver

Capybara::Cuprite::Driver.new(app, browser_path: "/path/to/browser")

route on Apr 6, 2020