⚠️ Common Issues

Throughout this documentation, we'll refer to keep-harmony as simply Harmony.

You lack the required entitlement

Error Message

You lack the required entitlement to use keep-harmony

Reason

All scripts using the FiveM escrow system are linked to your FiveM account.

To function correctly, these scripts must run on a server using a server key generated by the same FiveM account used on Tebex.

What is a server key?

A server key is generated in the FiveM keymaster and is not the same as a script key. A FiveM server can use only one server key.

Example of a server key in server.cfg

sv_licenseKey "cfxk_xxxxxxxxxxxxxxxxxxxxx_xxxxxx"

How to verify your server key

To check the server key your server is currently using, use the following command in your FiveM server console:

sv_licenseKey

Steps to Verify if You are Using the Correct Server Key

1. Check the Current Server Key:

   • Use the command sv_licenseKey in your FiveM server console.

2. Verify Ownership in FiveM Keymaster:

   • Go to FiveM keymaster.
   • Log in with the account that owns the scripts you are trying to use.
   • Verify if the scripts are listed under "Purchased assets".

3. Match the Server Key:

   • Ensure the server key your server is using is generated by the same account that owns the scripts.

Loading Issue

Encountering the "Loading Issue" might lead to an error message appearing when starting Harmony.

This issue can manifest in two main types:

Resource Stopping or Stopped

This occurs when a resource that Harmony depends on is either stopped or stopping. For example, if Harmony relies on qb-target but it hasn't started before Harmony, you'll need to adjust the order of resource loading in your server.cfg file.

Ensure that the dependency resource (qb-target in this case) is started before Harmony.

ensure qb-core
ensure ox_lib
ensure [standalone]
ensure [qb]
...
ensure qb-inventory
ensure qb-target <--- Start it before Harmony
ensure keep-harmony
...

Missing Resource

This occurs when the specified resource is either misspelled or truly missing. There could be several scenarios leading to this:

• Misspelled Resource Name: If the resource name is incorrect (e.g., ox-target instead of ox_target), the script won't find it, resulting in a missing resource error.

• Truly Missing Resource: If the resource is genuinely missing, you'll need to take appropriate action. For instance:

  • Replace the missing resource with the correct one. For example, if you're using ox-target but qb-target is missing, you might need to configure the script to use ox_target instead.