Closed cgraham-rs closed 1 year ago
Same for Windows users.
I am on mac (macOS Monterey).
Getting the same issue on firefox 105:
Still waiting to connect to Firefox, retrying in 1 second (attempt 36/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 37/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 38/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 39/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 40/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 41/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 42/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 43/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 44/62) Still waiting to connect to Firefox, retrying in 1 second (attempt 45/62)
Using it from the UI (npx cypress open).
@cgraham-rs We are worried there has been a regression in firefox. Previously this issue was fixed in this ticket https://bugzilla.mozilla.org/show_bug.cgi?id=1774476. That is firefox v103. Can you please try running against firefox 103 and confirming if youre still seeing the same issue? That would confirm it is most likely a regression in firefox that needs to be addressed.
@nagash77 Our CI process always installs the latest browser versions during setup. Cypress 10.7.0 absolutely worked with Firefox 104.0.2, and then Cypress 10.7.0 broke with Firefox 105.0 I then re-tested with Cypress 10.8.0 to confirm it appeared to be the browser version change as the cause fo the breakage.
@cgraham-rs thanks for confirming our suspicions. We are going to check with firefox to see if they are aware of this issue. I would encourage you to do the same. I will close this issue since this appears to be a problem on the firefox side.
Firefox bug logged: https://bugzilla.mozilla.org/show_bug.cgi?id=1792088
@nagash77 The Firefox team is asking a lot of technical questions about Cypress that I do not have the knowledge to answer.
@cgraham-rs thanks for getting that rolling! I have asked a couple of our engineers to keep an eye on the thread and attempt to answer whatever they can.
We are still facing this issue.. do we have any workaround ?
@nagash77 The Mozilla team seems very active with a lot of technical questions and proposals. Can someone from Cypress please interface with the Mozilla team to help expedite? https://bugzilla.mozilla.org/show_bug.cgi?id=1792088
The client is trying to connect to the IPv4 local IP address which won't work given that we do not have dual-stack support yet. I assume that Cypress doesn't fetch the address from stderr nor the WebDriverActivePort file in the Firefox profile. I can see some solutions: Cypress should not only try on 127.0.0.1 but also on [::1] or even localhost if no connection is possible on IPv4 with BiDi Enable IPv4 in your CI environment to get Firefox to run its BiDi server on IPv4 Add a preference to Firefox to force a specific network interface eg. IPv4 or IPv6 until we have dual-stack support
I'm not sure if they'll read closed issues
@403-html we absolutely try to read them all 😸
@cgraham-rs I am still working internally to find the right expertise to help keep moving this issue along.
Cypress cannot currently connect to Firefox 105. Mozilla has proposed changes to enable Cypress to successfully connect to the right host and port.
Per Mozilla:
Henrik Skupin: Cypress should not only try on 127.0.0.1 but also on [::1] or even localhost if no connection is possible on IPv4 with BiDi
Mozilla has proposed changes to enable Cypress to successfully connect to the right host and port.
Per Mozilla:
Henrik Skupin: Over on bug 1792875 I'm working on a patch to store the WebSocket connection details in the Firefox user profile as WebDriverBiDi.json. Maybe this could be a way for Cypress to read the host and port and connect to the right address.
@nagash77 Some movement on the Mozilla side with nightly build for FF 107 that works with Cypress 10.7.0 See here: https://bugzilla.mozilla.org/show_bug.cgi?id=1792088
As a temporary workaround, you may be able to comment out ::1 localhost
from your /etc/hosts
file to get Cypress to connect to firefox.
Note that https://bugzilla.mozilla.org/show_bug.cgi?id=1792088 is fixed now and will be part of the 107 release. That means that the upcoming Firefox 106 will still be affected, but 107 beta releases will work once released.
As a temporary workaround, you may be able to comment out
::1 localhost
from your/etc/hosts
file to get Cypress to connect to firefox.
Probably it should be also enough to just move this line to after 127.0.0.1 localhost
so that IPv4 is resolved first.
Maybe someone could update the summary of this issue to mention that this only happens when IPv6 is resolved first? Thanks.
Thanks for the update @whimboo!
We also plan on resolving this in Cypress for next week's release.
Probably it should be also enough to just move this line to after
127.0.0.1 localhost
so that IPv4 is resolved first.
Unfortunately, having IPv4 listed first doesn't seem to work (my host file has always listed IPv4 first).
We also plan on resolving this in Cypress for next week's release.
That's great! So I assume you fix it in a way that when 127.0.0.1
cannot be connected to that ::1
is tried?
The code for this is done in cypress-io/cypress#24155, but has yet to be released. We'll update this issue and reference the changelog when it's released.
That's great! So I assume you fix it in a way that when
127.0.0.1
cannot be connected to that::1
is tried?
Yep!
Can this fix not get released any sooner? it is a rather major issue and blocking us
The fix should be released today. In the meantime you can try this workaround https://github.com/cypress-io/cypress/issues/23897#issuecomment-1267670723
thanks @mschile sounds good. That fix doesn't seem to work for us not sure why. On latest Cypress and Firefox 105.
@Phonesis, you can also install a pre-release version to resolve the issue. https://github.com/cypress-io/cypress/commit/0e62696a0ed771794d1ccb350e8b9e01aa0a2e14#comments
The issue is still happening. Using Firefox v105 and Cypress v10.10.0. Now what happens is that using cypress open the page gets loaded - but it is blank. It does not able to load specs at all. I need to add manually in the url "/specs/" and reload the page, then the specs are loaded properly.
However, when running in headless mode, I get: Timed out waiting for the browser to connect. Retrying... Timed out waiting for the browser to connect. Retrying again...
Which most likely has the same issue.
@mschile Still we are unable to connect to firefox 105
@audriusnavickasDB, @jpatil14, sorry that you are still not able to connect to Firefox. I tried again locally and I am able to connect and run a spec on my machine. What OS are you using? Could you also run Cypress with these debug logs turned on:
DEBUG=cypress:network:connect,cypress:server:browsers:firefox-util,cypress:server:browsers:browser-cri-client
@mschile Ok, did a bit of more playing around, so apparently it looks like it started working properly when using base url as localhost or any other https://... url.
However the issue I have described happens when base url contains credentials like this: https://test:test@google.com For other browsers it is working properly.
@audriusnavickasDB, thanks for the update. Since this appears to be a separate issue, could you please log a new issue.
This comment thread has been locked. If you are still experiencing this issue after upgrading to Cypress v10.10.0, please open a new issue.
Current behavior
Updated to Firefox 105 locally and in CI and now Cypress 10.7.0 and 10.8.0 cannot connect to the browser.
Desired behavior
Cypress should continue being able to connect to and utilize the latest version of Firefox.
Test code to reproduce
Locally using Cypress UI.
Start E2E Testing in Firefox
Cypress Version
10.8.0
Node version
v16.17.0
Operating System
macOS 12.6
Debug Logs
Other
No response