FiveM resource errors at startup

When a resource fails to start, FiveM prints a specific message in the txAdmin console. Knowing how to read it lets you fix it in two minutes.

Cause / The problem

Resource errors most often come from a missing dependency (oxmysql, another script), a Lua syntax error, a malformed fxmanifest.lua, or an incorrect load order (the resource starts before its dependency).

Solution

1. Open the txAdmin Live Console and look for the red lines containing failed to start or [script].
2. Read the full error message. A few common cases:
   • “resource xxx could not be found” — the folder does not exist or its name does not match the ensure line.
   • “attempted to call a nil value” — Lua error in the code or a missing dependency.
   • “No such function GetHashKey” — artifacts version is too old.
3. Check fxmanifest.lua: a missing comma or a wrong file path prevents the resource from starting. The file must correctly list client_scripts, server_scripts, shared_scripts.
4. Check the server.cfg order. A resource that depends on oxmysql must appear after ensure oxmysql.
5. Reinstall the resource if the folder is corrupted (missing files) — download it fresh from the official repository.
6. Review the detailed logs in txAdmin → Server log for the full error context.

To test a resource in isolation: stop all the others, then start my_resource in the console.