If this sounds like your week
`EADDRINUSE: address already in use :::2019` — and you just wanted to run your app.
You started Caddy and hit a wall of red. Something is already on port 2019, so it refuses to boot. Nine times out of ten it's a previous instance that crashed without releasing the socket, or a second project you forgot was still running. The error names the port. It never names the culprit.
Where tooling usually breaks
netstat gives you a PID. A PID is not an answer.
The standard ritual is `netstat -ano | findstr :2019`, copy the PID, `tasklist` to see what it even is, then `taskkill`. Two context switches and one chance to fat-finger the number — and because Windows recycles PIDs, the ID you copied can belong to something else by the time you run the kill.