> For the complete documentation index, see [llms.txt](https://studioworks.gitbook.io/studioworks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studioworks.gitbook.io/studioworks-docs/support/finding-logs.md).

# I need to find my error logs

Find the relevant error and remove sensitive values before sharing.

## Server console

Use the console or logs in txAdmin or your hosting panel. Find the time when you started the resource or performed the failing action.

Copy a continuous excerpt beginning with the **first relevant error**. Keep the resource name and timestamps visible. Log storage locations depend on your installation and host.

## Client console

Open the F8 console in FiveM, reproduce the problem, and capture the relevant error. Record the action and time. If the message disappears quickly, add a screenshot or short video.

## Crash information

Keep the exact crash message or identifier if one is displayed. Describe whether only your client or other players are affected. Send large dumps only through a private method requested by support.

## Remove before sharing

* Server license keys and API tokens.
* Database passwords and full connection strings.
* Webhook URLs and other access links.
* Personal information that is not needed for the investigation.

Keep technical error messages, filenames, and line numbers readable where possible. Replace a secret value with `[REMOVED]`.

## Context matters

A short complete sequence with timestamps is better than multiple unrelated screenshots. Label each excerpt with the test that produced it. Mixing logs from different tests can lead to the wrong diagnosis.

[Return to the ticket template](/studioworks-docs/support/preparing-a-ticket.md).

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# 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://studioworks.gitbook.io/studioworks-docs/support/finding-logs.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.