Troubleshooting & Sandbox
Test connectivity, read the module logs, decode common API errors, and use sandbox mode safely.
First checks
- Test API (module admin) calls the health endpoint with your configured URL and key. Run it after any configuration change.
- Logs (module admin) record every API call with payloads. Enable Debug Mode temporarily for more detail.
Common errors
| Error | Cause and fix |
|---|---|
TENANT_MISMATCH (403) | The API key does not belong to the domain in *Aegis API URL*. Set the URL to your portal domain, the one shown next to the key in portal settings. |
Unauthenticated. (401) | Missing or stale API key. Regenerate in the portal and update the module config. |
ACCOUNT_SUSPENDED (403) | Your partner account is suspended. Contact support. |
ENDPOINT_LIMIT_EXCEEDED / DOMAIN_LIMIT_EXCEEDED (403) | The customer's plan is full. Upgrade the plan or free a slot, then retry from Tools. |
DNS_RESOLUTION_FAILED (422) | A hostname the customer added does not resolve. Have them use the IP directly. |
RATE_LIMITED (429) | Manual scans have a per-endpoint cooldown; the response says how long to wait. The module surfaces this to customers automatically. |
Sandbox mode
With Sandbox Mode on, the module sends X-Aegis-Sandbox: true on provisioning calls, so everything is simulated: no scans run and no wholesale charges accrue. Pick the mock scenario in the module settings: clean (no issues), warnings (web ports) or critical (database ports). Your test customers see matching mock results.
Sandbox auto-disables when your onboarding completes; it can be re-enabled from the portal for later testing. The Sandbox API exposes the same controls for custom integrations.
Still stuck?
Collect the relevant module log entries (they include request IDs) and contact us. Partner support responds fast.