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 There is no Internet connection #1671

Closed
nWidart opened this issue May 3, 2018 · 10 comments
Closed

Cypress There is no Internet connection #1671

nWidart opened this issue May 3, 2018 · 10 comments

Comments

@nWidart
Copy link

nWidart commented May 3, 2018

Current behavior:

When running cypress open and clicking Run All Tests, the chrome browser opens but with the following message:

There is no Internet connection

image

Desired behavior:

The browser opens correctly.

Steps to reproduce:

Versions

  • 2.1.0
  • Chrome 66

Thanks!

@jennifer-shehane
Copy link
Member

Hi @nWidart, this error usually displays when:

  1. You don't have internet (I'm sure you've already determined this is not the issue 😉)
  2. You are behind a corporate proxy - I suggest following the env vars workaround outlined here.

Let me know if the proxy workaround solves your issue!

@jennifer-shehane jennifer-shehane added the stage: awaiting response Potential fix was proposed; awaiting response label May 3, 2018
@nWidart
Copy link
Author

nWidart commented May 3, 2018

Hello,

Indeed I read the issue about the corporate proxy, but even when not on the vpn it wouldn't work.
It worked before also on this same vpn.

Strangely what did work, however, was rebooting the computer 😄

Not sure what went on, but I guess it can be considered as resolved then :)

Thank you for your reply.

@nWidart nWidart closed this as completed May 3, 2018
@jennifer-shehane jennifer-shehane removed the stage: awaiting response Potential fix was proposed; awaiting response label May 3, 2018
@jeremyjh
Copy link

I had this same error when a Cypress process was left open after I'd closed the client. I did a ps -ef | grep cypress, found the culprit, and killed it. That fixed it, which is probably what the reboot accomplished as well.

@nWidart
Copy link
Author

nWidart commented May 19, 2018

That's good to know, thanks @jeremyjh !

@seanpoulter
Copy link

Force quitting a test running in Chrome can also cause these symptoms. Thanks @jeremyjh. 👌

@NoahPlanGrid
Copy link

Just saw this error. Solved by rebooting.

@mukul7
Copy link

mukul7 commented May 16, 2019

Rebooting Solves this

@jeremyjh
Copy link

@muku7 it really is not necessary to notify everyone subscribed to this issue with information that is already in the thread. Just upvote someone else's comment instead of adding a new one.

@mukul7
Copy link

mukul7 commented May 20, 2019

@muku7 it really is not necessary to notify everyone subscribed to this issue with information that is already in the thread. Just upvote someone else's comment instead of adding a new one.

its @mukul7 **

@prashanth-sams
Copy link

Still an issue on the end of 2021. Rebooting helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants