> For the complete documentation index, see [llms.txt](https://hayston.gitbook.io/flp-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hayston.gitbook.io/flp-wiki/operations-and-troubleshooting/reporting.md).

# Report a problem

Open an issue in [FastLoginPlus](https://github.com/Hayston1001/FastLoginPlus/issues), not accidentally in the upstream FastLogin project. Read existing reports first.

Include:

1. FLP version **and commit/build source**, especially for development builds or a JAR copied from another server.
2. Server/proxy type and exact version, Java runtime, auth plugin version, and relevant ProtocolLib/Floodgate/Fabric mods.
3. Deployment: direct or proxy, forwarding mode, which side contains each plugin, and storage type. Do not reveal secrets.
4. Account situation: new or existing, password or bound, Java or Bedrock/linked, expected UUID policy and recent commands/upgrades.
5. Numbered reproduction steps, expected result and actual player-visible result. Say whether reconnect/restart changes it.
6. Sanitized startup and one attempt's debug logs from both proxy and backend, plus relevant config. Include timestamps so the attempt can be correlated.
7. What you have already tried and the result of each attempt.

Remove passwords, generated credentials, proxy IDs, forwarding secrets, private IPs if needed and personal data. Never attach the full authentication database. If the issue is a vulnerability or account takeover, use GitHub's private vulnerability reporting where available rather than publishing exploit details or live secrets in a public issue.

For documentation problems, include the page link and the incorrect text. For login problems, include the message the player actually saw; a skin alone does not establish whether verification succeeded.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hayston.gitbook.io/flp-wiki/operations-and-troubleshooting/reporting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.