a month ago
Hi Railway team,
My builds have been failing consistently for several hours across 7+ commits with this error:
Build Failed: build daemon returned an error < failed to solve: secret Cloud not found >
Project details:
- Project name: strong-possibility
- Service: Coating-app-Prototype-
- Repo: GitHub, auto-deploy from main branch
- Root Directory: backend
- Start Command: uvicorn server:app --host 0.0.0.0 --port $PORT
- Builder: default (Nixpacks/Railpack, no custom Dockerfile)
What I've verified on my side:
- GitHub connection is healthy, commits are being picked up correctly
- I have not configured any build secret named "Cloud" anywhere — no such secret exists in my service variables
- The same codebase built and deployed successfully ~2 days ago with no build config changes since
- One deploy attempt failed differently with a ghcr.io registry pull failure, which suggests a transient platform-side issue
Impact: my production service is currently stuck serving a stale build from 2+ days ago. I'm on a tight deadline (client demo today), so any help would be greatly appreciated.
Could you check whether this is a build daemon / infrastructure issue on Railway's side, and if so, retry or reroute my builds?
Deployment ID of the most recent failed build: [paste this from the failed deployment's page — open the failed deploy and copy the ID from the URL or details panel]
Thanks!
1 Replies
a month ago
Your service has an environment variable named Cloud Convert PDF, and the space in that name is what is causing the build failure. The build system interprets each space-separated word as a separate secret identifier, so it looks for a secret called Cloud and fails. Rename that variable to something without spaces (e.g. CLOUD_CONVERT_PDF) in your service's Variables tab and redeploy.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved suyshx31 • about 1 month ago