Alex Plischke

Thank you for taking a look! I unfortunately do not have any additional information on this. I suppose it would have been helpful if `chrome-remote-interface` would print the response body...

I ran with the DEBUG setting that was provided, but was not able to get any more information out of this error case: ``` ================================================================================ (Run Starting) ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Cypress:...

The tests are actually targeting the cypress hosted examples (https://example.cypress.io/).

> it possible you're on a corporate network/VPN Yep! > might be interjecting some network middleware (proxy, etc)? My suspicion is that the "

> Do you still see this issue when running off your corporate VPN/network? Unfortunately I can't control that in the environment where I'm experiencing this issue. > I notice the...

Replicated 🥵 There is a proxy service that starts on `49221` and `55001`. If that overlapped with the random port that Cypress picked, it resulted in the JSON error above....

Indeed, I'm not running into this issue after updating `get-port` to version `6.1.2`. Would be great if that could find its way into cypress 🙏

Could the update of `get-port` be possible now? Considering that Cypress requires Node 16+ these days.

Which framework? Cypress, Playwright or TestCafe?

The tunnel should definitely be already set up by the time the commands from `preExec` are executed. However, you may likely need to configure your HTTP client with the tunnel...