Skip to content
This repository has been archived by the owner on Nov 27, 2020. It is now read-only.

Capybara::Poltergeist::StatusFailError: failed to reach server (but manually I can connect perfectly) #936

Open
jmuheim opened this issue Nov 26, 2020 · 1 comment

Comments

@jmuheim
Copy link

jmuheim commented Nov 26, 2020

Hello

I'm just upgrading a Rails 5 app to Rails 6. Running the specs, I see that all JS-enabled specs fail with the following:

  1) Autocomplete keyboard interaction up options visible moves selection up
     Failure/Error: visit new_page_path
     
     Capybara::Poltergeist::StatusFailError:
       Request to 'http://127.0.0.1:50193/en/pages/new' failed to reach server, check DNS and/or server status - Timed out with no open resource requests
     # /Users/josh/.rvm/gems/ruby-2.6.3@base/gems/poltergeist-1.18.1/lib/capybara/poltergeist/browser.rb:396:in `command'
     # /Users/josh/.rvm/gems/ruby-2.6.3@base/gems/poltergeist-1.18.1/lib/capybara/poltergeist/browser.rb:39:in `visit'
     # /Users/josh/.rvm/gems/ruby-2.6.3@base/gems/poltergeist-1.18.1/lib/capybara/poltergeist/driver.rb:100:in `visit'
     # /Users/josh/.rvm/gems/ruby-2.6.3@base/gems/capybara-3.33.0/lib/capybara/session.rb:278:in `visit'

etc.

This is very strange, because when manually connecting to http://127.0.0.1:50193/en/pages/new (while the spec is still running), I can perfectly connect to this address. I have no idea what's going on and how to debug this problem.

Thank you for any hint.

@twalpole
Copy link
Contributor

Poltergeist went EOL quite some time ago due to the library it depends on only replicating a browser from 8+ years ago. It’s time to move to a newer driver

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

No branches or pull requests

2 participants