Vigil: the site answers is failing
fixedopened 26 days agodown 50s
what the check said
the site answers — expected 200, got 502
Warden’s diagnosis · 88% sure of the cause
Cause: the vigil process is stopped. pm2 list shows "vigil" with status=stopped, lastStartedAt 2026-09-14T10:45:59.232Z, and the last successful check at 10:46:01.964Z was followed within seconds by the process being gone. Public probe to https://vigil.80.225.209.190.sslip.io/ just returned 502 in 16ms, consistent with the upstream being down rather than slow or erroring. Evidence in the pm2 out log shows a clean Next.js startup sequence ("Starting... ✓ Ready in ...ms") then no further output — i.e. the app came up fine and was then stopped externally, not crashed mid-request. The vigil-error.log was empty, so there is no stack trace pointing at application code. The likely cause is the site being stopped (the standing rules describe this service as one "the console lets visitors break on purpose" and it is restarted frequently). Recommended act: pm2_start vigil. The process status is "stopped" (not "errored"), pm2_start is permitted without asking, and the standing rules record prior owner approval for exactly this action on this service. I have not acted yet; one act will follow.
suspect · pm2 process "vigil" — status stopped since 2026-09-14T10:45:59Z
This one was worked before you opened the page, so there is nothing to watch live. Everything it did is in Everything it ran below, with the exact command and the rule that permitted each one — that table is the record, and this timeline is only the same thing arriving in real time.
Cause: the vigil process is stopped. Fixed, and the check that failed passes again.
Everything it ran5 calls · 1 changed something
Warden has no shell. Each row below is one named action from a fixed list, spawned without a shell, with the rule of yours that permitted it. Copy any command and run it yourself.
| what | how safe | your rule | command | ms |
|---|---|---|---|---|
read the log pm2_logs | looks only | did ityou allowed it | pm2 logs vigil --lines 50 (errors only) | 198 |
read the log pm2_logs | looks only | did ityou allowed it | pm2 logs vigil --lines 80 | 225 |
load the page http_probe | looks only | did ityou allowed it | GET https://vigil.80.225.209.190.sslip.io/ | 16 |
list the processes pm2_list | looks only | did ityou allowed it | pm2 jlist | 198 |
start the process pm2_start | undoes itself | did ityou allowed it | start vigil | 282 |
This incident is marked resolved because the site answers — the same check that failed — was run again and passed. Nothing Warden believed about its own fix could have closed it.