Debug failed Render deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.

Debug Render Deployments Analyze deployment failures using logs, metrics, and database queries. Identify root causes and apply fixes. When to Use This Skill Activate this skill when: Deployment fails on Render Service won't start or keeps crashing User mentions errors, logs, or debugging Health checks are timing out Application errors in production Performance issues (slow responses) Database connection problems Prerequisites MCP tools (preferred): Test with list services() provides structured data CLI (fallback): render version use if MCP tools unavailable Authentication: If you installed the Render plugin (Cursor, Codex, Claude Code), it provides OAuth for MCP — complete the OAuth prompt. For manual MCP clients, use a Render API key. For CLI, verify with render whoami o json . Workspace: get selected workspace() or render workspace current o json Note: MCP tools require the Render MCP server. If unavailable, use the CLI for logs and deploy status; metrics and structured database queries require MCP. MCP Setup If list services() fails, set up the Render MCP server. For detailed per tool walkthroughs, see render mcp . Plugin setup: If the Render plugin is installed, complete Render OAuth when prompted, then reload your tool and retry list services() . Manual MCP setup: Add the Render MCP server to your AI tool's MCP config: URL: https://mcp.render.com/mcp Auth header: Authorization: Bearer <YOUR API KEY API key: https://dashboard.render.com/u/ /settings api keys After configuring, restart your tool and retry list services() . Then set your workspace with list workspaces() / get selected workspace() . Debugging Workflow Step 1: Identify Failed Service If MCP isn't configured, ask whether to set it up (preferred) or continue with CLI. Then proceed. Look for services with failed status. Get details: Step 2: Retrieve Logs Build/Deploy Logs (most failures): Runtime Error Logs: Search for Specific Errors: HTTP Error Logs: Step 3: Analyze Error Patterns Match log errors against known patterns: Error Log Pattern Common Fix MISSING ENV VAR KeyError , not defined Add to render.yaml or update environment variables PORT BINDING EADDRINUSE Use 0.0.0.0:$PORT MISSING DEPENDENCY Cannot find module Add to package.json/requirements.txt DATABASE CONNECTION ECONNREFUSED :5432 Check DATABASE URL, DB status HEALTH CHECK Health check timeout Add /health endpoint, check port binding OUT OF MEMORY heap out of memory , exit 137 Optimize memory or upgrade plan BUILD FAILURE Command failed Fix build command or dependencies Full error catalog: [references/error patterns.md](references/error patterns.md) If errors repeat across deploys: Switch from incremental fixes to a broader sweep. Scan the codebase/config for all likely causes in that error class (related env vars, build config, dependencies, or type errors) and address them together before the next redeploy. Step 4: Check Metrics (Performance Issues) For crashes, slow responses, or resource issues: Detailed metrics guide: [references/metrics debugging.md](references/metrics debugging.md) Step 5: Debug Database Issues For database related errors: Detailed database guide: [references/database debugging.md](references/database debugging.md) Step 6: Apply Fix For environment variables: For code changes: 1. Edit the source file 2. Commit and push 3. Deploy triggers automatically (if auto deploy enabled) Step 7: Verify Fix Quick Workflows Pre built debugging sequences for common scenarios: Scenario Workflow Deploy failed list deploys → list logs(type: build) → fix → redeploy App crashing list logs(level: error) → get metrics(memory) → fix App slow get metrics(http latency) → get metrics(cpu) → query postgres DB connection list postgres → get metrics(connections) → query postgres Post deploy check list deploys → list logs(error) → get metrics Detailed workflows: [references/quick workflows.md](references/quick workflows.md) Quick Reference MCP Tools CLI Commands (Fallback) References Error patterns: [references/error patterns.md](references/error patterns.md) Metrics debugging: [references/metrics debugging.md](references/metrics debugging.md) Database debugging: [references/database debugging.md](references/database debugging.md) Quick workflows: [references/quick workflows.md](references/quick workflows.md) Log analysis: [references/log analysis.md](references/log analysis.md) Troubleshooting: [references/troubleshooting.md](references/troubleshooting.md) Related Skills render deploy — Deploy new applications to Render render monitor — Ongoing service health monitoring render mcp — MCP server setup and tool catalog

render-debug