PitwallOSPitwallOS docs

Agent troubleshooting

First-pass checklist when a rig isn't responding. Most issues fall into one of these buckets.

Rig dot is grey

Means: heartbeat not arriving in the last 30 seconds.

  • Is the rig PC powered on and connected to the network? Tryping pitwallos.com from the PC.
  • Is the PitwallOSAgentservice running? Open Services.msc → look for “PitwallOS Agent”.
  • Outbound HTTPS to *.pitwallos.com blocked? Most office firewalls allow it, but cellular hotspots sometimes throttle.

Rig dot is red

Means: agent connected but the last command failed. Click into the rig in the admin console to see the error.

Common causes:

  • AC isn't installed at the path the agent expects. The agent looks at %PROGRAMFILES(X86)%\Steam\steamapps\common\assettocorsa. If yours is elsewhere, set AC_HOMEin the agent's config file.
  • Missing circuit / vehicle. The admin tried to start a session with content not installed locally. Install it and retry.
  • CSP version mismatch. Pin to 0.2.5-preview1 per the AC config doc.

“Setup token expired or already used”

Setup tokens are one-shot and live for 24 hours. Generate a fresh one from the admin console and re-bind. Existing rigs keep their long-lived rig token regardless.

Re-binding a rig

If you replace a PC or re-image the disk, you can re-bind the new agent to the same logical rig. Use PitwallOSAgent --rebindon the rig PC; it'll prompt for a new setup token. The existing rig in the admin console keeps its history.