How to fix "lacking entitlement" in FiveM
Updated 29 Oct 2026 · 2 min read
On this page
"Lacking entitlement" is the most common error when starting a paid FiveM script. It means the server could not confirm that the script was bought by the account that owns the server. The script itself is fine; the fix is almost always on the account side.
You'll usually see it in the server console like this:
[ERROR] Resource 'zerio-bossmenu' is lacking entitlement
Failed to start resource: lacking entitlement
Why it happens
FiveM Asset Escrow ties every purchase to a Cfx.re account. When a protected resource starts, the server checks whether the account that owns its license key (sv_licenseKey) has been granted that asset. If the accounts don't match, the resource refuses to start.
The usual causes, most common first:
- The license key belongs to a different account than the one used at checkout. This happens a lot with game server hosts that generate keys under their own account.
- The server wasn't restarted after the purchase, so it is still using old entitlement data.
- The files weren't downloaded from the Cfx.re Portal under the buying account.
Fix 1: check who owns the license key
- Sign in to portal.cfx.re with the account you bought the script with.
- Check Granted Assets: the script should be listed there.
- Check Server Keys: the key your server uses must be listed under this same account.
If the key isn't there, create a new key under the buying account and replace it in your server.cfg:
sv_licenseKey "your-new-license-key"
On a hosted server, set the license key in your host's control panel instead; many hosts override server.cfg.
Fix 2: restart the whole server
Entitlements are loaded when the server starts. Restarting just the resource (restart zerio-bossmenu) isn't enough; restart the server process itself after buying or after changing the license key.
Fix 3: download a fresh copy
Download the script again from Granted Assets on the Portal while signed in to the buying account, and replace the folder on your server. Copies shared from another account or an old backup will not work.
Bought on the wrong account?
Contact us on Discord with your order details and the account you meant to use, and we'll help sort it out.
Still stuck?
Check the installation guide to make sure nothing was skipped, then open a ticket in our Discord with the full console output.