Cypress is having trouble establishing a connection to the Chrome browser during my CI #27915

sarah-vendredi · 2023-09-27T07:15:23Z

Current behavior

I've had this cypress error for 4 days from the CI. The problem is that I haven't touched anything and I don't understand what's happened.
If so, when do you expect to fix it?

Timed out waiting for the browser to connect. Retrying...
Still waiting to connect to Chrome, retrying in 1 second (attempt 18/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 19/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 20/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 21/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 22/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 23/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 24/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 18/62)
....


Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.

This usually indicates there was a problem opening the Chrome browser.

Desired behavior

No response

Test code to reproduce

i cant reproduce, its on the CI

Cypress Version

12.12.0

Node version

v.16.20.1

Operating System

macOs 13.1

Debug Logs

No response

Other

No response

The text was updated successfully, but these errors were encountered:

MikeMcC399 · 2023-09-27T12:24:27Z

@sarah-vendredi

From your problem description it seems very likely that you have been hit by a bug in Chrome 117 although you haven't said which version of Chrome you are using.
Your simplest solution may be to update Cypress to version 12.15.0 or higher. The pinned issue ECONNRESET on Chrome/Chromium 117.0.5851.0 when using Cypress <12.15.0 or passing--headless=old in browser launch options #27804 describes other workarounds.
The Chromium team have fixed the issue and the fix is in the process of being rolled out to Chrome. We don't have a date from them about availability in a stable release, however we know that releases regularly work on weekly schedules, so if for instance you are using Chrome provided in a default GitHub action runner it might take about three weeks for a full rollout to complete (no guarantee here!) from beta release to stable release to release in GitHub.
Also note that Node.js 16 reached its end-of-life on Sep 11, 2023, so you should plan on updating to Node.js 18 or 20. (This doesn't affect the Chrome issue.)

multivoltage · 2023-09-27T14:36:53Z

Same problem for my company.
This happen in pipeline with jenkins but also in my localhost.
This happen also in a production env (we did not touch code since 3 days)

MikeMcC399 · 2023-09-27T14:46:53Z

@multivoltage

Same problem for my company.
This happen in pipeline with jenkins but also in my localhost.
This happen also in a production env (we did not touch code since 3 days)

It is common for the Chrome version on a localhost to automatically update. It is also common for CI environments to automatically update the version of Chrome. In some CI systems you are able to use a Docker container to fix the version of Chrome used.

multivoltage · 2023-09-27T14:49:12Z

@MikeMcC399 Cool. I used docker in different project for specific chrome versione. Solve some problem but create others one :)

MikeMcC399 · 2023-10-06T17:44:26Z

@sarah-vendredi

Are you still having this issue?

Is yes, could you please say which version of Chrome you are using? For example from executing the command

npx cypress info

the output contains something like this:

Displaying Cypress info...

Detected 5 browsers installed:

1. Chrome
  - Name: chrome
  - Channel: stable
  - Version: 117.0.5938.150

What is the name of your CI provider.

veceslavsv · 2023-11-13T07:36:42Z

I also have this problem :(
Chrome: 119.0.6045.124
cypress: 13.5.0

magarwal19 · 2023-11-14T13:15:09Z

I am facing this issue when using latest cypress version with Cypress Browsers docker image (cypress/browsers:node-20.9.0-chrome-118.0.5993.88-1-ff-118.0.2-edge-118.0.2088.46-1)

if i revert back to cypress old version 12.4.0, then this issue is not observed, but then it blocks me to use replay functionality

danielbayerlein · 2023-11-22T09:21:21Z

I can confirm this issue.

Image: public.ecr.aws/cypress-io/cypress/base:20.9.0
Cypress: 13.6.0
Browser: Electron 114 (headless)
Node Version: v20.9.0 (/usr/local/bin/node)

Running: login/login.cy.ts (1 of 9)
Timed out waiting for the browser to connect. Retrying...
Cannot read properties of null (reading 'getWebSocketDebuggerUrl')
TypeError: Cannot read properties of null (reading 'getWebSocketDebuggerUrl')
at Object.open (:4454:111131)
at async Object.open (:4460:27335)
at async v.relaunchBrowser (:4526:36933)

MikeMcC399 · 2023-11-22T10:10:44Z

@danielbayerlein

You seem to have a different issue, given that the original post concerned Chrome and you write:

Browser: Electron 114 (headless)

cxh324 · 2023-11-30T22:45:18Z

Having this issue with Chrome AND Firefox. Upgraded Cypress to 13.6. Chrome is 119.0.6045.200. Firefox is 115.5.0. Both will throw a browser window that says it's being controlled, but no spec list appears, and the tests don't run

terohuomo · 2023-12-01T11:43:07Z

Also suffering from this issue for multiple weeks.
Docker-container: cypress/browsers:node-20.9.0-chrome-118.0.5993.88-1-ff-118.0.2-edge-118.0.2088.46-1
Cypress: 12.17.4
Browser used: Chrome (headless)

Jenkins manages to run cypress tests like once every 15th time, otherwise timed out connecting to Chrome.

Downgrading to Cypress version 12.4.0 seems to have solved the issue.

For some reason Chrome still stalls for 4 minutes and 50 seconds on Jenkins every time when starting tests without no apparent reasons.

magarwal19 · 2023-12-05T07:57:17Z

@cypress-app-bot @jennifer-shehane
Can you please help to assign this issue..

seems some changes after 12.4.0 are causing this

kolomietsan · 2023-12-28T13:37:25Z

have the same issue on cypress starting from v 12.5.0
Does anyone have solutions or an investigation result of the root cause?

EM-Creations · 2024-01-17T17:42:53Z

I see a similar issue with v13.2.0, when running in Jenkins (Red Hat 7 host) it will normally hang on Timed out waiting for the browser to connect. Retrying.... I've only seen it succeed a few times.

aodanxin · 2024-01-23T18:58:34Z

My company is having the same issue while running Cypress locally with UI. The issue seems to start with Chrome 120.
Cypress version: 12.17.4 and 13.6.2
Chrome version: 120

MikeMcC399 · 2024-01-24T13:46:26Z

Does anybody who is facing this issue have a public repo available where this problem occurs and can be looked at?

Chrome tests in GitHub Actions
https://github.com/cypress-io/github-action/actions/workflows/example-chrome.yml
are not showing this problem.

Is this only a problem on macOS like the original issue post, or are other operating systems also showing problems?

@sarah-vendredi
Are you still experiencing this issue?

damasofc · 2024-02-08T18:57:37Z

Does anybody who is facing this issue have a public repo available where this problem occurs and can be looked at?

Chrome tests in GitHub Actions https://github.com/cypress-io/github-action/actions/workflows/example-chrome.yml are not showing this problem.

Is this only a problem on macOS like the original issue post, or are other operating systems also showing problems?

@sarah-vendredi Are you still experiencing this issue?

this is happening to me in AzureDevops with Linux:

Cypress: 12.17.3
Browser: Chrome 121 (headless)
Node Version: v18.19.0 (/usr/local/bin/node)

is there any workaround?

mauschepano · 2024-02-09T08:23:04Z

@MikeMcC399
I forked the cypress.io "cypress-realworld-testing-course-app" and run into the same error.

Cypress: 13.6.4
Browser: Chrome (121.0.6167.160)
Node: 20.9.0

Forked Realworld-Testing-Course-App

MikeMcC399 · 2024-02-09T09:10:56Z

@mauschepano

Thanks for your feedback! Which operating system were you using?

MikeMcC399 · 2024-02-09T10:26:14Z

@mauschepano

Is the error condition permanent or do the tests work if you run them again?

I tried the following repro steps using:

current Node.js LTS version 20.11.0
Google Chrome Version 121.0.6167.161 (Windows) / 121.0.6167.160 (Ubuntu)

git clone --branch final https://github.com/cypress-io/cypress-realworld-testing-course-app
cd cypress-realworld-testing-course-app
npm ci
npm install [email protected] -D
npm run dev

In a separate terminal

npx cypress run --browser chrome

On Ubuntu I once saw

Still waiting to connect to Chrome, retrying in 1 second (attempt 18/62)
then the test user-journey.cy.ts failed with a timeout.

When I ran it again, it all worked with no warnings or errors.

mauschepano · 2024-02-12T05:40:04Z

@MikeMcC399

I am using MacOS (14.3.1).

Initially, I was able to launch the test app using
npx cypress open
At some point, Cypress stopped launching altogether, and I received the message "Still waiting to connect to Chrome, retrying in 1 second".
However, I had to restart the command after each test because Chrome was no longer responsive.

Today, I checked out the repository again and followed your instructions - it's working so far!

oguzhantx · 2024-02-13T16:29:24Z

Having the same problem
Chrome version: 121
Cypress Version: 13.6.4
Test runner only works with electron version which is 114

mankittens · 2024-02-16T20:49:51Z

Been experiencing the same problem at my company in our gitlab ci setup. Cypress version 13.5.0.

Rajesh-Kodandam · 2024-02-27T12:41:43Z

I when I used this image tag: node-20.9.0-chrome-118.0.5993.88-1-ff-118.0.2-edge-118.0.2088.46-1
works as expected all Chromium based browsers (Chrome, edge, etc); but not the firefox. Any advise.
(Run Starting)
11:44:26 ──────────────────────────────────────────────────────── 11:44:26 │ Cypress: 13.6.6 │
11:44:26 │ Browser: Firefox 118 (headless) │
11:44:26 │ Node Version: v20.9.0 (/usr/local/bin/node) │
11:44:26 │ Specs: 1 found (start-page-nina.cy.ts) │
11:44:26 │ Searched: cypress/e2e/nina/* │
────────────────────────────────────────────
11:44:26
11:44:26 Running: start-page-nina.cy.ts (1 of 1)
11:45:34 Timed out waiting for the browser to connect. Retrying...
11:45:34 Still waiting to connect to Firefox, retrying in 1 second (attempt 18/62)
11:45:34 Still waiting to connect to Firefox, retrying in 1 second (attempt 18/62)

MikeMcC399 · 2024-02-27T14:07:28Z

@Rajesh-Kodandam

This problem has been reported by different users and so far no root cause has been identified, so it's difficult to give any advice.

I checked on GitHub Actions running cypress/browsers:latest (which is currently equivalent to cypress/browsers:node-20.11.0-chrome-121.0.6167.184-1-ff-123.0-edge-121.0.2277.128-1) with Cypress 13.6.6 and there was no problem connecting to any browser (chrome, edge, electron, firefox) to run a simple Cypress test.

Since the issue you have added your comment to is about Firefox, not Chrome, and it does not concern running in a Cypress Docker image, you may want to open a new Cypress issue and provide full debug logs.

Rajesh-Kodandam · 2024-02-27T14:23:51Z

@MikeMcC399
The issue is about Firefox not working using when the Docker image (node-20.11.0-chrome-121.0.6167.184-1-ff-123.0-edge-121.0.2277.128-1) usede and its not regarding the chrome.

MikeMcC399 · 2024-02-27T14:36:18Z

@Rajesh-Kodandam

The issue is about Firefox not working using when the Docker image (node-20.11.0-chrome-121.0.6167.184-1-ff-123.0-edge-121.0.2277.128-1) usede and its not regarding the chrome.

I am so sorry. 🤭 I wrote Chrome and Firefox exactly the wrong way around! I've corrected my post #27915 (comment) now. The conclusion is still correct though, that it would be clearer if you could open a new issue. Have you checked that the issue with Firefox is repeatable?

Rajesh-Kodandam · 2024-02-27T14:45:19Z

Thaank you, Already created new issue for the same. Much appriciated for quick response.

MikeMcC399 · 2024-02-27T15:35:11Z

@Rajesh-Kodandam

It's good that you opened a new issue Firefox not working using when the Docker image (node-20.11.0-chrome-121.0.6167.184-1-ff-123.0-edge-121.0.2277.128-1) used in Jenkins #29018.

EM-Creations · 2024-04-30T19:10:53Z

FYI, you can workaround this if you use the Chromium browser packaged with pupeeter and dynamically update your browser list to use this, it's then available to Cypress and the tests pass.

jessicapeng · 2024-05-01T18:29:42Z

Aside from the incompatibility of chrome/cypress and those fixes this behavior also occurs if you have cypress running in another place so you can close all instances of cypress running and try running it up again.

MateusRodriguesCosta · 2024-05-10T14:30:04Z

Having the same problem, on CI it works smoothly with static Chrome 111. But running on local has two scenarios: running Cypress 12.4 or lower shows the Author's timeout, and running v13 or above gives the 'connect ECONNREFUSED 127.0.0.1:4200'.

Chrome version: 124.0.6367.202
Cypress Version: 13.9.0
Node version: 18.20.2 (LTS)

superdrenner · 2024-06-19T19:42:56Z

@MikeMcC399

Here are the debug logs that I just got from a failure. This is with Cypress 13.11 and Chrome 124. The issue is very intermittent. If there are better logs, let me know what I can adjust the DEBUG value to and I'll post them.

 cypress:server:browsers browsers.kill called with no active instance +0ms
  cypress:server:browsers getBrowserLauncher { browser: { name: 'chrome', family: 'chromium', channel: 'stable', displayName: 'Chrome', version: '124.0.6367.60', path: 'google-chrome', minSupportedVersion: 64, majorVersion: '124', isHeadless: true, isHeaded: false } } +0ms
  cypress:server:browsers opening browser { name: 'chrome', family: 'chromium', channel: 'stable', displayName: 'Chrome', version: '124.0.6367.60', path: 'google-chrome', minSupportedVersion: 64, majorVersion: '124', isHeadless: true, isHeaded: false } +2ms
 DONE  Compiled successfully in 11598ms7:37:05 PM
assets by status 6.56 MiB [cached] 33 assets

... webpack stuff

  cypress:server:browsers browsers.kill called with no active instance +1m
Timed out waiting for the browser to connect. Retrying...
  cypress:server:browsers browsers.kill called with no active instance +1ms
  cypress:server:browsers getBrowserLauncher { browser: { name: 'chrome', family: 'chromium', channel: 'stable', displayName: 'Chrome', version: '124.0.6367.60', path: 'google-chrome', minSupportedVersion: 64, majorVersion: '124', isHeadless: true, isHeaded: false } } +0ms
  cypress:server:browsers opening browser { name: 'chrome', family: 'chromium', channel: 'stable', displayName: 'Chrome', version: '124.0.6367.60', path: 'google-chrome', minSupportedVersion: 64, majorVersion: '124', isHeadless: true, isHeaded: false } +1ms
  cypress:server:browsers browser opened for launch 1 +600ms
  cypress:server:browsers killing process because launch attempt: 1 does not match current launch attempt: 2 +1ms
  cypress:server:browsers killing browser process +0ms
  cypress:server:browsers browser process killed +14ms
Still waiting to connect to Chrome, retrying in 1 second (attempt 18/62)
...a few of these
Still waiting to connect to Chrome, retrying in 1 second (attempt 62/62)
Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.
This usually indicates there was a problem opening the Chrome browser.
The CDP port requested was 36876.
Error: connect ECONNREFUSED 127.0.0.1:36876
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)
  cypress:server:browsers browsers.kill called with no active instance +50s

jennifer-shehane · 2024-07-08T19:20:08Z

Please try updating to the latest Cypress version to see if this issue is resolved. We have resolved several browser connection error situations and this may already be fixed.

roelae · 2024-07-19T09:41:49Z

im having this problem when running in azure, cypress version is 13.13.1 and chrome is 126

MikeMcC399 · 2024-07-19T09:47:18Z

@roelae

The Node.js version v16.20.2, shown in your logs, is no longer supported. If possible update to use the LTS version: currently v20.15.1

roelae · 2024-07-22T00:21:44Z

@roelae

The Node.js version v16.20.2, shown in your logs, is no longer supported. If possible update to use the LTS version: currently v20.15.1

i upgraded my node version, still having the issue

j1000 · 2024-07-31T16:10:17Z

I'm still having the issue too.

Windows
Node v22.2.0
Cypress v13.13.1

AdanAraujoQA · 2024-08-06T19:36:30Z

I'm having the same trouble.
Cypress: 13.13.2
node: 22.6.0

AdanAraujoQA · 2024-08-06T20:53:03Z

@MikeMcC399 @jennifer-shehane

jennifer-shehane · 2024-08-23T15:23:01Z

Could you run Cypress in debug mode mode and print the entire set of logs here?

alexsch01 · 2024-09-09T19:43:09Z

@jennifer-shehane since Chrome 128, I've been seeing this
I think it could be caused by an extension installed by chrome://policy that's preventing Cypress from launching randomly

Matias0432 · 2024-10-02T21:06:14Z

Buenos dias. ¿Se tiene solucion para el inconveniente de ?

Timed out waiting for the browser to connect. Retrying...
Still waiting to connect to Chrome, retrying in 1 second (attempt 18/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 19/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 20/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 21/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 22/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 23/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 24/62)
Still waiting to connect to Chrome, retrying in 1 second (attempt 18/62)
....

aholland · 2024-10-03T00:15:22Z

Buenos dias. ¿Se tiene solucion para el inconveniente de ?

Are you on Chrome 129? I upgraded to Version 129.0.6668.90 (Official Build) (arm64) today and immediately began having this issue.

aholland · 2024-10-03T01:56:57Z

Buenos dias. ¿Se tiene solucion para el inconveniente de ?

Timed out waiting for the browser to connect. Retrying... Still waiting to connect to Chrome, retrying in 1 second (attempt 18/62) Still waiting to connect to Chrome, retrying in 1 second (attempt 19/62) Still waiting to connect to Chrome, retrying in 1 second (attempt 20/62) Still waiting to connect to Chrome, retrying in 1 second (attempt 21/62) Still waiting to connect to Chrome, retrying in 1 second (attempt 22/62) Still waiting to connect to Chrome, retrying in 1 second (attempt 23/62) Still waiting to connect to Chrome, retrying in 1 second (attempt 24/62) Still waiting to connect to Chrome, retrying in 1 second (attempt 18/62) ....

@Matias0432 - I had this problem after upgrading to 129. The problem was solved once I closed Cypress, closed all instance of Chrome (Cmd-Q on Mac) and then started Cypress again. I am now able to open Chrome from the Cypress "Choose a browser" page and have Cypress successfully connect and set the URL etc.

Matias0432 · 2024-10-03T03:13:07Z

@aholland lamentablemente sigo con las mismas falla !!!

MikeMcC399 · 2024-10-03T13:21:37Z

See also Troubleshooting > Clear App Data.

This is known to solve the issue in some circumstances.

nukuld · 2024-10-25T09:36:16Z

Hello! I have also encountered the connection Error issue. I just installed cypress, I cleared the app data, added some nodeEvents from Cypress that should bypass something frome chrome, but still nothing worked for me. I only encounter this issue for the Chrome browser. Below is a pastebin with all of the logs I could copy of the issue.

https://pastebin.com/q32XWuWr

muz234 · 2024-11-06T15:50:00Z

Hello! Im facing the similar issue with chrome browser throwing error:

Timed out after waiting 60000ms for your remote page to load.

Your page did not fire its load event within 60000ms.

You can try increasing the pageLoadTimeout value in

This issue is only faced during headless mode in both MAC and ubuntu instances.
I have also set chromeWebSecurity: false, to disable web security features and still no change.

Cypress v13.15.1
Chrome

Name: chrome
Channel: stable
Version: 130.0.6723.117
Executable: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

Looking for some suggestion to work around this issue.

pieh mentioned this issue Sep 28, 2023

chore: bump cypress to latest v12 opennextjs/opennextjs-netlify#2305

Merged

danielbayerlein mentioned this issue Nov 24, 2023

Timed out waiting for the browser to connect - Cannot read properties of null (reading 'getWebSocketDebuggerUrl') #28397

Closed

jennifer-shehane added the stage: needs information Not enough info to reproduce the issue label Jan 5, 2024

jennifer-shehane added stage: awaiting response Potential fix was proposed; awaiting response and removed stage: needs information Not enough info to reproduce the issue labels Jul 8, 2024

ZengLawrence mentioned this issue Sep 2, 2024

Upgrade cypress to version 13 ZengLawrence/diet-diary#107

Merged

Cypress is having trouble establishing a connection to the Chrome browser during my CI #27915

Cypress is having trouble establishing a connection to the Chrome browser during my CI #27915

Comments

sarah-vendredi commented Sep 27, 2023

Current behavior

Desired behavior

Test code to reproduce

Cypress Version

Node version

Operating System

Debug Logs

Other

MikeMcC399 commented Sep 27, 2023

multivoltage commented Sep 27, 2023

MikeMcC399 commented Sep 27, 2023

multivoltage commented Sep 27, 2023

MikeMcC399 commented Oct 6, 2023

veceslavsv commented Nov 13, 2023 • edited Loading

magarwal19 commented Nov 14, 2023

danielbayerlein commented Nov 22, 2023

MikeMcC399 commented Nov 22, 2023

cxh324 commented Nov 30, 2023

terohuomo commented Dec 1, 2023 • edited Loading

magarwal19 commented Dec 5, 2023 • edited Loading

kolomietsan commented Dec 28, 2023

EM-Creations commented Jan 17, 2024

aodanxin commented Jan 23, 2024 • edited Loading

MikeMcC399 commented Jan 24, 2024

damasofc commented Feb 8, 2024 • edited Loading

mauschepano commented Feb 9, 2024

MikeMcC399 commented Feb 9, 2024

MikeMcC399 commented Feb 9, 2024

mauschepano commented Feb 12, 2024

oguzhantx commented Feb 13, 2024

mankittens commented Feb 16, 2024

Rajesh-Kodandam commented Feb 27, 2024

MikeMcC399 commented Feb 27, 2024 • edited Loading

Rajesh-Kodandam commented Feb 27, 2024 • edited Loading

MikeMcC399 commented Feb 27, 2024

Rajesh-Kodandam commented Feb 27, 2024

MikeMcC399 commented Feb 27, 2024

EM-Creations commented Apr 30, 2024

jessicapeng commented May 1, 2024

MateusRodriguesCosta commented May 10, 2024

superdrenner commented Jun 19, 2024

jennifer-shehane commented Jul 8, 2024

roelae commented Jul 19, 2024

MikeMcC399 commented Jul 19, 2024

roelae commented Jul 22, 2024

j1000 commented Jul 31, 2024

AdanAraujoQA commented Aug 6, 2024 • edited Loading

AdanAraujoQA commented Aug 6, 2024

jennifer-shehane commented Aug 23, 2024

alexsch01 commented Sep 9, 2024 • edited Loading

Matias0432 commented Oct 2, 2024

aholland commented Oct 3, 2024

aholland commented Oct 3, 2024

Matias0432 commented Oct 3, 2024

MikeMcC399 commented Oct 3, 2024

nukuld commented Oct 25, 2024

muz234 commented Nov 6, 2024 • edited Loading

veceslavsv commented Nov 13, 2023 •

edited

Loading

terohuomo commented Dec 1, 2023 •

edited

Loading

magarwal19 commented Dec 5, 2023 •

edited

Loading

aodanxin commented Jan 23, 2024 •

edited

Loading

damasofc commented Feb 8, 2024 •

edited

Loading

MikeMcC399 commented Feb 27, 2024 •

edited

Loading

Rajesh-Kodandam commented Feb 27, 2024 •

edited

Loading

AdanAraujoQA commented Aug 6, 2024 •

edited

Loading

alexsch01 commented Sep 9, 2024 •

edited

Loading

muz234 commented Nov 6, 2024 •

edited

Loading