Environment & ports
Use TXHOST variables for panel ports, interfaces, and data paths.
Starting with txAdmin v8, host configuration uses TXHOST_* environment variables. Set them before launching FXServer. In the pinned stable v8.1.1 source, the old txAdminPort, txAdminInterface, and txDataPath ConVars are deprecated; new variables take priority when both are set. Upstream develop has removed these legacy variables; see Versions & compatibility before migrating.
Common variables
| Variable | Purpose | Default |
|---|---|---|
TXHOST_TXA_PORT | txAdmin web panel TCP port | 40120 |
TXHOST_FXS_PORT | Enforced game server endpoint port | Not forced |
TXHOST_INTERFACE | Network interface for txAdmin and enforced FXServer endpoints | 0.0.0.0 |
TXHOST_DATA_PATH | Directory containing txAdmin data | Platform-dependent |
TXHOST_TXA_URL | Public URL printed in the panel boot message | Not set |
TXHOST_GAME_NAME | Restrict offered game recipes to fivem or redm | Not set |
The panel port cannot be 30120, and the enforced game port cannot be 40120. These restrictions help keep panel and game endpoints distinct.
Windows example
Create a startup batch file beside your artifact and adjust the paths:
@echo off
set TXHOST_TXA_PORT=40125
set TXHOST_DATA_PATH=C:\FiveM\txData-main
FXServer.exe
pauseLinux example
From the artifact directory:
export TXHOST_TXA_PORT=40125
export TXHOST_DATA_PATH=/srv/fivem/txData-main
./run.shChoose a writable data directory. Do not reuse a directory that belongs to another server.
Containers and managed hosting
Set the variables in the container environment or provider startup controls. With Docker, load an environment file through --env-file; also publish the chosen panel and game ports. Pterodactyl users may need the provider to adjust the egg.
Multiple servers
Use separate txData directories and distinct panel/game ports for each server. The upstream docs discourage sharing txData profiles because admins.json can conflict. Avoid building a new deployment around the legacy serverProfile pattern.
Host status endpoint
TXHOST_API_TOKEN controls /host/status. It is disabled when unset. Use a protected token for automation; the literal value disabled makes the endpoint public. Prefer the x-txadmin-envtoken header rather than putting a token in a URL that can be logged.
See the complete environment reference for provider settings, deployment defaults, and migration examples.
Source: txAdmin upstream documentation.