Reference

Troubleshooting

What jev-guard's messages mean and how to fix them.

Start with /jevguard status. If it says Moderation is OFF (check console), config.yml has a problem and the console says which.

Config errors

Message	Fix
`No TypeSafe API key. Set TYPESAFE_API_KEY or api.typesafe.key.`	Add your key. See TypeSafe.
`Cloudflare needs an account id and API token.`	Set both. See Cloudflare.
`api.provider must be 'typesafe' or 'cloudflare'`	Fix the spelling of `api.provider`.
`mode must be shadow, deliver or hold`	Fix the spelling of `mode`.
`config.yml defines no enabled categories`	Turn at least one category back on.
`'safe' is reserved and cannot be a category key`	Rename that category.

Run /jevguard reload after fixing it.

/jevguard test says Request failed: with the reason, and status counts errors. Usually:

The key or token is wrong, or the Cloudflare token lacks the Workers AI Read permission.
Your account is out of credit with TypeSafe or Cloudflare.
Too many requests. jev-guard retries and then backs off. See reliability.

In shadow mode nothing is hidden, by design. Check the server log.
In deliver mode cancel does nothing; the message is already out.
Check the message with /jevguard test. If the probability is just below the threshold, lower the threshold or sharpen the category description.
Players with jevguard.bypass are never checked.

Describe that chat in safe-description, raise the category’s threshold, or reword its description to exclude it.

Something wrong or missing on this page?Open an issue on GitHub.