Help

Troubleshooting

Most issues fall into one of three categories: Sentinel connectivity, game server networking, or RCON configuration.

Panel shows “Sentinel Offline”
Check that the Sentinel Windows service is running: open services.msc → find SitrepSentinel → Status: Running. If stopped, right-click → Start. If it won't start, check the Sentinel log for errors. See Sentinel issues for a full diagnostic checklist.
Server is running but players can't connect
This is almost always a firewall or port-forwarding issue, not a Sitrep issue. Arma Reforger needs these ports open inbound on your router and Windows Firewall:

UDP 2001 — game traffic    UDP 17777 — Steam query
RCON says “Connection refused”
Confirm your RCON password and port in ArmaReforgerServer.json match what was configured during Sentinel installation. Also verify RCON is enabled in the config: "rcon": { ... } must exist and not be commented out.
Wizard Step 3 is stuck waiting for Sentinel
Work through the Sentinel issues checklist in order. The most common causes are: (1) wrong Panel URL in .env (trailing slash, typo), (2) wrong or rotated credentials, (3) outbound HTTPS blocked by a firewall.
Server FPS is very low / players rubber-banding
Low server FPS indicates CPU saturation on the main simulation thread. Common causes: too many AI entities, complex mods with heavy scripting, or underpowered hardware. See Hardware & requirements for guidance. Sitrep itself does not affect server FPS.
SteamCMD showed an error during installation
Check C:\Program Files\Spare Time Gaming\Sentinel\logs\content_log.txt for the specific error. Common fixes: re-run the installer to retry the download, or install the Arma Reforger dedicated server manually via Steam.
Still stuck? Use the Report issue button (bug icon, bottom-right of the panel) to copy your Sentinel log and open a pre-filled GitHub issue.