Builds failing on a commit that only touched test files and pytest config, nothing that affects the build itself. * **Deployment IDs**: `065d1e3e-37df-4bc6-bca2-28a1782f4fda` and `db6f0d26-aca8-4b2a-9dd0-b67ff9febb3a` * **Error**: `frontend grpc server closed unexpectedly`

Builds failing with `frontend grpc server closed unexpectedly` error

Builds failing with

frontend grpc server closed unexpectedly

error

michaelolig

HOBBYOP

a month ago

Builds failing on a commit that only touched test files and pytest config, nothing that affects the build itself.

Deployment IDs: 065d1e3e-37df-4bc6-bca2-28a1782f4fda and db6f0d26-aca8-4b2a-9dd0-b67ff9febb3a
Error: frontend grpc server closed unexpectedly

Solved

3 Replies

Railway

BOT

a month ago

We confirmed both deployments failed with the frontend grpc server closed unexpectedly error, and your service is currently in a FAILED state. This error originates from our build infrastructure, not from your code or configuration. It is a transient issue that typically resolves on a retry. Please trigger a new deployment by clicking "Redeploy" on the latest failed deployment from the three-dot menu in your deployments list, and it should build successfully.

Status changed to Awaiting User Response Railway • about 1 month ago

michaelolig

HOBBYOP

a month ago

Third deploy attempt failed with the same frontend grpc server closed unexpectedly error.

Status changed to Awaiting Railway Response Railway • about 1 month ago

michaelolig

HOBBYOP

a month ago

Just had a successful deploy. The underlying issue seems to have been resolved.

Status changed to Solved michaelolig • about 1 month ago

Welcome!