HZ Scripts
server setup

txAdmin Setup Guide 2026: Install, Configure, and Manage Your FiveM Server

HitzyMay 26, 202611 min read
txadminfivemfivem serverserver managementserver setup

txAdmin Setup Guide 2026: Install, Configure, and Manage Your FiveM Server

If you're setting up a FiveM server, you're going to spend a lot of time inside txAdmin. It's the web-based management panel that handles everything from starting your server to banning toxic players. Knowing it well will save you hours of debugging.

This guide covers everything from your first txAdmin launch to advanced configuration — automatic restarts, backups, resource management, and admin permissions.

If you haven't set up a FiveM server yet, start with our Complete Beginner Guide to Creating a FiveM Server.


Table of contents

  1. What is txAdmin?
  2. Installing txAdmin (Windows & Linux)
  3. First-time setup wizard
  4. Understanding the txAdmin dashboard
  5. Configuring server.cfg through txAdmin
  6. Managing resources
  7. Player administration
  8. Automatic restarts and backups
  9. Admin permissions and roles
  10. Troubleshooting common issues
  11. FAQ

What is txAdmin?

txAdmin is the official server management panel for FiveM. It's developed by the CFX.re team and ships bundled with every FiveM server build.

It provides a web-based interface (accessible at http://YOUR_IP:40120) that lets you:

  • Start, stop, and restart your server with one click
  • Access the live server console from your browser
  • Edit server.cfg with syntax highlighting
  • Browse, start, and stop individual resources
  • Ban, kick, and warn players
  • Set up scheduled restarts and automatic backups
  • Manage multiple admin accounts with role-based permissions
  • View server metrics (CPU, RAM, player count) in real-time
Without txAdmin, you'd manage your server via raw console commands — possible, but painful. txAdmin is the standard.

Installing txAdmin

txAdmin comes pre-bundled with the FiveM server. You don't install txAdmin separately — you download the FiveM server build, and txAdmin launches automatically.

Windows installation

  1. Install Git and 7-Zip if you don't have them already.
  2. Go to the official FiveM artifacts page: runtime.fivem.net/artifacts/fivem/build_server_windows/master/
  3. Download the latest "recommended" build (look for the green tag) — it's a .7z archive.
  4. Extract server.7z to a folder (e.g., C:\FXServer\server).
  5. Run FXServer.exe — txAdmin will auto-launch and open your browser.
  6. Enter the PIN displayed in the console, click Link Account, and authenticate with your CFX.re account.

Linux installation

For production, Linux is recommended (better performance, easier to keep updated, lower memory overhead).

# Prerequisites
sudo apt install git xz-utils

Create a dedicated user

sudo adduser fivem sudo su - fivem

Download FXServer

mkdir -p ~/FXServer/server cd ~/FXServer/server

Replace LATEST_LINK with the actual URL from the artifacts page

wget https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/LATEST_LINK tar xf fx.tar.xz --strip-components=1 rm fx.tar.xz

Start FXServer

bash run.sh +exec server.cfg

Replace LATEST_LINK with the actual download URL from the Linux artifacts page. Pick the latest recommended build.

After starting, you'll see the same txAdmin URL. Open it in your browser.

A note on running txAdmin behind a reverse proxy

If you want a clean URL like panel.yourserver.com instead of your-ip:40120, set up Nginx or Caddy as a reverse proxy. This also lets you enable HTTPS via Let's Encrypt. Recommended for any public-facing server.


First-time setup wizard

On first launch, txAdmin walks you through a 4-step wizard.

Step 1 — Create your master admin account

You'll create the primary admin account for txAdmin. This account has full permissions over the panel. Pick a strong password — anyone with this login controls your entire server.

You can also link via your Discord or CFX.re account for OAuth login. Recommended for security (no password to leak).

txAdmin will ask you to authorize it with your CFX.re account. This connects your server to your CFX.re license key so it can authenticate properly.

Step 3 — Server configuration

You'll be asked for:

  • Server name (e.g., "My Awesome RP Server")
  • Server folder — where your resources/ and server.cfg will live
  • Server data path — where txAdmin stores its data (logs, backups, etc.)

Step 4 — Choose a recipe (or skip)

This is the big decision: do you want txAdmin to automatically install a base server for you, or do you want to start from scratch?

Select "Popular Recipes" to see available templates. The list varies over time, but typical options include:

  • CFX Default FiveM — minimal default setup, no database required. Best for first-time experimentation.
  • QBCore — full QBCore framework + essential scripts. Requires MariaDB.
  • ESX Legacy — full ESX framework + essential scripts. Requires MariaDB.
  • QBox — full QBox framework. Requires MariaDB.
Some community recipes (vMenu, custom templates) may also be available. Our recommendation: if you're a complete beginner just experimenting — use CFX Default FiveM (no database needed). If you're building a serious RP server — pick a QBCore or QBox recipe, or start with a blank setup and install everything manually. You'll understand your stack much better, which pays off when debugging at 2am.

After this step, txAdmin finishes setup and starts your server. You should see "Server started" in the console.


Understanding the txAdmin dashboard

Once logged in, you'll see the main txAdmin dashboard. Let's break down each section.

Header bar

The top bar shows:


  • Server status (Online/Offline with player count)

  • Server uptime

  • CPU and RAM usage

  • Quick action buttons (Start, Stop, Restart server)


  • Dashboard — overview metrics and quick actions
  • Players — connected players + database of all players
  • History — admin action history (bans, kicks, warns)
  • Whitelist — if whitelist is enabled
  • Resources — start/stop/restart individual scripts
  • Server Log — real-time console output
  • Server.cfg Editor — edit your main config file with syntax highlighting
  • txAdmin Settings — configure the panel itself

Live console

The Live Console is where you'll spend most of your debugging time. It shows real-time server output: chat messages, errors, resource warnings, player connects.

You can type server commands directly into the console — anything you'd type via SSH works here. Examples:

ensure hz-weather-pro     # start a resource
restart hz-weather-pro    # restart a resource
stop hz-weather-pro       # stop a resource
status                    # show server status
players                   # list connected players
quit                      # stop the server

Configuring server.cfg through txAdmin

Your server.cfg is the heart of your FiveM server. It controls hostname, slot count, license key, admin permissions, and which resources to start.

txAdmin's built-in editor includes syntax highlighting and a "Save & Restart" button.

Essential server.cfg settings

Here's a minimal server.cfg to get you started:

# License key from portal.cfx.re
sv_licenseKey "your-key-here"

Server identity

sv_hostname "^1My ^7Awesome ^2RP Server" sv_projectName "MyServer" sv_projectDesc "A friendly RP community" sv_maxClients 48

Endpoint settings

endpoint_add_tcp "0.0.0.0:30120" endpoint_add_udp "0.0.0.0:30120"

Server tags (for the FiveM browser)

sets tags "roleplay, qbcore, custom" sets locale "en-US"

Database connection (MariaDB — for ESX/QBCore/QBox)

set mysql_connection_string "mysql://user:password@localhost/dbname?charset=utf8mb4"

OneSync (required for server-side player awareness)

set onesync on

Resources — order matters

ensure oxmysql ensure ox_lib ensure qb-core ensure pma-voice ensure hz-weather-pro ensure hz-television

... add more resources here

Resource ordering

Resources are loaded in the order they appear in server.cfg. Dependencies must come first.

Common order:


  1. Database (oxmysql — the modern standard, replaces mysql-async)

  2. Libraries (ox_lib, PolyZone)

  3. Framework core (es_extended, qb-core, qbx_core)

  4. Framework modules (jobs, banking, inventory)

  5. Standalone scripts (HZ-Scripts, weather, TVs, audio, etc.)

  6. Last (admin tools, optional mods)


If you ensure a script before its dependency, you'll see startup errors. Reading the console carefully tells you what's missing.


Managing resources

The Resources tab in txAdmin lists every resource in your resources/ folder, with their status (started/stopped) and start time.

Start/stop/restart from the panel

Click any resource and use the buttons:

  • Start — equivalent to ensure resource_name
  • Stop — equivalent to stop resource_name
  • Restart — stop then start
Restarting an individual resource is much faster than restarting the entire server. Use this constantly during development.

Refreshing the resource list

If you drop a new resource folder into resources/ and it doesn't appear in the panel, hit "Refresh". This re-scans the folder.

Common resource errors

Most resource errors show in the console with [ERROR] or [WARN] tags:

  • Could not find dependency — a required resource isn't running. Check the resource's documentation for its requirements (often ox_lib, oxmysql).
  • Script error: attempt to index a nil value — Lua script bug. Read the line number, open the file, investigate.
  • oxmysql: no connection — your MariaDB/MySQL credentials in server.cfg are wrong or the database isn't running.

Player administration

The Players tab shows everyone connected, plus a searchable database of all players who've ever joined.

Quick actions per player

Right-click any player to:


  • Kick (with reason)

  • Warn (recorded in their history)

  • Ban (temporary or permanent)

  • DM (direct in-game message)

  • Spectate (watch their gameplay)

  • Teleport (admin tool)


Bans

txAdmin bans store the player's license, IP, hardware ID, Steam, Discord, and Xbox Live identifiers. A banned player can't return by simply changing their IP or Steam account — unless they spoof their entire hardware ID.

For maximum effectiveness, run bans through txAdmin (not via in-game chat commands) so they're persisted in txAdmin's database.


Automatic restarts and backups

Two features that every server must enable: scheduled restarts and automatic backups.

Scheduled restarts

FiveM servers slowly accumulate memory over time. A clean restart every 6-12 hours keeps performance stable.

In Settings — Restarter:


  • Enable "Scheduled Restarts"

  • Set restart times (e.g., 06:00, 18:00 server time)

  • Configure warnings: txAdmin will broadcast in-game messages 30, 15, 5 minutes before restart


Automatic backups

txAdmin can back up your server-data folder + MariaDB database on a schedule.

In Settings — Backup:


  • Enable "Auto Backup"

  • Set frequency (daily recommended)

  • Set retention (keep 7-14 days of backups)

  • Specify backup destination (local folder or S3-compatible storage)


Configure MariaDB backups separately through your hosting provider or with a custom mariadb-dump cron job. txAdmin doesn't back up the database automatically by default.


Admin permissions and roles

txAdmin uses a role-based permission system. The default roles:

  • Owner — full access to everything (the initial admin)
  • Admin — can manage players, restart resources, edit server.cfg
  • Moderator — can kick/ban players, view logs, but can't modify server config
  • Custom roles — you can define your own

Adding new admins

In Settings — Admin Management:


  1. Click "Add Admin"

  2. Enter their username/email

  3. Assign a role

  4. They'll receive an invite link to set their password


Linking admin accounts to Discord OAuth is more secure than passwords:


  • No passwords to leak

  • Easier revocation (just remove from Discord)

  • Easier audit trail (Discord usernames in logs)


Set this up in Settings — Authentication.


Troubleshooting common issues

Server won't start

Symptom: txAdmin says "Server start failed" or hangs on startup. Causes:
  • Invalid sv_licenseKey — check it on portal.cfx.re
  • Port conflict — another process is using port 30120
  • Resource crash on load — check the console for the last resource that loaded
Fix: start with a minimal server.cfg (no resources except mapmanager, chat, spawnmanager). Add resources back one by one until you find the culprit.

Can't connect to txAdmin web panel

Symptom: http://your-ip:40120 doesn't load. Causes:
  • Firewall blocking port 40120
  • txAdmin isn't running (server not started)
  • Wrong IP
Fix: SSH into your server, check netstat -tulpn | grep 40120 (Linux) to confirm txAdmin is listening. Open the port in your firewall (ufw allow 40120/tcp on Ubuntu).

Players can't connect

Symptom: Players get "Couldn't load resource" or "Connection lost" errors. Causes:
  • A resource failed to load — check console for [ERROR]
  • Server is over capacity — check sv_maxClients
  • Player's GTA V is out of date — tell them to update
Fix: read the server console when the player tries to connect. txAdmin shows you exactly which step failed.

MariaDB connection errors

Symptom: oxmysql: connection refused or Access denied. Causes:
  • Wrong connection string in server.cfg
  • MariaDB server not running
  • Wrong user permissions
Fix: test your credentials with HeidiSQL (bundled with MariaDB on Windows) or DBeaver. If they work there, the issue is your server.cfg syntax.

What's next?

Now that you know txAdmin inside out:

  1. Pick your framework wiselyESX vs QBCore vs QBox Comparison
  2. Choose your first scriptsFirst Scripts to Install on Your FiveM Server
  3. Build your script catalog — browse HZ-Scripts for premium plug-and-play resources
txAdmin is the most underrated piece of the FiveM ecosystem. Master it early — you'll thank yourself when you're debugging a 64-player server at 2am with a community Discord raid asking "is it back yet?"

FAQ

See the FAQ above each section, or browse related guides for specific topics.

Frequently Asked Questions