Practice and reference
Read the concept, then use a quiz, builder or checklist to make it stick.
First response goal
The goal is to reduce uncertainty quickly. Confirm the symptom, gather evidence, avoid risky assumptions and create a clear next action.
Do not make destructive changes just to see what happens. That is not troubleshooting. That is jazz with root access.
Checklist
- Confirm the URL and exact error
- Check HTTP status and redirects
- Check DNS resolution
- Check server load and disk space
- Review access and error logs
- Check recent changes, deployments or plugin updates
- Escalate with evidence, not vibes
Useful commands
$ curl -I https://example.com
$ dig +short example.com
$ df -h
$ tail -n 50 /usr/local/apache/logs/error_log
What good notes include
- The exact symptom and timestamp.
- The command or tool used to verify it.
- Relevant output, trimmed and sanitised.
- What was ruled out.
- Recommended next action or escalation reason.
Customer-safe summary
Explain what was checked, what was found, and what the customer can do next. Avoid dumping raw logs unless they help. Clear beats clever.