Elevated and consistent "502 Bad Gateway" when running in Cypress Cloud

cypress-io / cypress

Fast, easy and reliable testing for anything that runs in a browser.

https://cypress.io

MIT License

46.66k stars 3.16k forks source link

Elevated and consistent "502 Bad Gateway" when running in Cypress Cloud #29795

Closed efreethy closed 1 week ago

efreethy commented 2 months ago

Current behavior

We are experiencing significantly elevated and consistent 502 Bad Gateway errors from within cypress cloud runner. This is making it near impossible to get our tests to pass.

This started on upgrading from cypress 12 to cypress 13. This issue doesn't happen outside of cypress.

Desired behavior

No response

Test code to reproduce

N/A

Cypress Version

13.13.0

Node version

20.14.0

Operating System

Ubuntu 22.04.4 LTS

Debug Logs

No response

Other

No response

jennifer-shehane commented 2 months ago

We'll need some more information to narrow down this issue as we haven't seen this reported.

Is there a more specific Cypress version you can narrow down the problem to?
Are you able to provide a way to reproduce the error?
Is there anything revealing in the Test Replay that explains the difference in behavior? With timing, etc?

MikeMcC399 commented 2 months ago

@efreethy

Cypress Cloud isn't actually a runner. It's only the place where the results of running Cypress are recorded. I don't think it can cause a HTTP 502 Bad Gateway error. It would only record the fact that it is happening.

Can you say where you are running Cypress?
Is it running locally or are you using a CI provider like GitHub Actions or CircleCI?
Where is the server located that you are trying to contact and for which you are receiving an HTTP 502 Bad Gateway error? Is it a local server which is fired up as part of the test? Is it an external website which is already running?

I'm also seeing this error occurring sporadically so it would be good to know more about your environment.