TMC Integration
Kuzzle — TMC Integration
Connect your TMC (or compatible) FiveM server to your provisioned Kuzzle instance.
Credentials
From the welcome email or client area, collect:
| Field | Purpose |
|---|---|
| Index | Production Kuzzle index name |
| Server API key | Backend authentication |
| Player profile name | In-game user profile |
Example TMC config
Add to your server configuration (exact file depends on your TMC build):
Config.Server.Kuzzle = {
Host = "kuzzle.nexus-cloud.uk",
Port = 443,
Ssl = true,
Index = "your_index_name",
SecretKey = "your_server_api_key",
PlayerProfileName = "your_player_profile"
}
Replace placeholders with values from your welcome email. Do not commit API keys to public Git.
Dev index
For a staging server, point Index at your dev index ({prod-index}-dev) and use credentials scoped to dev if your setup provides separate keys. See Dev vs Prod Indexes.
Verify connection
- Start the FiveM server with the config in place
- Watch server console for Kuzzle connection errors
- Test an in-game feature that reads/writes Kuzzle data
Mappings
Your index is created with essential TMC mappings from the Nexus template set. MDT collections are created automatically by the FiveM MDT resource — they are not pre-seeded by WHMCS. Other custom collections may require support — open a ticket before altering production schema.
If you see HTTP 400 errors creating mdt_* collections, an older incompatible mapping may already exist. Ask support to delete those collections so the resource can recreate them.
Hjälpte svaret dig?
0 användare blev hjälpta av detta svar (0 Antal röster)

