-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Cypress cannot open firefox - getaddrinfo EAI_AGAIN error #31230
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
Comments
|
@MikeMcC399 |
I tried with Firefox 102esr
|
Can you please say which operating system you are using? Windows 11 perhaps? |
@MikeMcC399 |
Since cypress@13.15.1 released Oct 24, 2024:
So if you were testing one year ago, you would have been using a version of Cypress which did not use the geckodriver. The npm package geckodriver by default dynamically downloads and caches an architecture-dependent geckodriver from GitHub. This default behavior requires an Internet connection. You may be able to work around this issue in an air-gapped environment by downloading the geckodriver from the releases page and then unzipping the This is something that you might like to try. Regarding browser versions - independent of the geckodriver / air-gap issue: Firefox 128 from the Rapid Release Channel is no longer supported by Cypress, although judging by the fact that Firefox 128 ESR still works, I would expect Firefox 128 in general also to work. Firefox 102 ESR entered End-of-Life in Sep 2023. It is no longer supported by Firefox, nor by Cypress. Don't try to use this version with current versions of Cypress. |
Thanks, it works better with geckodriver workaraound but I still get errors
I debugged Firefox launch preferences (launchOptions)
|
I have also seen these errors occurring. I wasn't able to track down the reason, so it will need some input from the Cypress.io team. |
I completely deleted the Cypress folder in AppData/Roaming and opened Cypress. When I select the Firefox browser, it launches directly instead of a Cypress instance (error "Still waiting to connect to Firefox"). I hope there is a solution to this issue |
In fact, it seems Cypress instantiation is not complete. |
I wasn't able to reproduce the issue at will although I have seen it happening when trying to simulate an air-gapped environment. Using the follow steps shows Cypress On Windows 11 24H2, Node.js In Git Bash terminal with Internet connection: git clone https://github.com/cypress-io/cypress-docker-images
cd cypress-docker-images
cd examples/basic
rm -rf $APPDATA/Cypress # remove cached Cypress App Data
rm -rf $LOCALAPPDATA/Cypress # remove cached Cypress binary
rm -rf /tmp # remove temporary files including cached Geckodriver
git clean -xfd # if repeating
npm install cypress@latest
npx cypress run -b firefox Simulate air-gapped situation cd cypress-docker-images/examples/basic
rm -rf $APPDATA/Cypress # remove cached Cypress App Data
npx cypress run -b firefox |
Although I have seen the issue deleting the profile using Firefox |
@MikeMcC399 There is a conf file for Mozilla. To sum up, depending on your Cypress version, in an air-gapped environment you may have to put geckodriver.exe in AppData/Local/Temp Thank you! |
|
It's good to hear it works for you! Congratulations 🎉 |
I am working on a new project.
The web application is accessed via a VM through a proxy and without internet access.
I installed the latest version of Cypress (14.1.0) using the CYPRESS_INSTALL_BINARY environment variable and Artifactory.
Cypress launches with Edge but not with firefox.
When I run the command npx cypress run -b firefox, the following error messages are displayed
How to work around the getaddrinfo EAI_AGAIN error raw.githubusercontent.com and get firefox launch?
Originally posted by @wildnano in #31223
The text was updated successfully, but these errors were encountered: