Common Issues

Welcome to our common problems page! We will make sure to include every potential issue that users may encounter in our comprehensive list. Here you will discover quick fixes and helpful hints in case you run into any issues when utilizing our resources. This page has quick and easy solutions for technical issues, mistakes, and common traps.

YOU LACK THE REQUIRED ENTITLEMENT

If this problem persists, please attempt to restart your server and verify that the Keymaster account associated with the asset purchase is the correct one.

FAILED TO VERIFY PROTECTED RESOURCE

If you experience this problem, it might be because of one of the following:

• The artifacts on your server might be out of date.

• FileZilla might have trouble opening encrypted files; try utilizing another program.

• It's possible that corrupted files were transferred. Make sure to copy hidden files, particularly the.fxap file located in a protected resource. These necessary files might be skipped by some FTP software.

COULDNT START RESOURCE

Make sure you have installed all required dependencies as listed in the docs and fxmanifest.lua file if you run into this problem. Restart the server after installing the necessary dependencies.

Please feel free to open a support ticket on our Discord for additional help if the issue continues.

ATTEMPT TO INDEX A NIL VALUE (GLOBAL 'LIB')

If this problem arises, ensure that the shared_scripts section of the fxmanifest.lua file contains the line '@ox_lib/init.lua'. If the line is not present, simply add it; if it is present but followed by two hyphens, as in -- '@ox_lib/init.lua', simply remove it.

After applying the modifications, ensure the server is restarted.

shared_scripts { 
    '@ox_lib/init.lua', 
}

ATTEMPT TO INDEX A NIL VALUE (GLOBAL 'MySQL')

If this problem arises, ensure that the server_scripts section of the fxmanifest.lua file contains the line '@oxmysql/lib/MySQL.lua'. If the line is not present, simply add it; if it is present but followed by two hyphens, as in -- '@oxmysql/lib/MySQL.lua', simply remove it.

After applying the modifications, ensure the server is restarted.

server_scripts { 
    '@oxmysql/lib/MySQL.lua', 
}

USED WRONG KEYMASTER ACCOUNT TO BUY A RESOURCE

You can easily transfer a purchased resource to the correct Keymaster account if you accidentally used the incorrect account.

---

WARNING: Transfer will remove this license from your account and move it to another Cfx.re account. This action is irreversible and can be done only once for each license.

---

Use these steps for transferring any resource to a different Keymaster account:

1. Go to keymaster.

2. Then select Granted Assets.

3. Find the asset or resource that you wish to transfer.

4. There is a dropdown arrow next to the download button. Click it and choose Transfer to Another Account.

5. Enter your Keymaster account, and click Transfer Asset License.

6. Look in the email inbox of your Keymaster account for a confirmation message about the asset transfer, then select Confirm Transfer Request.