Keymaster License Errors

Over 90% of startup failures on new resource installations are related to Cfx.re Keymaster license key mismatches, outdated server artifacts, or renamed resource folders. Follow this guide to resolve license verification errors immediately.

---

1. You are not authorized to use this resource

Cause: The FiveM server license key (sv_licenseKey in server.cfg) was generated on a different Cfx.re Keymaster account than the one used to purchase the asset on Tebex.

Resolution:

1. Identify the Purchasing Account: Log in to Keymaster and verify that the resource appears under Granted Assets.
2. Check Your Active Server License Key:
   • In Keymaster, click on Server Keys (or Register a new key).
   • Generate a new server key under the same Keymaster account that owns the granted asset.
3. Update server.cfg:

   sv_licenseKey "cfxk_your_correct_license_key_here"

4. Restart FXServer: Restart your server and verify the startup logs.

Alternatively, if your server uses a license key owned by another developer or host, transfer the asset to that account via the transfer icon in Keymaster Granted Assets.

---

2. Failed to verify asset token or Authentication timed out

Cause: FXServer was unable to establish an outbound SSL/TLS connection with Cfx.re Keymaster authentication servers (keymaster.fivem.net / lambda.fivem.net) during resource initialization.

Resolution:

• Test Server Outbound Connectivity: Ensure your server host allows outbound HTTPS requests on port 443 and port 30120.
• Verify Cfx.re System Status: Check status.cfx.re to ensure Keymaster authentication endpoints are fully operational.
• Clear Server Cache:
  1. Stop your FXServer.
  2. Navigate to your server root directory and delete the cache/ folder (specifically cache/files/ and cache/kvs/).
  3. Start FXServer.

---

3. Could not load citizen-resources-core.dll or Script Crashes on Boot

Cause: Your FXServer artifact build is outdated. Asset Escrow encryption requires FXServer Build 5848 or higher (Recommended: Build 7290+).

Resolution:

1. Visit the official FiveM Artifacts page:
   • Windows Server Artifacts: runtime.fivem.net/artifacts/fivem/build_server_windows/master/
   • Linux Server Artifacts: runtime.fivem.net/artifacts/fivem/build_proot_linux/master/
2. Download the latest Recommended or Latest build.
3. Extract the artifact files into your FXServer core directory.
4. Restart your server.

---

4. Corrupted or renamed resource folder

Folder Integrity Verification

Escrowed scripts check their folder name against the internal cryptographic signature generated by Keymaster. If you rename the resource folder, the asset will refuse to start.

Ensure the folder on your server matches the exact official naming format (e.g. mtm-matrixborden, mtm-flessenautomaat, mtm-taxi, etc.).

---

5. Recent Purchase Delays (Keymaster Sync Delay)

When purchasing a resource on Tebex, it typically takes 1 to 5 minutes for Cfx.re to synchronize the asset grant across all global CDN edge nodes:

1. Wait 5 minutes after checkout.
2. Verify the asset appears in keymaster.fivem.net.
3. Restart your FiveM server to trigger a fresh license validation token.