Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cypress can't test an application running at https://127.0.0.1 in a Docker container #1371

Closed
benjaminapetersen opened this issue Feb 23, 2018 · 2 comments
Labels
type: duplicate This issue or pull request already exists

Comments

@benjaminapetersen
Copy link

benjaminapetersen commented Feb 23, 2018

  • Operating System: MacOS
  • Cypress Version: 2.0.3
  • Browser Version: Chrome 64.0.3282.167, & whatever Electron is used by the above Cypress version.

Is this a Feature or Bug?

Bug

Current behavior:

Cypress is unable to load anything and simply shows the ERR_SSL_VERSION_OR_CIPHER_MISMATCH error.

Desired behavior:

Cypress would load the page at https://127.0.0.1:8443 and run the tests.

How to reproduce:

I'm using the oc cluster up command from this guide for openshift to setup a local cluster. This is similar to minikube or minishift or any number of the other kubernetes distros to run a local cluster in a VM on your local machine.

I'm attempting to test the web console for OpenShift. The console can be run locally at localhost:9000 for development, however I am trying to test the console that is already built into a container running on the platform, which is accessible at https://127.0.0.1:8443/console. This is necessary to ensure that the console is packaged and configured properly for deployment (talks to the APIs, etc).

Test code:

Nothing fancy, this is just a visit() to kick off the test:

const protocol = 'https://',
    host = '127.0.0.1',
    serverPort = 8443,
    baseUrl = protocol + host + ':' + serverPort,
    loginUrl = baseUrl + '/login',
    consoleUrl = baseUrl + '/console';
describe('and login', () => {
      it('should successfully login', () => {
        cy.visit(consoleUrl);
      });
});

Additional Info (images, stack traces, etc)

Nothing to add here, we don't get far enough.

Thanks!

@brian-mann
Copy link
Member

This is actually a duplicate of: #771

You're running into a highly unusual situation where Cypress doesn't work on HTTPS. There is a reproducible example (in the other issue) but we haven't had time to look at it / and fix it. It's a bug in Cypress though and it will be fixed.

The vast majority of https works fine. Closing as duplicate but will note when the underlying issue is fixed.

@brian-mann brian-mann added the type: duplicate This issue or pull request already exists label Feb 25, 2018
@benjaminapetersen
Copy link
Author

Sounds good to me, thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants