> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.proto.xyz/fleet/llms.txt.
> For full documentation content, see https://docs.proto.xyz/fleet/llms-full.txt.

# Proto Fleet Support

Proto Fleet is open source and supported by its community. Here's where to go for help.

## Ask a question

Head to [GitHub Discussions](https://github.com/block/proto-fleet/discussions) for general questions, setup help, or to share what you're building.

## Report a bug or request a feature

Open an issue on GitHub. The issue chooser has three templates:

* **Bug Report** — something is broken or behaving unexpectedly.
* **Feature Request** — suggest a new feature or improvement.
* **Miner Compatibility Issue** — report a problem with a specific miner model or firmware version.

File issues at [github.com/block/proto-fleet/issues](https://github.com/block/proto-fleet/issues).

## Report a security vulnerability

Please **don't** open a public issue for security problems. Follow the process described in [SECURITY.md](https://github.com/block/proto-fleet/blob/main/SECURITY.md) in the repository.

## Common issues

A short list of things that trip up new installs:

* **Miners aren't discovered.** Confirm Fleet can actually reach the IPs or subnets you're scanning — either by [enabling host networking in Docker](/fleet/installation#make-miners-reachable), or by pointing Fleet at subnets the host can already route to.
* **Pairing fails.** Confirm the miner's firmware is supported and that the discovery port listed in [supported hardware](/fleet/home#supported-hardware) is reachable from the Fleet host.
* **UI won't load after install.** Check that Docker is running and the Fleet containers are healthy (`docker ps`). If they're restarting, their logs usually point at the cause.