Help
Troubleshooting
Fixes for the problems people run into most.
My domain won't verify#
Choose Verify and read the message under it. It says what's wrong.
- Record not found: wait a few minutes. If it still fails, check your DNS provider didn't add your domain twice, making
_auditgate.api.example.com.example.com. Enter just the short name. - Wrong value: paste the value again exactly, without extra quotes.
- Platform domain: addresses like
*.up.railway.appcan't be verified. Add a custom domain. - Changed the API address? A new domain needs a new record.
Check what the internet sees: dig +short TXT <record name> @1.1.1.1
A scan failed#
- Open the scan. Each check shows why it was skipped or failed.
- Use Test connection in project settings to check AuditGate can reach your API. It needs to be on the public internet, not behind an IP allow list.
- Only one active scan runs per project at a time.
- Check you haven't used this month's scans under Settings → Billing.
Authorization checks were skipped#
- Add test users under Scan test tokens. Cross-user checks need two; admin checks need a low-privilege user.
- Tokens expire. Call your API with the stored token yourself to check it still works, and use long-lived tokens for test accounts.
- Cookies and API keys need the header name:
Cookie: session=…orX-API-Key: ….
Some endpoints weren't scanned#
The scan page says how endpoints were found. To give it the full list, connect your GitHub repository, or publish a JSON OpenAPI document at /openapi.json. If every route needs sign-in, add a test user.
A finding looks wrong#
Check its confidence first: Unverified findings are leads, not proof. If it isn't a real problem, mark it False positive. It stops counting towards your health score and your feedback is recorded.
My CI job fails#
Print the status code and message from the response; the message names the problem.
| Status | Usually means |
|---|---|
| 401 | The token expired or was revoked |
| 403 | Wrong project ID, or the domain isn't verified |
| 402 | This month's scans are used up |
| 409 | Two pipelines tried to scan at once |
Webhook deliveries fail#
Open the alert rule's delivery history to see the error. Your endpoint must reply with a 2xx within 10 seconds, be public, and not redirect.
I can't do something in settings#
Your role may not allow it. Developers can't manage keys, tokens, members or billing. Ask a workspace owner.
Still stuck?#
Contact us with the project name and, for a scan problem, a link to the scan page.
