Skip to content
Skip to this exploration
All explorations

Practical self-hosting · beginner

04 · Turn an error into a timeline

Read logs without confusing symptoms with causes.

10 min 5 sectionsv1

What you can take away

  • Build a short incident timeline with a testable hypothesis.
  • Create a private four-row timeline from a harmless practice incident or a fictional incident you label as such

Your trail through this idea

Checking saved progress…

A login screen fails at the same time a database reconnects. Which caused which? Ian’s troubleshooting conversations are a reminder that a dramatic final error is often the last link in a chain.

Prerequisite: complete the preceding lesson or bring its worksheet.

Mark sections complete when you choose. Reading alone does not mark them.

Understand the system

Logs are reports from individual components. They differ in clocks, detail, and what they consider an error. A timeline joins observations while preserving uncertainty. Record the action, the component, the time, and the observed result. Distinguish 'database refused a connection' from 'database caused the outage': the latter needs a causal test.

Docker Compose logs supports bounded output, timestamps, and service selection. On a disposable Compose project, docker compose logs --timestamps --tail 30 is a manageable first look. Run it only from the intended project directory. Logs can contain tokens, addresses, and personal content; do not paste raw output into a public lesson or issue.

Checking saved progress…

Work through the case

Original example: an app retries its database connection three times, then the proxy returns an upstream error. The proxy error establishes a failed request, not a faulty proxy. A useful next test checks whether the app can reach its expected database service. Restarting every component destroys timing evidence and changes several variables at once.

Checking saved progress…

Make something useful

Try this

Original exercise

Create a private four-row timeline from a harmless practice incident or a fictional incident you label as such. Add an 'observation or inference' column. Write two competing explanations and one check that would distinguish them. If you use real logs, retain only necessary lines locally and replace sensitive values before discussing them. No restart is required for this lab.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

A proxy reports an upstream error. What follows?

Choose one answer

A self-study prompt. You can retry; this is not an exam.

Checking saved progress…

Keep the result and follow the sources

A good incident note ends with a falsifiable next step. If the test gives the opposite result, change the explanation. Keep the timeline for the recovery exercise; it is more useful than a screenshot of the last error.

Sources and scope

  • Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
  • Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
  • Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.
Checking saved progress…

These checks are for reflection and practice. Your answers and reflection notes are not sent anywhere.

Back to all explorations