> For the complete documentation index, see [llms.txt](https://docs.bountysecurity.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bountysecurity.ai/burp-bounty-pro/faq.md).

# 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

<details>

<summary>New menu labels are missing</summary>

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

</details>

<details>

<summary>Profiles/rules are empty</summary>

On a new installation, place a valid `BurpBountyData` pack beside the release JAR for automatic detection. An existing configured directory takes precedence. In Settings → General, check that Directory points to the base `BurpBountyData` directory, reload and inspect any validation errors. See [data pack setup](/burp-bounty-pro/installation.md#configure-the-data-pack).

</details>

<details>

<summary>Will a JAR update keep my license, servers and AI settings?</summary>

Yes, when their saved user storage is retained. The current version stores these settings outside the JAR and imports existing Burp preferences. Replacing the JAR on the same machine does not require clearing settings or re-entering every credential. Check Settings → Storage and the [migration guide](/burp-bounty-pro/installation.md#persistent-user-storage) if something is missing.

</details>

<details>

<summary>The default settings directory is not writable</summary>

Choose an empty writable directory in Settings → Storage and reload the extension. For managed installations, set `BURPBOUNTYPRO_HOME` to an absolute writable directory before starting Burp. Write access beside the JAR and administrator privileges are not required. See [restricted computers and custom locations](/burp-bounty-pro/installation.md#restricted-computers-and-custom-locations).

</details>

<details>

<summary>Server remains unhealthy</summary>

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

</details>

<details>

<summary>Remote passive issue only appears in Burp</summary>

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

</details>

<details>

<summary>License native-library error on Apple Silicon</summary>

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

</details>

## Scans and findings

<details>

<summary>Scan is Finished without a Collaborator issue</summary>

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

</details>

<details>

<summary>Local scan is Finished but the request count is below the total</summary>

Finished means execution ended; it does not guarantee complete coverage. Local scans that complete some requests before an error, interruption or timeout also display Finished in green. Actual counts, findings and retry eligibility remain available. Review warnings and failed requests before deciding whether to repeat the affected checks. See [scan states](/burp-bounty-pro/scan-control.md#states).

</details>

<details>

<summary>Clear removed the rows but requests are still being sent</summary>

Clear removes the displayed history and evidence views without cancelling running work or removing Burp findings. Cancel work first when you want it to stop. Remove Selected requests cancellation and removes those rows. If a batch is still being prepared, newly admitted scans can appear after Clear. See [Active table controls](/burp-bounty-pro/scan-control.md#clear-the-active-scanner-table).

</details>

<details>

<summary>The scan does not reach the configured requests per second</summary>

RPS is an upper limit. Throughput also depends on concurrency, response times, available workers and profile execution. Compare the local timing summary in the extension Output tab with target-side measurements before increasing concurrency. See [investigating low local throughput](/burp-bounty-pro/scan-control.md#investigating-low-local-throughput).

</details>

<details>

<summary>Local/Server request totals differ</summary>

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

</details>

<details>

<summary>Remote row is Reconnecting</summary>

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

</details>

## Automation

<details>

<summary>Smart Scan does not launch the intended profile</summary>

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

</details>

<details>

<summary>AI analysis completes but no active scan starts</summary>

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

</details>

## 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](/creating-profiles/compatibility.md), 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](/burp-bounty-server/troubleshooting.md).