Help
Sentinel issues
Work through this checklist in order. Most connectivity failures are resolved by step 3.
1
Is the service running?
Open services.msc (Win+R → type services.msc). Find SitrepSentinel. Status should be Running. If not: right-click → Start.
2
Are the credentials correct?
Open C:\Program Files\Spare Time Gaming\Sentinel\.env in Notepad and check:
PANEL_URL=https://panel.spare-time-gaming.us # no trailing slash
AGENT_TOKEN=sts1.xxxx # starts with sts1.
AGENT_SECRET=aabbcc... # 64-char hex
3
Restart after any .env change
nssm restart SitrepSentinel
Run as administrator in PowerShell. Or use services.msc → SitrepSentinel → Restart.
4
Read the log
Get-Content "C:\Program Files\Spare Time Gaming\Sentinel\logs\sentinel.log" -Tail 50
Unauthorized
Token or secret is wrong — re-check .env
ECONNREFUSED
Panel URL unreachable from this machine
ENOTFOUND
DNS failure — check the PANEL_URL hostname
ETIMEDOUT
Outbound HTTPS blocked by a firewall
5
Can this machine reach the panel?
curl https://panel.spare-time-gaming.us/api/health
Should return {"ok":true}. If it doesn't, the machine can't reach the panel — check internet connectivity or corporate firewall rules blocking outbound HTTPS.
6
Are credentials stale?
If the token or secret was rotated since installation: in the panel, click Sentinel Setup (top-right) → Rotate credentials. Copy the new values, update .env, and restart the service (step 3 above).
If none of these steps fix it, use the Report issue button in the panel to include your Sentinel log in a GitHub issue.