cypress-io/github-action "Cypress could not verify that this server is running"/binary verify failed

Cypress verifies its binary before running. A corrupt or partially downloaded binary, or a transient download failure, makes verification fail before any test runs.

What this error means

The Cypress step fails with "Cypress failed to verify that the binary is valid" or a verification timeout.

Cypress verification timed out.
Cypress failed to verify that the binary is valid.
##[error]Process completed with exit code 1.

Common causes

Corrupt or partial binary

A bad cache entry or interrupted download left an invalid Cypress binary.

Transient download failure

A momentary network failure fetching the binary breaks verification.

How to fix it

Reinstall/verify the binary and re-run

1. Clear a stale Cypress cache key so the binary is re-downloaded.
2. Run cypress verify explicitly, or let the action reinstall.
3. Re-run the job; transient download issues usually clear.

- uses: cypress-io/github-action@v6
  with:
    install-command: npm ci
    command: npx cypress run

How to prevent it

• Key the Cypress binary cache on the Cypress version so upgrades re-download cleanly.
• Latchkey managed runners auto-retry transient binary-download failures, so a flaky Cypress verify usually resolves without manual intervention.

Related guides