> For the complete documentation index, see [llms.txt](https://crossban.thelukez.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crossban.thelukez.com/docs/troubleshooting.md).

# Troubleshooting

### Common Issues

* **Bot Not Responding**: Check if it's online in Discord. Verify token and permissions.
* **Database Errors**: Ensure PostgreSQL is running. Reinitialize the Docker volume if needed (deletes data!).
* **Bans Not Syncing**: Confirm "incoming bans" is enabled and servers are connected.
* **Logs Not Sending**: Set a logging channel and ensure the bot has message permissions.

### Logs and Debugging

* View Docker logs: `docker compose logs`
* Enable debug logging by setting a webhook in the env file with the key `LOGGING_WEBHOOK`. This will produce **a ton** of logs, so only use it for debugging purposes.
* If issues persist, check the bot's console output.
* Open a GitHub Issue if nothing works.

### Support

* Review the README for advanced tips.
* For code issues, open an Issue on GitHub.


---

# 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://crossban.thelukez.com/docs/troubleshooting.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.
