Dashboard troubleshooting
Problems that are specific to running and monitoring DAST scans from the Levo dashboard UI. For CLI / YAML / Docker runtime issues, see the main troubleshooting page.
Quick axis
- This page — UI-only: scan status stuck on the list page, logs tab empty, findings not appearing in the dashboard.
- Main troubleshooting — runtime failures from the CLI / Docker / Kubernetes / YAML validation.
Scan stuck in "Queued"
You clicked Start Scan and the run sits at Queued for more than a minute without moving to Running.
- Confirm the target domain is listed under Settings → Owned Domains. DAST refuses to scan domains you don't own.
- Check Settings → Firewall / IP Allowlist — your WAF or cloud provider may be blocking Levo's runner IPs. (Allowlist details.)
- Open the scan's Logs tab; if it shows
worker offline, start a worker — the scheduled or on-prem path needs one.
For CLI-side "exits immediately" behavior, see main troubleshooting → CLI.
Findings missing after a successful scan
Scan is Completed but the Findings tab is empty.
- Wait 1–2 minutes — post-processing runs after the scan finishes.
- Check the Logs tab for
post-processing failedentries. - Confirm
reporting.severity(dashboard field or YAML) isn't filtering everything out — set it tolowand re-check. - Verify Active Scanning was on (Step 4 of the Create Scan dialog). Passive-only scans on a small static site will legitimately find nothing.
Incomplete coverage (missing pages / endpoints)
- Raise Max Crawl Depth (default 3 → try 5–7) and Max Pages in Step 3.
- Check Exclude Domains / Exclude Paths on the scan's detail page for accidental filters.
- If the missing endpoints are behind a flow the crawler can't reach, switch the crawler mode to AI Assisted or Hybrid in Step 3.
Scan fails mid-run
Open the scan's Logs tab and look for the last line before the failure:
| Log line | Fix |
|---|---|
browser crashed | Worker is starved of /dev/shm — restart it with --shm-size=1g. |
target unreachable | Target went down mid-scan or network flapped. |
auth expired | Refresh the token / re-run form login; scans longer than the token lifetime need a refresh-issued token. |
For deeper CLI errors (e.g., Docker permission denied, YAML validation), see main troubleshooting.
Support
- Copy the scan ID from the dashboard URL (e.g.,
/scans/dast/abc-123). - Open Help → Contact Support from the dashboard, or email support@levo.ai with the scan ID.
Next
- Main troubleshooting — CLI, Docker, YAML.
- Managing findings — triage and export.
Was this page helpful?