Saltar al contenido
Updating txAdmin and FXServer

Updating txAdmin and FXServer

txAdmin ships inside FXServer, so updating the artifact updates txAdmin. How to update, what to back up, migrating old start.bat configs to TXHOST variables, and rollbacks.

Esta documentación está en inglés por ahora.

Last updated

Since early 2020 txAdmin is a component of FXServer. There is no separate txAdmin download and no separate update button: each FXServer artifact contains a specific txAdmin version. Update the artifact and you update txAdmin.

How to tell which version you run

  • The txAdmin panel shows its version in the sidebar or footer, and the FXServer build number on the dashboard.
  • The console prints both on start.

When a new txAdmin version is out, it arrives in a new artifact. The recommended artifact may lag behind the latest one by a few builds.

The update, step by step

The artifact update routine is the same one described in Updating artifacts safely. Short version:

  1. Check the build on our Artifacts page, avoid builds flagged as broken.
  2. Back up txData (it holds admins.json, player database, bans, warns and settings) and your database.
  3. Stop the server and close FXServer.
  4. Rename the old artifact folder, extract the new one to a fresh folder.
  5. On Linux, make sure txData is where txAdmin expects it (by default next to run.sh, which is inside the artifact folder), or set TXHOST_DATA_PATH.
  6. Start FXServer. txAdmin migrates its own config and database automatically on first start.
  7. Check the dashboard, live console and in-game menu.

Warning

Going back to an older artifact after txAdmin migrated its data can fail, because the old version may not read the new format. That’s why you back up txData before updating, not after.

Migrating old start scripts (txAdmin v8)

Older guides start txAdmin with convars on the command line:

start.bat (old style)
@echo off
"C:/FXServer/server/FXServer.exe" +set serverProfile "server2" +set txAdminPort "40125"
pause

Since txAdmin v8.0.0, host settings are TXHOST_* environment variables. The txAdminPort, txAdminInterface and txDataPath convars (and the txAdminZapConfig.json file) are deprecated and will stop working in a future update. The txAdmin docs give this replacement:

start.bat (current)
@echo off
set TXHOST_DATA_PATH=C:\FXServer\txData-server2
set TXHOST_TXA_PORT=40125
"C:/FXServer/server/FXServer.exe"
pause

On Linux, add export TXHOST_...=... lines to a small env.sh and start with source env.sh && ./run.sh, or use Environment= lines in your systemd unit.

If both old and new configs exist, the new one wins. TXHOST_IGNORE_DEPRECATED_CONFIGS=true silences the warnings. The concept of profiles (serverProfile) will likely be deprecated too, so use one txData per server instead.

What usually changes after an update

  • New settings with default values (check the Settings pages after big updates).
  • The in-game menu may look different or have new permissions: review your admins’ permissions in the Admin Manager.
  • Discord bot: new permissions or intents are occasionally needed. Check System Logs if the bot stops working.
  • Deprecated features disappear. The feature graveyard lists what was removed and why (for example built in SSL: use a reverse proxy or Cloudflare Tunnel instead).

Keeping up with changes

  • The txAdmin GitHub releases and the txAdmin Discord announce new versions.
  • The official txAdmin YouTube channel has short videos for some features.
  • Cfx.re’s forum announces artifact changes that affect server owners.

FiveM for GTA V Enhanced

Enhanced uses a different server build (Cfx Server) with its own downloads, and txAdmin has a separate “FiveM Basic Server (Enhanced)” recipe. Don’t point an Enhanced artifact at your Legacy txData and server folder and expect it to work: read the Legacy and Enhanced notes and test on a copy.