Firefox v105 not working for runner/headless
See original GitHub issueCurrent behavior
Currently FFv105 will not open and times out when attempting to run specs in the runner and also running specs in headless.
Desired behavior
FF browser should not timeout and user should be able to run specs in the FF browser
Test code to reproduce
no test code needed just try to open FFv105 and run spec or use the cli to run a headless test
Cypress Version
10.9.0
Node version
v14.16.1
Operating System
mac 12.4 Monterey
Debug Logs
cypress:server:cypress exiting with err Error: connect ECONNREFUSED 127.0.0.1:55248
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
{
isCypressErr: true,
type: 'FIREFOX_COULD_NOT_CONNECT',
details: 'Error: connect ECONNREFUSED 127.0.0.1:55248\n' +
' at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)\n',
messageMarkdown: 'Cypress failed to make a connection to Firefox.\n' +
'\n' +
'This usually indicates there was a problem opening the Firefox browser.',
originalError: Error: connect ECONNREFUSED 127.0.0.1:55248
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
{
isCypressErr: true,
type: 'CDP_COULD_NOT_CONNECT',
details: 'Error: connect ECONNREFUSED 127.0.0.1:55248\n' +
' at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)\n',
messageMarkdown: 'Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.\n' +
'\n' +
'This usually indicates there was a problem opening the Firefox browser.\n' +
'\n' +
'The CDP port requested was `55248`.',
originalError: OperationalError: connect ECONNREFUSED 127.0.0.1:55248
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
{
cause: [Error],
isOperational: true,
errno: -61,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 55248
},
stackWithoutMessage: ' at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)\n'
},
stackWithoutMessage: ' at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)\n'
} +53s
Cypress failed to make a connection to Firefox.
This usually indicates there was a problem opening the Firefox browser.
Error: connect ECONNREFUSED 127.0.0.1:55248
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
Other
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Firefox does not work - Common fixes to get you back up and ...
Find solutions to Firefox issues like crashing, not starting, slowness and websites not loading.
Read more >Firefox 105.0, See All New Features, Updates and Fixes
Firefox Release Notes. Release Notes tell you what's new in Firefox. As always, we welcome your feedback. You can also file a bug...
Read more >105.0a1 Firefox Nightly - Mozilla
Fixed · Firefox is less likely to run out of memory on Linux and also performs better towards the rest of the system...
Read more >Troubleshoot and diagnose Firefox problems - Mozilla Support
1 1. Restart your computer · 2 2. Clear your cookies and cache · 3 3. Restart Firefox in Troubleshoot Mode · 4...
Read more >Security Vulnerabilities fixed in Firefox 105 - Mozilla
This advisory was updated December 13, 2022 to add CVE-2022-46880. This fix was included in the original release of Firefox 105, but did...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello @brentsharon , We have a fix for a problem that appeared after firefox made a change to how they resolve localhost. https://github.com/cypress-io/cypress/issues/23897 will be releasing today in
Cypress 10.10.0
. Can you please try upgrading to that version of Cypress and seeing if that resolves the issue?Right now there doesn’t seem to be enough information to reproduce the problem on our end. We’ll have to close this issue until we can reproduce it. This does not mean that your issue is not happening - it just means that we do not have a path to move forward.
Please open a new issue with a reproducible example and link to this issue. Here are some tips for providing a Short, Self Contained, Correct, Example and our own Troubleshooting Cypress guide.