> For the complete documentation index, see [llms.txt](https://five-customs.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://five-customs.gitbook.io/docs/troubleshooting.md).

# 👷‍♂️ TROUBLESHOOTING

## Resource fails to start

* Read the first server-console error; later errors may be consequences.
* Check that the resource folder name matches the `ensure` entry.
* Confirm dependencies are installed and started first.
* Check for missing files or incorrect case in file paths.
* Verify the server artifact supports the resource's manifest features.

## Framework not detected

* Set the framework option explicitly if the resource supports it.
* Confirm the intended framework is started before the resource.
* Avoid starting multiple independent cores unless supported.

## SQL or database errors

* Confirm `oxmysql` (if required) is started and configured.
* Check connection settings and database permissions.
* Import the matching SQL file once and inspect the exact error message.
* Back up data before attempting schema changes.

## Items or interactions do not appear

* Verify inventory and target settings.
* Register the supplied item definitions for your inventory.
* Confirm item names, target resource names, job names, and permissions.
* Check client F8 and server logs for missing exports or events.

## UI is blank or does not open

* Check NUI paths in `fxmanifest.lua`.
* Ensure the packaged HTML, JavaScript, CSS, and assets were not removed.
* Check F8 for NUI/JavaScript errors.
* Clear client cache only after confirming the resource files are correct.

When asking for support, include the resource name/version, framework, inventory, dependency versions, exact error text, and the steps that reproduce the issue. Never post database passwords, license keys, or other secrets.