Resource dependency failed to start (FiveM)
FXServer's resource system resolves dependencies before starting anything. If resource A declares that resource B must be running and B fails to load or isn't in server.cfg's ensure list, A refuses to start and logs 'Dependency Y failed to start'. The fix is straightforward: install the missing resource and ensure it is started before the resource that needs it.
Fastest path: paste your crash report into the Crash Doctor — it identifies this pattern and 40+ others automatically. No signup.
How to fix it
- 1
Read the log to find the missing dependency name
The error message names both the dependent and the dependency: '[scriptname] has a dependency on [missingname], which failed to start'. Write down 'missingname' — that's what you need to install.
- 2
Download and install the missing resource
Search for the dependency on the CFX.re community forums, GitHub, or the resource's documentation page (most resources list their deps in the README). Drop the resource folder into your FXServer/server-data/resources/ directory.
- 3
Add ensure lines in the correct order in server.cfg
Open server.cfg and add 'ensure missingname' BEFORE 'ensure scriptname'. FXServer processes ensures top-to-bottom; if the dependency line comes after the caller, it still fails even though the resource is installed. Dependency before dependent — always.
- 4
Restart FXServer and verify both resources show [started]
After restarting, check the server console. Both resources should print '[started]' on their lines. If the dependency itself fails with its own error, read that error next — it may have its own dependencies or a config issue.
Alternative causes
These can produce the same error message — worth ruling out if the steps above don't resolve it.
Wrong resource folder name
FXServer identifies resources by folder name. If the dependency is named 'oxmysql' in the code but you dropped the folder in as 'oxmysql-main' (a common GitHub download artifact), the dependency lookup fails because 'oxmysql-main' != 'oxmysql'. Rename the folder.
Resource is in a subfolder not on the resource path
If resources live in nested directories, server.cfg must include the parent: 'ensure [some-category]' to scan the category folder, or explicit 'ensure some-category/scriptname'. Resources that aren't on the path are invisible to the dependency resolver.
Frequently asked
How do I find all dependencies for a resource?
Look in the resource's fxmanifest.lua file for the 'dependencies' table. It lists every resource that must be running. The README usually explains them too, with download links.
Can a resource have optional dependencies?
Not in the fxmanifest dependencies table — those are hard requirements. Some scripts handle optional integrations in Lua with Citizen.GetPlugin or exports checks at runtime, but those don't appear as dependency errors on startup.
What's the order of ensure lines in server.cfg?
Alphabetical order is tempting but wrong. Order by dependency graph: frameworks first (es_extended, qb-core), then framework dependencies (oxmysql), then resources that depend on those. When in doubt, put the dependency at least one line above its caller.
Want this auto-fixed on your server?
CoalHosting's Minecraft hosting runs the same pattern database against every crash and applies the known fix before your players notice. Free crash diagnosis works on any server, hosted or not.
Related crashes
License key was not accepted (FiveM / FXServer)
Fix the FiveM 'license key was not accepted' error — your sv_licenseKey in server.cfg is invalid, expired, or …
oxmysql / mysql-async: Database connection failed (FiveM)
Fix FiveM oxmysql or mysql-async 'database connection failed' errors — wrong connection string, MySQL not runn…
FXServer crash loop (server keeps restarting)
Fix a FiveM FXServer crash loop — the server restarts immediately after starting. Read the last log, find the …
Last reviewed 2026-06-15. If a step is wrong or out of date, tell us — we'll fix the article and the auto-pattern at the same time.