Home Server Error Triage Checklist
Use this when a home server, Linux service, Docker container, Nginx proxy, DNS record, SSL certificate, NAS share, or homelab route stops working and you need a safe next step.
Do not paste passwords, API keys, tokens, cookies, private keys, private source code, customer data, or production shell access into any public form.
1. Freeze The Symptom
- Write the exact visible error, status code, or failed command.
- Write what changed immediately before the failure.
- Keep the current config untouched until you have a backup or rollback path.
2. Split The Problem
- Service layer:
systemctl status, container status, restart loop, or missing dependency. - Network layer: DNS, port forward, firewall, reverse proxy target, upstream health.
- Certificate layer: expiry, wrong virtual host, HTTP-01/ALPN failure, or mixed HTTP/HTTPS route.
- Storage layer: SMB/NFS mount, UID/GID mismatch, disk full, permission drift.
3. Share Only Public-Safe Evidence
Good public context is OS version, service name, public URL if relevant, redacted error text, what changed, and the desired result. Bad public context is a credential, token, private key, private customer log, or direct shell access.
4. Make One Reversible Test
Prefer a single small test that proves or disproves one layer. Avoid changing Docker Compose, Nginx, firewall, DNS, and storage permissions all at once.
Need An Outside Read?
Devmes offers a fixed USD 1 public-context triage check: three likely causes, three safe next checks, and one rollback or backup reminder within 24 hours after payment and usable public input.