Common errors
Map VisibleMax error messages and statuses to concrete next actions.
Updated 2026-08-06
Use this page as a quick index. Match the message or status you see, apply the fix, then follow Recovery steps if needed.
Errors and next actions
| Message / status | Meaning | What to do |
|---|---|---|
| Website unreachable / connection failed | Crawl could not fetch the origin | Website unreachable |
| DNS / NXDOMAIN | Hostname does not resolve | Fix DNS; wait for propagation; rescan |
| SSL / certificate error | TLS handshake failed | Renew/fix cert chain and hostname match |
| 403 / 503 / challenge / bot detected | WAF or bot blocking | Adjust CDN/WAF; retry once |
| Timeout / aborted / deadline | Fetch or pipeline exceeded time budget | Speed up origin; reduce blocks; see Slow scans |
| Scan failed (crawl step) | Hard fail before analyze | Scan failed |
| Partial / platforms missing | Provider skip or soft-fail | AI provider unavailable |
| Free includes one AI visibility scan… Upgrade… | Lifetime Free scan used | Upgrade to Pro Early Adopter (7-day trial, then $50/year) via Polar |
| upgrade_required | Entitlement gate | Subscription · Payment |
| Checkout canceled / payment failed | Polar payment incomplete | Payment issues |
Status guide
- queued — waiting for Trigger.dev worker; usually brief
- running / crawl — fetching pages
- analyzing — building the report
- completed — core success (probes may still enrich briefly)
- partial — usable report with soft-failed sections
- failed — hard failure; read
error_messageand recover
Edge cases
- Generic “Scan pipeline failed” — treat as hard fail; include scan ID for support
- Empty error with failed status — still send screenshots and timestamps
- UI says failed but report exists — prefer report data; probe may have soft-failed after unlock
When to contact support
If the table does not match your message, or the recommended fix fails twice, contact support.
FAQ
Where do I find the scan ID?
Open the scan detail URL in the app — the path includes the scan ID. Copy the full URL into your support email if unsure.
Are error strings stable?
Wording can evolve. Prefer matching the category (DNS, SSL, timeout, upgrade_required, partial) over exact punctuation.
Do screenshots help?
Yes — especially for checkout, entitlement, and progress UI issues. Redact secrets; include project URL and scan ID in the email body.
Related
Still stuck? Contact support with your project URL and what you already tried.