FiveM 'Failed to verify protected resource' Fix

The error

Failed to verify protected resource my_resource

This appears in the server console when a resource protected by Cfx.re asset escrow (most paid scripts from Tebex stores) will not start. The server checks the resource against the Cfx.re account that owns your sv_licenseKey. If that check fails, the resource refuses to load, and you often see a parse error on the first line of an encrypted .lua file straight after. The script itself is usually fine. Work through these causes in order.

1. The asset is on a different Cfx.re account

The purchase has to be granted to the same Cfx.re account that generated the license key in your server.cfg. A common case: the server owner made the key, but someone else bought the script on their own account. Log in to the Cfx.re Portal with the account that owns the key and check the script is listed under your granted assets. If it is on another account, transfer it or generate the key from the account that owns the script.

2. The .fxap file is missing or was corrupted in upload

Every escrowed resource has a hidden .fxap file in its folder, and that is what gets verified. Some FTP clients skip hidden files, and a transfer in text (ASCII) mode quietly corrupts binary files. The file can still be there and still the wrong bytes. Download the resource again, upload the .zip to the server and extract it there, or force binary mode in your FTP client.

3. An encrypted file was edited

Opening an encrypted server file and saving it, even with no visible change, breaks verification. Editors that change line endings do this silently. Only edit files that open as readable Lua (usually config.lua). If you touched anything else, replace the resource with a fresh download and copy your config values back in.

4. The server was not fully restarted

Verification runs when the server boots. refresh and restart my_resource are not enough after a new purchase, an account transfer or a license key change. Stop the server process completely and start it again.

5. Old server artifacts

Escrow needs a reasonably recent server build. If the same resource works on a local test server but not on your host, compare the artifact versions and update the host.

Check the upload

# Linux host: .fxap is hidden, so use -a
ls -la resources/[paid]/my_resource/

# compare with a fresh download on your PC; the hashes must match
sha1sum resources/[paid]/my_resource/.fxap

# Windows host (Command Prompt)
dir /a resources\[paid]\my_resource
certutil -hashfile resources\[paid]\my_resource\.fxap SHA1

If the hashes differ, the upload changed the file: re-upload as a zip and extract on the server. If they match and the error remains, check the account (cause 1) and do a full restart (cause 4).

Real reports of this error: Cfx forum: Failed to verify protected resource (corrupted files) and Cfx forum: error with purchased script (works locally, fails on the host).

FiveM 'Failed to verify protected resource' – Fix