Cloud and container troubleshooting guides
Production playbooks built around decisive evidence
Follow practical investigation paths for Docker container, Azure application, identity, networking, and data failures. Each guide separates symptoms from causes, identifies the evidence to collect, and finishes with safe recovery verification.
05
guides
100%
free
A–Z
practical
Start here
Featured guide
Structured for quick scanning during an incident and deeper reading when you are building preventive controls.
Latest practical guide
Updated September 5, 2026 · 10 min read
How to Troubleshoot Azure App Service 502 and 503 Errors
A production-aware investigation guide for Azure App Service 502 Bad Gateway and 503 Service Unavailable errors, including startup, deployment, health, and routing checks.
- Test the default App Service hostname before investigating an upstream gateway.
- Correlate the first failure with deployment, restart, scaling, and configuration timestamps.
- Collect runtime evidence before restarting whenever the incident allows it.
- Verify representative application transactions after service recovery.
Explore more
All guides
Key Vault access denied troubleshooting
Diagnose Azure Key Vault 403 and access-denied errors by separating identity, authorization model, RBAC scope, secret permissions, and network restrictions.
Application Gateway backend health
A step-by-step guide to Application Gateway backend health, probe failures, DNS, NSGs, TLS certificates, hostnames, and HTTP status problems.
Azure SQL connectivity troubleshooting
Diagnose Azure SQL Database and SQL Managed Instance connection failures using client, DNS, network, firewall, TLS, authentication, and service-health evidence.
Docker container startup troubleshooting
Troubleshoot Docker containers that exit, restart, remain unhealthy, or cannot serve traffic by checking image, command, configuration, permissions, resources, storage, and networking evidence.
Need a guided investigation?
Bring the live problem to CloudForge.
Share the exact error, environment, impact, and recent change. Sign-in remains optional unless you want the conversation saved.