The resource does not start

Start with the server console (or txAdmin's live console). Restart the server, then search the output for the resource name. The first red line about it is usually the cause; later errors often follow from it.

Paste that output into the error doctor of the free FiveM Script Tester: it explains known FXServer and txAdmin errors in your browser and redacts license IDs, IPs and keys. With the resource loaded too, it points at the file and line.

Couldn't find resourceCopy Anchor Link

The server cannot find a folder with that name and an fxmanifest.lua inside it.

• Name mismatch. The name after ensure must match the folder name exactly, including - and _.
• Folder inside a folder. The zip often unpacks to resource_name/resource_name/fxmanifest.lua. Move the inner folder up so fxmanifest.lua sits directly in the resource folder.
• Wrong place. The folder must be inside resources (or a [bracket] folder within it) of the server that reads this server.cfg.
• Old manifest. Very old resources use __resource.lua. They still load, but are rarely maintained; check for a newer version.

A dependency is missingCopy Anchor Link

A message that names another resource as a dependency means the resource lists it in its fxmanifest.lua and the server does not have it, or it is not started.

1. Install the named resource (the product description lists the required ones).
2. Start it before the resource in server.cfg.
3. Check the spelling: the dependency name must match that resource's folder name.

A manifest or Lua file fails to loadCopy Anchor Link

Read the first parse error and its file/line number. Check your latest config or item edits for a missing comma, quote or closing bracket, and compare with the backup. Preserve the supplied manifest; renaming files or inventing an export does not repair incompatible code. If the untouched release fails, send the error and resource version to support.

For a newly copied resource that FXServer does not yet list, run refresh in the server console, then ensure resource_name, or restart the server. Core, item and job changes may still require a full restart.

Asset Escrow and entitlementsCopy Anchor Link

You lack the required entitlement means the server is not authorized to run that protected asset. This is different from the RPScripts download API's no_entitlement error, which concerns your shop account.

Check the creator's delivery instructions and that the asset is granted to the intended Cfx.re account. Verify the server registration key belongs to that account without sharing the key. Keep the supplied protected files intact and use a supported FXServer version. If access is missing, contact the seller with the order reference; do not try to bypass protection.

Asset Escrow availability also depends on the GTA V edition. Check the current Cfx.re Asset Escrow documentation and Legacy/Enhanced migration notes rather than treating a framework badge as proof.

SCRIPT ERROR linesCopy Anchor Link

The resource starts, but its code fails. The line shows the file and line number:

SCRIPT ERROR: @resource_name/server/main.lua:42: attempt to index a nil value

Common causes, in this order:

1. Framework object is nil (QBCore, ESX): the framework starts later, or it is the wrong framework. See QBCore, ESX, Qbox.
2. Config points at a resource you do not run: inventory, target, notify or fuel set to something else. Check config.lua.
3. No such export: the script calls a resource that is not started or has a different name on your server.
4. Database errors such as missing tables: see Database errors.

It starts but nothing happens in gameCopy Anchor Link

• Items: registered in the framework? See your framework page.
• Jobs: does your character have the job and grade the config requires?
• Client errors: press F8 in game and look for red lines that mention the resource.
• Maps and vehicles: check for a conflict with another resource that streams the same files.

Still stuckCopy Anchor Link

Collect the relevant console output from server start, the resource's config.lua settings you changed and your framework version. Redact passwords, server keys and tokens, then contact support. For client-side crashes and error codes see FiveM error codes.