Logs / Error guide / FiveM
FiveM: “Couldn't start resource …”
What the message means
FXServer couldn't start a resource from your server.cfg. The message itself only gives the name – you'll find the reason in the lines directly before it.
What it looks like in the log
[ c-scripting-core] Creating script environments for oxmysql
[ resources] Started resource oxmysql
[ resources] Started resource es_extended
[ resources] Couldn't start resource esx_garage.
[ resources] Started resource esx_policejob
Excerpt from an example log, marked the way the analysis marks it.
Common causes
- A dependency is missing (“Could not find dependency” directly before).
- The file fxmanifest.lua (or __resource.lua) is missing or contains an error.
- Folder name and the name in server.cfg don't match – on Linux, upper and lower case count.
- The resource is nested twice in the folder (resources/name/name/fxmanifest.lua).
- A script of the resource fails right at startup (SCRIPT ERROR).
How to fix it
- Read the lines directly before the message – the actual reason is almost always there.
- Check whether the resource's folder contains an fxmanifest.lua and whether the folder is named exactly as in ensure <name>.
- Install missing dependencies and start them in server.cfg before this resource.
- Try ensure <name> in the live console – the messages then appear right away.