flyio-common-errors
Diagnose and fix common Fly.io errors including deployment failures, health check failures, machine issues, and networking problems. Trigger: "fly.io error", "fly deploy failed", "fly.io not working", "fly health check".
Best use case
flyio-common-errors is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Diagnose and fix common Fly.io errors including deployment failures, health check failures, machine issues, and networking problems. Trigger: "fly.io error", "fly deploy failed", "fly.io not working", "fly health check".
Teams using flyio-common-errors should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/flyio-common-errors/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How flyio-common-errors Compares
| Feature / Agent | flyio-common-errors | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Diagnose and fix common Fly.io errors including deployment failures, health check failures, machine issues, and networking problems. Trigger: "fly.io error", "fly deploy failed", "fly.io not working", "fly health check".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Fly.io Common Errors ## Overview Quick reference for the most common Fly.io deployment and runtime errors with solutions. ## Error Reference ### Health Check Failed ``` Error: health checks for machine e784... failed ``` **Causes:** App not listening on correct port, slow startup, missing dependencies. **Fix:** ```bash # Check logs for startup errors fly logs -a my-app # Verify internal_port matches your app grep internal_port fly.toml # SSH in and test manually fly ssh console -C "curl localhost:3000/health" # Increase health check grace period ``` ```toml # fly.toml — give app more time to start [http_service.checks] grace_period = "30s" interval = "15s" timeout = "5s" ``` ### Deployment Failed — Image Build ``` Error: failed to build: exit code 1 ``` **Fix:** ```bash # Test Docker build locally first docker build -t test . docker run -p 3000:3000 test # Check Dockerfile — common issues: # - Missing EXPOSE directive # - Wrong WORKDIR # - npm install before COPY (layer caching) ``` ### Machine Won't Start ``` Error: machine e784... failed to start ``` **Fix:** ```bash # Check machine events fly machine status e784... # Common cause: OOM — increase memory fly scale vm shared-cpu-1x --memory 512 # Or check for crash loops in logs fly logs --instance e784... ``` ### Connection Refused on .internal ``` Error: connection refused my-api.internal:3000 ``` **Fix:** ```bash # Verify target app is running fly status -a my-api # Check the app listens on correct port fly ssh console -a my-api -C "ss -tlnp" # Ensure apps are in same organization fly orgs list ``` ### Volume Mount Failures ``` Error: volume vol_xxx not found in region iad ``` **Fix:** ```bash # Volume must be in same region as machine fly volumes list -a my-app # Check region fly volumes create data --size 10 --region iad # Match region ``` ### Rate Limited by Machines API ``` HTTP 429 Too Many Requests ``` **Fix:** Implement backoff. See `flyio-rate-limits`. ## Quick Diagnostic Commands ```bash fly status -a my-app # App and machine status fly logs -a my-app # Recent logs fly machine list -a my-app # All machines fly ssh console -a my-app # Shell access fly doctor # Check flyctl health fly platform status # Fly.io platform status ``` ## Resources - [Fly.io Status](https://status.flyio.net/) - [Fly.io Community](https://community.fly.io/) - [Fly Docs](https://fly.io/docs/) ## Next Steps For comprehensive debugging, see `flyio-debug-bundle`.
Related Skills
workhuman-common-errors
Workhuman common errors for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman common errors".
wispr-common-errors
Wispr Flow common errors for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr common errors".
windsurf-common-errors
Diagnose and fix common Windsurf IDE and Cascade errors. Use when Cascade stops working, Supercomplete fails, indexing hangs, or encountering Windsurf-specific issues. Trigger with phrases like "windsurf error", "fix windsurf", "windsurf not working", "cascade broken", "windsurf slow".
webflow-common-errors
Diagnose and fix Webflow Data API v2 errors — 400, 401, 403, 404, 409, 429, 500. Use when encountering Webflow API errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "webflow error", "fix webflow", "webflow not working", "debug webflow", "webflow 429", "webflow 401".
vercel-common-errors
Diagnose and fix common Vercel deployment and function errors. Use when encountering Vercel errors, debugging failed deployments, or troubleshooting serverless function issues. Trigger with phrases like "vercel error", "fix vercel", "vercel not working", "debug vercel", "vercel 500", "vercel build failed".
veeva-common-errors
Veeva Vault common errors for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva common errors".
vastai-common-errors
Diagnose and fix Vast.ai common errors and exceptions. Use when encountering Vast.ai errors, debugging failed instances, or troubleshooting GPU rental issues. Trigger with phrases like "vastai error", "fix vastai", "vastai not working", "debug vastai", "vastai instance failed".
twinmind-common-errors
Diagnose and fix TwinMind common errors and exceptions. Use when encountering transcription errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "twinmind error", "fix twinmind", "twinmind not working", "debug twinmind", "transcription failed".
together-common-errors
Together AI common errors for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together common errors".
techsmith-common-errors
TechSmith common errors for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith common errors".
supabase-common-errors
Diagnose and fix Supabase errors across PostgREST, PostgreSQL, Auth, Storage, and Realtime. Use when encountering error codes like PGRST301, 42501, 23505, or auth failures. Use when debugging failed queries, RLS policy violations, or HTTP 4xx/5xx responses. Trigger with "supabase error", "fix supabase", "PGRST", "supabase 403", "RLS not working", "supabase auth error", "unique constraint", "foreign key violation".
stackblitz-common-errors
Fix WebContainer and StackBlitz errors: COOP/COEP, SharedArrayBuffer, boot failures. Use when WebContainers fail to boot, embeds don't load, or processes crash inside WebContainers. Trigger: "stackblitz error", "webcontainer error", "SharedArrayBuffer not defined".