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

# Troubleshooting & FAQ

Fixes for the most common Striga Core problems.

{% hint style="info" %}
Start with the server console. On a good start striga-core prints `striga-core 0.1.0 ready (framework: ..., inventory: ..., notify: ...)`. No such line? Fix that first: no Striga script works without it.
{% endhint %}

<details>

<summary>A Striga script does not start</summary>

* Check `ensure striga-core` comes **before** the script in `server.cfg`.
* Look for a red `needs striga-core >= ...` line in the console. If you see it, update striga-core.
* After `restart striga-core`, FiveM stops the scripts that depend on it. `ensure` them again, or restart the server.

</details>

<details>

<summary>Console: "... did not start, striga-core stays disabled"</summary>

Your framework did not start within 30 seconds. Check it is installed and started, and that ox\_lib starts before it.

</details>

<details>

<summary>The wrong framework is used, or standalone</summary>

The framework resource did not run, or has another name. Set it by hand in `config.json`, e.g. `"framework": "qbcore"`. An `unknown framework` warning means the name is spelled wrong. See [Frameworks](/docs/striga-core/integration/frameworks.md).

</details>

<details>

<summary>Error: attempt to index a nil value (global 'MySQL')</summary>

txAdmin uses the old manifest. Type `refresh`, then `ensure striga-core`. Also check oxmysql is installed and running.

</details>

<details>

<summary>ox_lib error, or lib is nil</summary>

ox\_lib is missing or starts after the framework. Put `ensure ox_lib` at the top. ox\_lib needs FXServer artifact 7290 or newer and OneSync.

</details>

<details>

<summary>Staff checks always fail</summary>

The group is not in `staff.groups`, or your framework does not give that group. Quick fix: `add_ace group.admin striga.staff allow`.

</details>

<details>

<summary>A notification has no title or icon</summary>

The notify system you picked does not show that field (QBCore shows no icon or position). Use `"notify": "striga-notify"` or `"notify": "ox_lib"`. See [Notify](/docs/striga-core/integration/notify.md).

</details>

<details>

<summary>Fuel always shows full</summary>

Your fuel script is not in `fuel.resources`. Add its name there, restart striga-core and the HUD. See [Fuel](/docs/striga-core/integration/fuel.md).

</details>

<details>

<summary>ESX: no hunger or thirst</summary>

`esx_status` is not installed, or `esx.statusResource` has the wrong name.

</details>

<details>

<summary>My custom adapter is not used</summary>

* Check the console: a missing function is named there (`... adapter "my-x" is missing function ...`).
* Check the name in `config.json` matches the name you registered. If it is not registered (yet), core warns and uses auto detection.
* Register again when striga-core restarts (`onResourceStart` / `onClientResourceStart`).

</details>

<details>

<summary>I never see an UPDATE line</summary>

That is normal when everything is up to date. Check `"versionCheck"` is not `false`. Set `"debug": true` to see a green `all Striga resources up to date` line. A yellow `version check failed` line means GitHub could not be reached; core tries again in 6 hours.

</details>

{% content-ref url="/pages/yGREkGui961z8NSGqAfh" %}
[Updates & Versions](/docs/updates-and-versions.md)
{% endcontent-ref %}


---

# 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://striga.gitbook.io/docs/striga-core/troubleshooting-and-faq.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.