Common Errors
Here you will find common errors and solutions to resolve them!
Last updated
Here you will find common errors and solutions to resolve them!
Last updated
This error may appear in the client console or server console. To fix this, please make sure that you are using a server licence key from the same account the resources were purchased through.
All resources run using the FiveM Tebex Escrow System. This means that assets hold a licence to a resource on a Keymaster account, which be transferred once per resource. Only servers using a licence key from that Keymaster account will be able to run the resource successfully.
To resolve this error, we recommend checking your server licence key is the one from the account where you downloaded the resource. You will also need to restart the server after installing it.
We also recommend making sure that your server artifacts are up to date.
This error may appear in the client console. To fix this, we recommend you firstly checking the contents of the resource folder that you have installed on your server. Please make sure there is a .fxap file as seen in the photo below:
Some file transfer softwares either corrupt this file, or do not transfer it over properly. We recommend using WinSCP to install your resource, if your server is on a remote computer. You can download WinSCP here.
If you are using FileZilla, make sure to set your transfer mode to binary, as seen below:
This error may appear in the server console. If you do not use ESX on your server, simply head to the fxmanifest.lua of the resource producing the error and comment out or remove the ESX line as follows:
Once this has been removed from the fxmanifest.lua file, your error will no longer appear.