Troubleshooting

Find the next useful check when something in Pro does not behave as expected.

Choose the symptom that matches what you see.

Loading and setup

New menu labels are missing

Reload the intended JAR and check its full path in Burp. The current menu has Local Scanner and Burp Bounty Server Scanner.

Profiles/rules are empty

Settings → General must point to the base BurpBountyData directory. Reload and inspect malformed JSON errors.

Server remains unhealthy

URL, reachability, enabled state and the server's license key. Use the REST base URL without /mcp.

Remote passive issue only appears in Burp

Confirm the updated JAR is loaded; current remote ingestion also updates Scanners → Passive.

License native-library error on Apple Silicon

Use the current complete JAR with its JNA resources, then unload/reload the extension.

Scans and findings

Scan is Finished without a Collaborator issue

Finished does not prove out-of-band coverage. Check provider availability, profile requirements and warnings.

Local scan is Incomplete

Some requests completed before interruption/error/timeout. Inspect evidence and remaining coverage.

Local/Server request totals differ

Compare profiles, original service/response, insertion points, strategy, redirects and engine compatibility.

Remote row is Reconnecting

The server may still be scanning. Restore connectivity and reconcile the same ID before resubmitting.

Automation

Smart Scan does not launch the intended profile

Check exact rule references and enabled state; review the documented rule limitations.

AI analysis completes but no active scan starts

Check auto-scan, enabled/available profiles and the structured model response.

Does a remote Cancel stop server work?

Pro sends cancellation to the scan's owning server. A network failure can prevent immediate delivery or confirmation. Wait for the confirmed state; closing a window is not evidence that server execution stopped.

Can I use the same profiles everywhere?

The .bb format is shared, but a shared file format is not a guarantee of identical execution. See compatibility, especially redirect modes, cookie reuse, variation matching and Pro-only planning.

Is the Server MCP the same as Burp Suite MCP?

No. Burp Bounty Server's optional Streamable HTTP endpoint is normally /mcp on port 8081. A separate Burp Suite MCP extension can expose Burp's tools on another port. Register them as separate client connections.

For server-specific startup, authentication, catalogue or history problems, use Server troubleshooting.