Add Chromium-family browser `RemoteDebuggingAllowed` troubleshooting advice

[MikeMcC399]

What would you like?

Add browser troubleshooting information to https://docs.cypress.io/app/references/troubleshooting#Launching-browsers for the case of applied policy for Chromium-family browsers blocking the use of --remote-debugging-port causing a failure to test.

Why is this needed?

Cypress uses --remote-debugging-port with Chromium-based browsers including Google Chrome and Microsoft Edge. This can be blocked by policy external to Cypress, causing Cypress to be unable to connect to the related browser. The default is to allow remote debugging.

Browser	Policy documentation
Google Chrome	RemoteDebuggingAllowed
Microsoft Edge	RemoteDebuggingAllowed

• This was the subject of Cypress is having trouble in connecting with chrome and edge cypress#32526

Other

[MikeMcC399]

• I'm considering this issue resolved through PR Add Chrome & Edge policy requirements RemoteDebuggingAllowed #6291

with the additional sections:

• Launching browsers > Chrome policy
• Launching browsers > Edge policy

These mention the error condition ECONNREFUSED when policy is blocking and Cypress is started in cypress run mode.

• In cypress open mode, the open issue Chrome browser stays on about:blank page with RemoteDebuggingAllowed false cypress#32671 documents how Cypress behaves in this error condition. The logs / UI do not give a clear indication of the source of error, so this first needs to be investigated to see if it can be improved.