Fly.io Deploy Failed: Waiting for Depot Builder, Registry 401, Too Many Requests
Quick answer
Most fly deploy failures are builder or registry problems. Try --depot=false or --local-only, re-login for 401s, and push images under 8GB.
Most likely fix: Switch builder
How to fix it
Try these in order — the most common fix is first.
1. Switch builder
- fly deploy --depot=false for the legacy remote builder
- fly deploy --local-only if remote builds are down (needs Docker)
- Debug the Dockerfile with docker build .
Did this fix it?2. Fix 401 on push
- Run fly auth logout then fly auth login
- Check status.flyio.net for a registry incident
Did this fix it?3. Fix rate limits and manifest errors
- Push to Docker Hub or a private registry and run fly deploy --image <image:tag>
- For failed to get manifest, wait about a minute and retry
- For release_command machine not found, retry and read fly logs
Did this fix it?4. Shrink the image
- Use multi-stage builds, add .dockerignore, move large assets to volumes or object storage (limit 8GB)
Did this fix it?
Symptoms
fly deploy hangs at Waiting for depot builder, fails with failed to push registry: 401 Unauthorized, too many requests, machine not found, or failed to get manifest.
Why it happens
- Remote builder down or slow
- Expired CLI auth
- Registry rate limits (GHCR and others)
- Image larger than 8GB
- Release command timing issues
This guide also covers
- fly deploy failed
- waiting for depot builder
- failed to push registry 401 unauthorized fly
- fly deploy too many requests
Still not working?
If Fly.io keeps failing, you're not alone. See every Fly.io problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All export, render & quality loss guides →
Railway Slow Deployments and Slow App (Railway)
Render Free Instance Spins Down: Slow First Request (Render)
DigitalOcean App Platform Build Failed (DigitalOcean)
Heroku Build Failed Error (Heroku)
Other Fly.io errors
- Fly.io: The app is not listening on the expected address and will not be reachable by fly-proxy
- Fly.io 502 Bad Gateway
- Fly.io 503 Service Unavailable
- Fly.io Health Checks Failing
- Fly.io Machines Stopping or Not Starting (Auto-Stop)
- Fly.io Out of Memory (OOM Killed)
- Fly.io Certificate Not Issuing or Custom Domain Not Working
- How to Cancel Fly.io: Delete an App, Stop Billing and Delete Your Account