cypress: We encountered an unexpected error talking to our servers (error: socket hang up)
Current behavior:
Whenever I run tests with recording enable I get an error about it not being able to communicate with Cypress. Additionally, it retries at 30 seconds, 1 minute, and 2 minutes which adds 3:30 on to my total test run time.
What’s really interesting is it does successfully record the test on the cypress dashboard so I’m not sure what call is failing / retrying. Everything is working great. The logs and video are uploaded to the dashboard. However, my tests take 3 minutes longer than they should because they need to retry whatever this call is 3 times before the tests can even start.
Error message
Results in dashboard
Desired behavior:
Should not fail to contact cypress server or retry repeatedly on a call that is clearly not needed for the core functionality to succeed.
Steps to reproduce: (app code and test code)
This is just a default install of cypress running on a newly created Digital Ocean droplet running Ubuntu 18 Server. I also see this issue if I try to run it locally (on Ubuntu 18 desktop). Repro is probably just npm install cypress on Ubuntu and try to have it report to the dashboard.
The error happens during initialization (before any tests run) so I doubt the test code is relevant
This is the command I’m using to run the tests:
cypress run --spec cypress/tests/live-tests.spec.js --record --key my-key-here
(if I remove --record --key there is no error, but obviously it doesn’t record to the dashboard)
cypress.json is pretty minimal, but here it is just in case:
{
"fixturesFolder": false,
"integrationFolder": "cypress/tests",
"pluginsFile": false,
"defaultCommandTimeout": 15000,
"projectId": "redacted"
}
Versions
OS: Ubuntu 18.04.2 LTS Browser: Electron 59.0.3071.115 (default) Cypress: 3.2.0 (in the screenshots it’s 3.1.5, but I upgraded and tried again and got the same result)
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 30 (12 by maintainers)
I don’t understand why this issue is closed. We need Cypress to fix it. If you agree with me, please give me sum up
After a couple of weeks of troubleshooting this issue in our org, this error is caused by some security tools that block the network connection with Cypress Cloud. The Cypress-issued CA cert is not verified as a trusted cert and is captured by the security tool as a risk malware. So, if you are experiencing this issue, please disable that cloud security platform tool on your laptop. Or, contact your company’s security engineer to whitelist this Cypress CA cert. However, cypress provides very limited resources on its issued cert, and its customer service is not aware of anything related to this. Just FYI @AtofStryker
hey im getting this error inside jenkins when i run the tests with the --record and the -key for the cypress dashboard
We are also having this problem running our test suite against both Chrome 74 and Electron 59 (headless) on CI pipelines in Jenkins, using Cypress 3.2.0. Our test suite always ends up running and recording to the dashboard successfully, but takes anywhere from 1-3 tries with that same output before the first test will start.
I can send debug logs but there are a LOT - should I focus on a certain section that would be helpful? This is the request that times out and then eventually succeeds, usually only for the first test.
@flotwig redacted logs are here: https://gist.github.com/maryhipp/b1398a87effaf2a7d281ae7505e50423
@flotwig This is a local run on my laptop. It only failed to connect once which is pretty typical on my laptop. On the server it usually retires 3 times (occasionally only 1 or 2).
I purposely made the first test fail (and I have it set to bail on the first failure) so it’d be a shorter log. This issue basically entirely exists before the tests start, but I figured I’d give you an end to end log anyways in case some of the data about the upload after the run (which I’ve never seen fail) sheds any light.