Couldn't start resource
The server won't start a resource and shows "Couldn't start resource". The 4 real causes (manifest, dependencies, syntax and files) and how to fix it.
The problem
When you ensure or start, the console responds "Couldn't start resource <name>" and the resource stays stopped.
The cause
It's almost always: an invalid or missing fxmanifest.lua, a script file that doesn't exist at the given path, a dependency that isn't started, or a Lua syntax error that prevents the resource from loading.
The solution
Check the manifest and that every referenced file exists:
lua
-- minimal valid fxmanifest.lua
fx_version 'cerulean'
game 'gta5'
client_scripts { 'client.lua' } -- the file MUST exist
server_scripts { 'server.lua' }
-- dependency 'es_extended' -- if you depend on a frameworkStep by step
- 1.Look at the line JUST above "Couldn't start resource": it usually states the exact cause (file not found, syntax error...).
- 2.Confirm that `fxmanifest.lua` exists with `fx_version` and `game 'gta5'`.
- 3.Verify that every file in client_scripts/server_scripts exists at that exact path.
- 4.If it depends on a framework or library, start it first with ensure.
Related guides
Last updated: 2026-06-19. Crxative-M is not affiliated with Cfx.re or Rockstar Games.
