The hardening change that took the shop down
A TLS hardening change went out at 06:00 and the shop has returned errors since. Read the nginx unit’s journal to find the broken file, the line, and the bad directive.
- Terminal mission
- Beginner
- 3 questions
- 0 of 3 solved
Your goal
Your goalFind the broken setting that stopped nginx starting after a hardening change.
At 06:00 a configuration-management run pushed a TLS hardening snippet to shop-01. Since then the load balancer marks the host as down.
journalctl -u nginx shows both nginx’s own errors and what systemd did with the unit.
What’s on screen
- Briefing
- the story: what happened and what evidence you were handed.
- Terminal
- the dark box. It is a pretend Linux shell that runs in your browser. Type a command and press Enter. Nothing you type touches a real system.
- Walkthrough
- the numbered path. Each step says what to type and what you should see. Hints open one at a time.
- Answer boxes
- under each question step. Type what you found and press Check.
Words to know
- TLS
- Transport Layer Security, the encryption behind HTTPS
shop-01 · Linux log triage
Type help for the command list and objectives for your tasks. Everything runs in this browser.
Up and down arrows walk your history. Ctrl+L clears the screen. Try help, ls, and objectives.
Read first
More in Linux log triage
The whole walkthrough
Every step in order: 287 words, about 2 min. It gives away every answer, so try the steps first.