Fix FiveM resource filename case problems after moving to Linux
A FiveM resource that worked on one machine may fail after a move to a case-sensitive filesystem. A reference to Config.lua is not interchangeable with an actual file named config.lua there. Investigate the exact missing path rather than reinstalling the whole framework or clearing unrelated server data.
Preserve and locate the failure
Save the first file-not-found error and the resource name. Download a private copy of the affected resource before editing. Record its release and compare its directory layout with the author's original package. Keep configuration containing credentials out of public issue reports.
Check whether the archive added an extra outer folder. A resource manifest buried inside a second copy of the resource directory is a packaging problem, not necessarily a case problem. First confirm which folder the server actually starts and whether it contains the expected fxmanifest.lua.
Compare literal paths
- Open the manifest and compare each reported script, file and UI path with the real filename, character for character. The Cfx manifest reference explains how those files are declared.
- Check directory names as well as the final extension. A correct
menu.jsstill cannot be found through the wrongHTML/directory name. - For a browser interface, inspect references inside its HTML and stylesheet files too. A manifest can load the page successfully while an image or JavaScript import uses different case.
- Look for two files that differ only by case. Compare their contents and the author's release before deciding which one is intended. Do not overwrite one with the other on your local computer.
- Correct the smallest proven mismatch in a test copy. Prefer the author's documented naming convention and avoid broad search-and-replace across unrelated resources.
Move the corrected copy carefully
If your editor or file manager does not register a case-only rename, rename through a temporary unique name, then the intended final spelling. Do this in a stopped test copy so the resource cannot briefly load an incomplete path. Git's configuration reference documents filesystem-related case handling; do not change repository case options blindly to conceal a genuine filename conflict.
Upload the complete corrected resource and compare the resulting filenames in the panel. Keep the previous version in your private backup, outside the active resource search path. Avoid leaving duplicate working copies with confusing names in folders that the server automatically starts.
Verify the affected feature
Start the resource on staging and check that the original error is gone. Open the specific menu, load the relevant asset or run the action that previously failed. Look for new missing-file errors rather than accepting an empty interface as success.
If the correction fails, restore the saved resource and configuration together, then reassess packaging, build output and declared dependencies. Some packages require a build step and do not ship their generated web assets. An encrypted or vendor-managed resource may require an upstream fix; do not edit protected files. Apply the verified minimal correction to production only during an appropriate maintenance window.