Argus

Operating

Troubleshooting

The things that come up in tickets, in the order they come up. If yours is not here, the Discord is the fastest route.

Argus refuses to start

“another anti-cheat is running” — Argus will not run beside one, because two anti-cheats produce false positives in both. Remove the other, or if you are migrating and want a day of overlap, set Config.RefuseWithOtherAntiCheat = false for that day only.

“licence invalid” — the key must match the panel exactly. If you set both the convar and Config.LicenseKey, the convar wins; check that one.

“API unreachable” at boot — the server cannot reach api.arguss.ac on 443. Check outbound firewall rules on the host. Argus still starts, in whatever Config.OfflineMode says.

My own status says “bypassed”

You hold bypass without having granted argus.bypass. Two things count: a principal with command allow (the common add_ace group.admin command allow wildcard), and being authenticated as a txAdmin admin. To test detections against yourself, use an account with neither, or comment the wildcard out for the session. Bypass never hides detections — they are still recorded — it only stops the action.

A legitimate player was flagged or kicked

Open the detection in the panel. Every hit carries what was measured and what the limit was. Then, in order:

  1. Read the detection's legitimate causes in the catalogue. Most false positives are a script doing exactly what the catalogue says can trip it.
  2. Fix the number, not the detection. Armour over 100 from your EMS script: raise Max armour. A modded weapon: add it to the Weapon Table. Long-range hits on a sniper server: check the range in the table. Off-axis hits on a high-ping crowd: raise Behind the shoulder line under Combat tuning.
  3. Mark the hit as a false positive in the panel so it does not count against the player's Integrity Score.
  4. Only then consider lowering the action to flag, and record why in the note the panel asks for. Never add the script to Ignored resources — that makes Argus blind to it, which makes everything it does look like a cheat.

Detections show but nothing happens

You are in Learning Mode, or Enforcement is off, or the player is bypassed. argus status says which. Learning Mode ends on its own after the configured hours; you can end it early under Settings.

verify says a resource “never called in”

The resource started before Argus did, so its shim had nothing to report to. Restart that resource, or move ensure argus earlier in server.cfg. The shim keeps retrying for a while after load, so this usually clears on its own; if a resource stays silent across restarts, it is loading in a way the shim cannot see — open a ticket with the resource name.

A resource fails to start after argus install

First, read the actual error: script errors are never caused by Argus, and the integration adds two lines to a manifest and nothing else. If the resource genuinely will not load with the lines present, exclude it:

text
argus exclude the_resource

and open a ticket with its name and the error so it can be looked at. That is what the exclude list is for, and nothing else.

“unknown detection slug reported” in the console

The resource and the panel disagree about which detections exist, which means the resource folder is a different version from the one the panel offers. Download the current archive from the panel and replace the folder contents. The line is a warning; the report it refers to was dropped.

“This copy of Argus has been modified”

Every release carries a digest of the code it shipped, and at boot the resource hashes its own files and reports what it got. A copy whose digest does not match has been edited, patched or rebranded — and the API can decline to serve it. Only config.lua is yours to edit; it is excluded from the digest, as are locales. If you see this on a build you downloaded from the panel and did not touch, something on the way to the box rewrote a file — download it again, replace the folder contents, and if it persists open a ticket with the server id. Line endings are not the cause: the digest folds them.

Removing Argus

text
argus uninstall     -- strips every integration line, from the server console
stop argus

then remove ensure argus, the exec @argus/data/permissions.cfg line and the folder.