Troubleshooting
Step-by-step guidance for the most common issues security and engineering teams hit when running VulnProScan Vuln Pro Scan.
Login problems
- Confirm you are using the email address provisioned for your workspace.
- Use “Forgot password” on the login page to rotate credentials.
- Clear site data for vulnscan hostnames if SSO or cookies were updated recently.
- If your organization enforces IP allowlists, verify your network is permitted.
Scan does not start
- Check that the scanner backend (ZAP) is reachable from the environment running VulnProScan Vuln Pro Scan.
- Retry after a minute in case a previous scan is still draining worker capacity.
- Open the browser network tab and confirm /api/pentest returns JSON, not HTML or 404.
- Review server logs for rate limiting or upstream proxy errors.
Invalid URL errors
- Include http:// or https:// at the beginning of the target.
- Remove trailing spaces or hidden characters copied from documents.
- Avoid file:// or internal-only hosts unless the scanner has network path to them.
Slow scan performance
- Large single-page apps may require longer crawl phases—be patient or narrow scope to a path.
- Throttle other synthetic traffic hitting the same environment during the scan window.
- Check target latency; high round-trip times extend both spider and active phases.
Empty or incomplete results
- Some applications block automated clients—review WAF or bot management rules.
- If authentication is required, ensure a reachable test account or static token path exists.
- Partial output can appear when scans time out; rerun with a smaller URL subtree.
Report generation issues
- Copy the raw findings panel as a temporary workaround while export services catch up.
- Verify your browser is not stripping downloads from pop-up blockers.
- For Enterprise PDF bundles, confirm billing status and storage quotas with support.