Guide Β·
Fix "You Lack the Required Entitlement" in FiveM (Escrow Error)
Why FiveM says you lack the required entitlement for an escrowed script, and the six checks that fix it: license key account, granted assets, FTP transfer mode, artifacts and more.
You bought a script, put it on the server and the console prints:
You lack the required entitlement to use my_scriptor its sibling:
Failed to verify protected resource my_scriptBoth come from FiveM Asset Escrow, the system that encrypts paid scripts and ties them to the Cfx.re account that bought them. The script itself is fine. The server just cannot prove that it is allowed to run it. Work through the checks below in order; the first one fixes most cases.
1. The license key belongs to a different account
Escrow checks the account that owns your server's sv_licenseKey, not the account you are logged into in-game.
- Open portal.cfx.re with the account you bought the script on.
- Go to Assets β Granted Assets and confirm the script is listed there.
- Go to Servers and look at the license keys on that same account.
- Compare it with the key in your
server.cfg(or in txAdmin under Settings β FXServer).
If the key was created on a friend's or an old account, either generate a key on the buying account and swap it in, or ask the seller to transfer the asset.
2. The server was not restarted after the purchase
The server checks entitlements when it boots. If you bought the script, or swapped the license key, while the server was running, do a full restart of FXServer. Restarting just the resource is not enough.
3. The files were damaged on upload
Escrowed scripts contain an encrypted .fxap file and encrypted .lua files. If even one byte changes, decryption fails with "Failed to verify protected resource".
- FTP in ASCII mode rewrites line endings. In FileZilla set Transfer β Transfer type β Binary and upload again.
- Do not open and save encrypted files in an editor.
- Git and some panels may convert line endings too. Upload a fresh copy from the original archive.
Only files listed as editable (usually config.lua, locales and anything in the escrow_ignore list of fxmanifest.lua) may be changed.
4. The .fxap file is missing
Some archive tools and hosting panels hide files that start with a dot. Check that .fxap sits next to fxmanifest.lua on the server. If it is missing, extract the original archive again with 7-Zip or WinRAR and upload the whole folder.
5. Server artifacts are too old
Escrow needs a reasonably recent FXServer build. If your artifacts are a year or more old, update them to the current recommended build from the official artifacts page (or the Linux equivalent), or in txAdmin use the update button on the dashboard.
6. The asset was refunded or charged back
A refunded or disputed payment removes the entitlement automatically. In that case the script will not run again until the purchase is valid.
Quick checklist
| Check | Where |
|---|---|
| Script listed under Granted Assets | portal.cfx.re β Assets |
| License key on the same account | portal.cfx.re β Servers |
| Full server restart done | txAdmin or your host panel |
| Files uploaded in Binary mode | FTP client settings |
.fxap file present | Resource folder on the server |
| Artifacts up to date | txAdmin dashboard |
Still stuck?
If you bought a SleepyCode script and all six checks pass, open a ticket on our Discord with the exact console line and the Cfx.re username you bought on. Every one of our FiveM scripts also has a step-by-step installation page in the docs.
Every script for ESX and QBCore, in one place.
Browse scripts