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".
What this skill does
# 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 in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.