Common issues

Common problems that often appear in Fivem scripts, both in ESX and QB

ERROR: You lack the require entitlement

Try restarting your server and make sure your server license key is correct. If you bought the resource on the wrong account, you can transfer it to another account on keymaster.

ERROR: Failed to verify protected resource

· Your server artifacts are likely outdated. · Files were possibly corrupted during transfer. Ensure hidden files are copied; the .fxap file in a protected resource must be included. Some FTP programs skip these files. · FileZilla can have problems with encrypted files, tried using

ERROR: Error parsing script / Failed to load script

·Your server artifacts are likely outdated.

ERROR: Attempt to index a nil value (field 'MySQL')

If you use mysql check that in the fxmanifest.lua file in the server_scripts part the following line appears, if not add it and restart the script

server_scripts {
    "@mysql-async/lib/MySQL.lua",

The script starts but does nothing and no error is displayed

This usually happens in scripts like bit-garage, bit-pets, etc.. in which if you don't have enough money for example, you get a notification. But if it is not configured, this notification does not appear and it seems as if the script does not work.

Check if in the config.lua of the script there is the option of notifications. If so, configure it according to the script you normally use to send notifications. Restart the script and check if you get any notifications.

No permissions or commands do not work

This usually happens in QB-Core servers, and it is due to the fact that you do not have the administrator permissions properly configured. To fix it add the following line in the server.cfg of your server:

add_principal identifier.license:03f315c25a9d8..... qbcore.god

Change the license number to your account number. You can find this license from txadmin or from the database. For ESX you can add this:

add_ace group.superadmin "command" allow
add_principal identifier.license:03f315c25a9d8..... group.superadmin

[ESX] Used the getSharedObject event, this event no longer exists!

This is because ESX, since version 1.9, no longer uses the getSharedObject event. To fix this problem, in the config.lua of the script you will see the following option:

--If you are using one of the most recent versions of ESX, set the script name. Default = "es_extended"
Config.ESXExport = ""

Modify it as follows and restart the script:

Config.ESXExport = "es_extended"