FiveM 'Couldn't find resource' – Fix
The error
Couldn't find resource my-resource. Failed to start resource my-resource.
What it means
FXServer looked for a folder with that exact name that contains fxmanifest.lua (or a legacy __resource.lua) and did not find one. This is different from “Couldn't load resource”, which means it found a folder but could not read a valid manifest. Here the name after ensure does not match a visible resource.
The fix
-- The folder name is the resource name
-- resources/[local]/my-resource/fxmanifest.lua correct
-- resources/[local]/my-resource/my-resource/... too deep
-- resources/[local]/my-resource-main/... GitHub zip name
# server.cfg — must match the folder, including case and hyphens
ensure my-resource
Unzipped GitHub downloads often create my-resource-main or a doubled folder. Move the inner folder up so the manifest sits directly inside the folder you name in server.cfg. On Linux hosts the match is case-sensitive: ensure vmenu will not find vMenu. Category folders such as [standalone] are fine; you still ensure the inner resource name (or the whole category).
After you fix the files, you do not always need a full restart. In the console run refresh then ensure my-resource. If the same error prints again, the folder is not in the resources directory that this server.cfg actually loads (txAdmin recipes sometimes use a different data folder).
These steps are for creators and server owners working on their own scripts. Test the change on a development server or in Studio before you put it live.
Related tools: FiveM script generator · Fix a FiveM Lua error · all script generators