Website Incident Response Checklist for Solo Operators
When a website breaks, panic creates bad decisions. A solo operator needs a simple incident response process: stabilize, protect data, identify the failing layer, fix the root cause and prevent repeat failure.
Core principle
Your first job is not to look smart. Your first job is to stop damage and preserve recovery options.
Checklist
- Write down the symptom and time of incident.
- Check whether the issue affects all users or only you.
- Take a quick backup if the system is still accessible.
- Avoid making multiple changes at once.
- Check monitoring and server status.
- Check logs for evidence.
- Identify the failing layer.
- Apply the smallest safe fix.
- Verify recovery from user perspective.
- Write a short incident note for future prevention.
What to learn
Every incident should improve your system. After recovery, add monitoring, backup, documentation or security controls that would have made the issue easier to detect or fix.
When to Use This Checklist
Use this checklist when a website, VPS, WordPress site or automation system breaks and you need a calm recovery process.
Required Tools
Admin access, SSH access, backup method, logs, monitoring tool, incident notes
Before You Start
Do not make many changes while panicking. Preserve evidence and recovery options first.
Structured Checklist Steps
- Record symptom and time.
- Check if issue is global.
- Create quick backup if possible.
- Stop making random changes.
- Check monitoring.
- Read logs.
- Identify failing layer.
- Apply smallest fix.
- Verify recovery.
- Write incident note.
Verification Steps
- Website works for users.
- Logs show no repeated critical error.
- Root cause is documented.
- Backup status is known.
- Prevention action is defined.
Rollback Plan
If the first fix makes things worse, revert it immediately and return to the last known stable state before testing another fix.
Common Mistakes
- Panic editing.
- No incident timeline.
- Skipping backup.
- Fixing symptoms only.
- Not writing lessons learned.
Related Commands
date
curl -I https://example.com
sudo systemctl status nginx
sudo tail -n 100 /var/log/nginx/error.log
free -h
df -h