Migrate txAdmin v7 host settings to v8
Replace deprecated txAdmin host ConVars with TXHOST environment variables, preserve txData and confirm ports after upgrading FXServer.
Since txAdmin v8, host-level settings belong in TXHOST_* environment variables, set before FXServer starts. Legacy txAdminPort, txAdminInterface and txDataPath ConVars are deprecated in v8.1.1 and removed in the upstream development branch; check version compatibility before applying changes.
Map the old settings
| Legacy | v8 host environment | Purpose |
|---|---|---|
txAdminPort | TXHOST_TXA_PORT | Panel TCP port |
txAdminInterface | TXHOST_INTERFACE | Bind interface |
txDataPath | TXHOST_DATA_PATH | Persistent txData directory |
| Legacy ZAP configuration | Relevant TXHOST_* options | Consult upstream mapping |
Important: These variables do not belong in server.cfg. That file is processed after txAdmin's own host startup.
Upgrade sequence
- Record the installed FXServer/txAdmin version, panel URL, game port, txData path and startup command.
- Take a consistent backup of
txData, server data and any external database. - Translate your current host settings using Environment & ports and the TXHOST generator.
- Update the Windows launcher, Linux service, Docker environment or hosting-provider startup variables. Use the same persistent txData path if you intend to retain accounts and moderation history.
- Remove conflicting legacy flags from your startup command after confirming the replacement settings are active.
- Start one instance and verify panel login, player actions, game startup, backups and any provider port mappings.
Linux startup example (edit for your artifact):
export TXHOST_TXA_PORT=40125
export TXHOST_DATA_PATH=/srv/fivem/txData
./run.shRoll back carefully
Changing the environment is easy; data migrations may not be reversible. Keep a full snapshot and the previously working artifact. Do not restore older binaries over newer data without checking compatibility first.
If you hit a bind conflict, follow E5800 troubleshooting. For multiple instances, assign unique panel/game ports and independent txData paths.
Sources: txAdmin v8 environment reference, environment guide.