2 months ago
My deployment 210cffa6 for service cs-platform-api fails immediately at “Diagnosis”, before Initialization and Build start. A new GitHub commit was created after the Railpack incident was resolved, but it failed in the same way. The existing deployment remains online. Please check or reset the deployment diagnosis for this service.
3 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
Try to deploy latest commit by selecting your service, then press CTRL+K, then select deploy latest commit, and see if that resolves the issue.
Status changed to Solved csadvogados • about 2 months ago
2 months ago
Resolved. Deploying the latest commit exposed a stale start-command issue: Uvicorn was receiving $PORT as literal text. I changed the Railway configuration to use the Docker entrypoint, updated the entrypoint to bind to the dynamic PORT, and changed the public networking target port to 8080. The deployment is now active and the API healthcheck returns 200 OK.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved Railway • about 2 months ago