Enable txAdmin on a FiveM Server

txAdmin is the administration panel shipped with FXServer: start and stop the server, edit server.cfg, manage players, issue bans, schedule restarts and run backups, all from a browser. This guide covers the full setup, from first start to automated tasks.

⚙️ Requirements

• A Lordhosting FiveM server, reachable from the panel
• Console access to the server, to read the signup link
• A Keymaster key if you are building the server from scratch - see getting your Keymaster key
• An extra allocation created in the panel's Network tab and dedicated to txAdmin, with its port set in the Startup tab

⚙️ 1. Create the txAdmin allocation in the panel

On a Pterodactyl panel, the txAdmin interface does not open on an already-available port: you have to assign it one.

1. Go to the Lordhosting panel.
2. In your server, open the Network tab.
3. Click Create Allocation to generate an extra port: this is the one txAdmin will use, alongside game port 30120.
4. Open the Startup tab and set that port in the variable dedicated to txAdmin.
5. Restart the server so the value is picked up.

👉 If you want a custom dedicated port, contact Lordhosting support directly.

⚙️ 2. Start the server with no configuration

txAdmin is part of the artifact: it launches as soon as FXServer starts without a valid server.cfg. In the panel, start the server and open the console. It prints a one-time signup link:

[txAdmin] Please open the following URL in your browser:
http://203.0.113.42:40120/addMaster/pin?pin=1234

⚙️ 3. Create the administrator account

Open the link in a browser, then create the master account: username, strong password, and optionally a link to a Cfx.re account for two-factor authentication.

That account holds every permission, including stopping the server and file access. Create separate accounts for your staff afterwards, with restricted permissions.

⚙️ 4. Deploy or link the server

Two paths, depending on your situation.

Existing server. Pick Existing server data and give the data path plus the server.cfg file. txAdmin takes over the current configuration without overwriting anything.

New server. Pick a recipe: ESX, QBCore or empty. txAdmin downloads the resources, creates the database and writes a starting server.cfg. Fill in the MySQL connection string then - see connecting MySQL with oxmysql.

⚙️ 5. Enter the license key

Under Settings → FXServer, paste your Keymaster key (cfx_live_...). It can also stay in server.cfg:

sv_licenseKey "cfx_live_your_key"
sv_hostname "My RP Server"
sv_maxclients 48

Without a valid key the server starts but never shows in the public list.

⚙️ 6. Schedule restarts (optional, but recommended)

Under Settings → Restarter, set the automatic restart times. On a busy RP server, two to four restarts a day keep script memory drift under control.

06:00, 14:00, 22:00

txAdmin warns players several minutes ahead; message and delay are configurable on the same page.

⚙️ 7. Turn on backups and monitoring (optional, but recommended)

The Diagnostics tab shows CPU load, memory and per-resource tick time: that is where you spot the script dragging performance down.

Also configure the watchdog under Settings → Monitor: it restarts the server when the process stops responding, with no action from you.

⚙️ 8. Fix the common errors

• The interface will not open: on the panel, check that the txAdmin allocation exists in the Network tab and that its port is set in the Startup tab. On a self-managed VPS, it is the firewall you need to open.
• invalid license key: expired key, or one bound to another IP. Regenerate it in Keymaster.
• The server starts then stops: an error in server.cfg. txAdmin's Console tab shows the offending line.
• Master password lost: run txAdmin-resetAdmin in the server console.

⚙️ Ready-to-paste configuration

The baseline server.cfg, the one txAdmin then drives from its interface - paste it and replace the key and the name:

# ---- Server identity -----------------------------------------------------
sv_licenseKey "cfx_live_YOUR_KEY"
sv_hostname "🌍 MyServer RP | Whitelist | EN"
sv_maxclients 48
sets locale "en-GB"
sets tags "roleplay, whitelist, esx, en"

# ---- Networking ----------------------------------------------------------
endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"
set sv_forceIndirectListing true
sv_endpointPrivacy false
set steam_webApiKey ""

# ---- Database ------------------------------------------------------------
set mysql_connection_string "server=127.0.0.1;database=fivem;userid=fivem;password=MY_PASSWORD;charset=utf8mb4"

# ---- Resources -----------------------------------------------------------
ensure oxmysql
ensure es_extended
# ensure your-resources

# ---- Administration ------------------------------------------------------
add_ace group.admin command allow
add_principal identifier.fivem:YOUR_ID group.admin

Scheduled restarts are set under Settings → Restarter. Three patterns that work:

Avoid the 7 pm - 11 pm window: that is the attendance peak, and a restart there empties the server for the evening.

The emergency command cheatsheet, in the server console:

txAdmin-resetAdmin        # master password lost
txaRestart                # immediate restart
txaStop                   # clean shutdown
refresh                   # reload the resource list

✅ Conclusion

txAdmin drives your server: startup, configuration, players, restarts and monitoring from a single interface. Round it out with the server.cfg guide and listing your server in the public list.

Our FiveM servers ship with txAdmin from install: all that is left is to create its allocation in the Network tab and set the port in the Startup tab.