Including auth credentials in baseUrl causes browser to never connect in headless mode

[cherednyk-tcm]

Current behavior:

After update of cypress from 1.4.2 to 2.1.0 browser never connected in headless mode.

Console output

(Tests Starting)

Timed out waiting for the browser to connect. Retrying...

Timed out waiting for the browser to connect. Retrying again...

The browser never connected. Something is wrong. The tests cannot run. Aborting...

  (Tests Finished)

Steps to reproduce:

removed folders:
node_modules
cypress

removed @ types/cypress from package.json
changed cypress version in package.json from 1.4.2 to 2.1.0

Then installed dependencies and started tests in default headless mode

npm install

cypress run

Versions

OS: Windows 10 / macOS High Sierra v 10.13.4
Cypress: 2.1.0

same behavior on Windows and macOS

package.json

  "devDependencies": {
    "@ bahmutov/add-typescript-to-cypress": "2.0.0",
    "@ types/chai": "4.1.1",
    "@ types/chai-as-promised": "7.1.0",
    "@ types/mocha": "2.2.48",
    "@ types/node": "9.3.0",
    "chai": "4.1.2",
    "chai-as-promised": "7.1.1",
    "cypress": "2.1.0",
    "dotenv-safe": "5.0.1",
    "mocha": "5.0.5",
    "mochawesome": "3.0.2",
    "tslint": "5.9.1",
    "typescript": "2.8.1"
  }

cypress.json

{
  "integrationFolder": "dist/specs",
  "reporter": "mochawesome"
}

[jennifer-shehane]

Does the run work when running cypress open?

[cherednyk-tcm]

Yes, cypress open works on version 2.1.0.
On version 1.4.2 both modes work ok: cypress run and cypress open.

[jennifer-shehane]

Yeah, I don't see why this should be happening from the information provided. Could you run DEBUG=cypress:* cypress run and share the .log?

[cherednyk-tcm]

Here's the log

[jennifer-shehane]

• Are you visiting a site with basic auth credentials in the url?
• Do the tests run when visiting another url without basic auth credentials in the url?

[cherednyk-tcm]

Yes, the app requires basic auth credentials, they are passed in the url.
I started the app on localhost with turned off basic auth, then removed credentials from the url in tests, and this problem disappeared, tests are now working in headless mode.
Looks like cypress is not backward compatible for this feature.

[fbring]

I had a similar issue when I updated from 1.3.0 to 2.1.0.

I removed the auth credentials from the baseUrl and pasted them into the options of cy.visit().

Before

{
   "baseUrl": "https://name:secret@domain.io"
}

After

cy.visit('/', {
   auth: {
      username: 'name',
      password: 'secret',
   },
});

Now it works for me. Maybe this is helpful.

[jennifer-shehane]

@IgorCherednyk were you able to try the workaround as described by @fbring ?

[AyWa]

Hi,

I had the same issue as you describe.
However if I was installing cypress in a new folder, I was able to use chrome for the test they provide, but not with my test suite.

So after investigation, my problem was coming from plugins/index

I used to have:

  on('before:browser:launch', (browser = {}, args) => {
    // console.log(browser, args) // see what all is in here!
  
    // browser will look something like this
    // {
    //   name: 'chrome',
    //   displayName: 'Chrome',
    //   version: '63.0.3239.108',
    //   path: '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome',
    //   majorVersion: '63'
    // }
  
    // args are different based on the browser
    // sometimes an array, sometimes an object
  
    if (browser.name === 'chrome') {
      args.push('--headless')
      args.push('--disable-dev-shm-usage')
  
      // whatever you return here becomes the new args
      return args
    }
  })

and it was working totally fine before 2.X. But with 2.X chrome can't open. However if I remove this code, everything run correctly. So I think there is a breaking change there. Maybe you have similar problem ?

problem of the code was args.push('--headless')

So does there is an other way to put chrome in headless ?

[jennifer-shehane]

@AyWa No, there is currently not a way to run Chrome headlessly in Cypress.

We could probably have a better error for this situation.

[AyWa]

Got it, indeed could be cool, if cypress throw an error, or maybe even a little help like:
The browser never connected. Something is wrong. The tests cannot run. Aborting , Please check your plugin configuration