Hi ,
I am using cypress 3.1.5 and am trying to open "kitchen Sik"
describe('My First Test', function() {
it('Visit a UI!', function() {
cy.visit("https://example.cypress.io")
})
})
Simple code as given in your doc. Upon execution , the page fails to load with the following error
=============
We attempted to make an http request to this URL but the request failed without a response.
We received this error at the network level:
> Error: connect ETIMEDOUT 104.25.215.23:443
Common situations why this would fail:
- you don't have internet access
- you forgot to run / boot your web server
- your web server isn't accessible
- you have weird network configuration settings on your computer
The stack trace for this error is:
Error: connect ETIMEDOUT 104.25.215.23:443
at Object.exports._errnoException (util.js:1024:11)
at exports._exceptionWithHostPort (util.js:1047:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1150:14)
==============
Note: When i try to visit the same url using regular chrome browser it opens without any issues .
Only through Cypress this happens . In fact i just checked and i am not able to open any url using Cypress
Chrome version is 72.0.3626.119
Are you behind a corporate proxy? You may want to look into these workarounds: https://github.com/cypress-io/cypress/issues/1469
Thanks @Jennifer. Yes i am behind a corporate proxy. Will look into the mentioned workarounds
Awesome . It was indeed the proxy . I followed the workarounds and am able to progress with my tests
Thanks
@jennifer-shehane - When are the proxy issues expected to be fixed? Is there an ETA? I have checked on all the workarounds mentioned but they seem to not help in my case.
Please comment
We'll be releasing improved proxy support in our next release. https://github.com/cypress-io/cypress/pull/3531
Hi!
I get the same error, but I am not behind a proxy.
Is there any other reason that can trigger this error? Thx!
This issue will be closed to further comment as the exact issue here was resolved and tested.
@Robert3191 If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.