- Home
- Skills
- DevOps & Cloud
- Site Down Triage: 502, 503 and SSL Errors Behind a Proxy
Works with the AI Agents you already use
Site Down Triage: 502, 503 and SSL Errors Behind a Proxy
Classify a proxy or container outage from pasted diagnostic text: fault pattern, evidence lines, next read-only check and a reversibility-flagged fix.
$5
Site Down Triage: 502, 503 and SSL Errors Behind a Proxy
Example session with this skill installed
My site returns 502 Bad Gateway. It runs behind nginx with Docker. I saved the response headers to http.txt, the nginx error log to proxy.log and docker ps -a to containers.txt. What is the most likely fault, and what should I check next?
- Read your context and instructions
- Compiled the site down triage
The skill runs its triage script on the three files. This is the script's own output, shortened where marked with ...:
$ python scripts/triage.py --http http.txt --proxy-log proxy.log --containers containers.txt --hostname example.com
{
"pattern": "upstream-connection-refused",
"evidence": [{"file": "proxy.log", "line": 1, "text": "... connect() failed (111: Connection refused) while connecting to upstream ..."}],
"next_check": "docker logs CONTAINER_NAME --tail 100 2>&1",
"remediation": "The proxy cannot reach the upstream container because the connection was refused. ... Back up any persistent volumes before restarting. ...",
"reversible": "depends",
"missing": [],
"also_fired": [{"pattern": "container-unhealthy", "evidence": [{"file": "containers.txt", "line": 2, "text": "ab12cd34ef56 app:1.4 Exited (137) 3 minutes ago web"}]}]
}
Most likely fault: upstream-connection-refused. nginx tried to reach the app container and the connection was refused.
Also matched: container-unhealthy. The web container exited with code 137 three minutes ago, which often means it was killed, for example for running out of memory.
Next read-only check: docker logs web --tail 100 2>&1, to see why the container stopped before you restart anything.
Before you fix: reversible is depends, so back up any persistent volumes before restarting the container.
This is a term match against eleven named fault patterns, not a verified diagnosis. Confirm it with the next check before acting.
Connects securely to your tools. The creator never sees your data.
About this skill
Use when your site returns 502, 503, 504, 403 (CDN or WAF block) or SSL errors, or the proxy returns a routing error, and it runs behind a reverse proxy with containers.
The skill reads up to six kinds of plain-text evidence (HTTP headers, container list, proxy log, container log, certificate text, DNS lookup), picks the most likely of eleven named fault patterns, and returns:
- the supporting evidence lines, with file and line number
- the next read-only command to confirm it
- a remediation suggestion with a reversibility flag, so you know whether to take a backup first
- other patterns that also matched, and evidence that is missing
A match is a term match to confirm, not a verified diagnosis.
scripts/evidence_checklist.py --symptom 502 lists the read-only commands that collect the evidence text.
Do not use when the site has no reverse proxy layer, or when you need to repair a container image before deployment.
Covers eleven fault patterns for proxy-and-container setups. A match is a term match against those patterns, not a verified diagnosis. Does not run commands, apply fixes, predict recovery time or guarantee that a fix resolves the issue. Not for sites without a reverse proxy layer.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Requires