Downloading the FiveM server artifacts and double-clicking FXServer.exe is the easy part. The moment that has to actually work is what happens next: linking your account, generating a license key, picking a starting recipe, and ending up with a server.cfg that boots cleanly instead of erroring out on the first restart. txAdmin is the tool that ties all of that together, and it ships with every FXServer build, so there is nothing extra to install.

Short answer: txAdmin is the web-based management panel bundled with every FXServer build. You set it up by downloading the FiveM server artifacts, running FXServer.exe to open its setup wizard, linking your Cfx.re account, and using the Recipe Deployer with a license key from Keymaster to generate a working server.cfg (and database, for framework recipes) in a few minutes. From there, the Resources tab handles starting, stopping, and monitoring every script without touching the console directly.

What txAdmin actually is

A management panel, not a separate program

txAdmin is a full-featured web panel that ships pre-installed with FXServer, built to manage and monitor a FiveM server from a browser instead of a raw console window. It has been available since FXServer build 2524, and to let it take over configuration you launch FXServer in monitor mode without any +exec startup arguments, letting txAdmin build and run the config for you.

What it does beyond initial setup

Once a server is live, txAdmin keeps managing it. The panel covers:

  • A recipe-based deployer for the initial build, plus the ability to start, stop, and restart the whole server or any single resource.
  • An in-game admin menu with teleport, vehicle spawning, healing, spectating, and freezing.
  • A warning and ban system with temporary or permanent bans, logged and searchable from the panel.
  • Live CPU and RAM tracking, a console with command history, and a performance chart of threads and player counts.
  • Automatic restarts if FXServer crashes or hangs, plus scheduled restarts with custom in-game announcements.
  • Role-based logins by password or Cfx.re account, a permission structure, and action logging with brute-force protection.
  • Discord integration for status embeds and player management commands.

One distinction trips people up: txAdmin keeps its own self-contained admin and player database and does not need MySQL for that. That is separate from your framework's game database. If you run ESX, QBCore, or Qbox, that framework still needs its own MySQL server regardless of what txAdmin uses internally.

Before you start: what you actually need

  • A legitimate copy of the FiveM server artifacts for your operating system (Windows or Linux).
  • A Cfx.re forum account, used to link and authorize the panel on first run.
  • A free license key, generated at keymaster.fivem.net.
  • A machine that meets the minimum specs for the player count you are planning, plus somewhere to extract the server files, for example C:\FXServer\server on Windows.

The full download and prerequisite walkthrough is in the official txAdmin setup guide, which also links the current artifact build listing so you are always grabbing a supported version rather than an old cached copy.

The official setup overview also lists game server hosting providers as a valid starting path alongside self-hosted Windows and Linux installs. If you already pay for managed FiveM hosting, your provider almost certainly runs txAdmin for you already; the steps below still apply once you have panel access, since the wizard, recipe deployer, and server.cfg output are the same regardless of who owns the physical machine.

First-run setup: linking your account

Extract the artifacts archive, then run FXServer.exe. Your browser opens automatically to the setup interface. From there:

  1. Confirm the PIN shown in the console matches the one in your browser, then click Link Account.
  2. Log into your Cfx.re account in the tab that opens, then click Yes, Allow to authorize the panel.
  3. Create an administrator password for the txAdmin panel itself.

That password is separate from your Cfx.re login and from any in-game admin permissions you set up later, so store it somewhere you will not lose it.

Deploying your server with a recipe

Once you are past account linking, txAdmin walks you through a setup wizard:

  1. Enter a server name and continue.
  2. Under Popular Recipes (sometimes labeled Popular Templates), pick a starting point. CFX Default FiveM needs no database at all. Framework recipes like QBCore or ESX prompt for MySQL credentials during deploy because they need a working database.
  3. Choose a folder for your server data, or accept the suggested default.
  4. In the Recipe Deployer, review the recipe and click Next.
  5. Paste in the license key you generated at Keymaster and click Run Recipe. txAdmin downloads dependencies, runs any SQL imports the recipe needs, and builds server.cfg automatically.
  6. Click Save & Run Server to finish.

server.cfg basics txAdmin builds for you

A fully manual, vanilla FXServer setup requires writing every one of these lines yourself, by hand, from the official server.cfg reference. Recipe deploy writes the same file automatically, so you do not have to type it from scratch, but you will still end up editing it once your server is live, so it helps to know what is actually in there and why:

  • sv_licenseKey "yourKeyHere", required. Without a valid key here the server will not start at all.
  • endpoint_add_tcp "0.0.0.0:30120" and endpoint_add_udp "0.0.0.0:30120", the address and port players connect to.
  • sv_maxclients 48, the default player cap. Going higher requires a Cfx.re Element Club Argentum subscription or higher, plus an updated server artifact.
  • sv_hostname, the name shown in the public server browser.
  • ensure lines for the default resources: mapmanager, chat, spawnmanager, sessionmanager, basic-gamemode, hardcap, and rconlog. These start automatically once the config runs.
  • add_ace and add_principal, used to grant command permissions to admin groups, for example add_ace group.admin command.someCommand allow.

A few resource commands are worth knowing precisely, since the official server commands reference defines them narrowly: ensure restarts a resource if it was already running, or starts it if it was not. start only starts a stopped resource. restart only restarts one that is already running. refresh rescans the resources folder and loads new manifests without touching resources that are already running.

Managing resources from the panel once you are live

The Resources tab is where day-to-day work happens after launch. You can start, stop, or restart any individual resource from the browser, which matters when you are testing a new script and do not want to bounce the entire server for everyone connected. The same tab shows which resources are currently running, so a script that silently failed to start is visible immediately instead of discovered when a player reports a missing feature.

The Players tab and in-game admin menu handle moderation day to day: teleporting to a reported player, spectating a conflict in progress, or issuing a temporary or permanent ban that logs to the panel instead of living only in a Discord message someone will forget. The performance chart tracks threads and player counts over time, which is usually the fastest way to notice a resource that is quietly consuming more CPU each week rather than at a fixed rate. Scheduled restarts with custom in-game announcements keep long-running servers from degrading silently between reboots, instead of relying on someone remembering to restart manually.

txAdmin turns "edit server.cfg and hope" into a panel you can actually observe. What crashes a server in its first week is rarely txAdmin itself. It is almost always an untested resource added after launch, with no monitoring in place to catch it.

Common txAdmin issues and how to fix them

  • Server not appearing in the server list, or showing as private. Confirm the #sv_master1 "" line in server.cfg still has its # in front; removing that character is what makes a server show as private. Then verify http://ip:port/info.json returns a JSON object in a browser, and check the port with a tool like canyouseeme.org (default port 30120). It can take up to 8 minutes for a server to appear in the list after launch if no heartbeat has been sent yet.
  • Player count capped at 48. This is the default limit. Raising it requires a Cfx.re Element Club Argentum subscription or higher, plus an updated server artifact and a matching change to sv_maxclients.
  • Slow first startup on Windows. Microsoft Defender scanning the FXServer files in real time is the usual cause. Excluding the server folder from antivirus scanning resolves it.
  • Recipe deploy fails at the database step. This only happens with framework recipes like QBCore or ESX, which prompt for MySQL credentials during deploy. If no database service is installed and running yet, the deploy has nothing to connect to. Set up MySQL first if you are deploying a framework recipe rather than the default CFX template.
  • Server will not start at all after a config edit. Check sv_licenseKey first. A missing, blank, or malformed license key is the single most common reason a server refuses to boot.
  • Server is reachable locally but never appears for outside players. A NAT or gateway setup that masks the UDP source port can prevent the server from being externally visible even when local testing looks fine. This is a router or network configuration issue rather than anything inside server.cfg, so it needs to be fixed at the router or, in more advanced setups, in your firewall rules.

Where self-serve setup stops being enough

txAdmin gets a server booted and reachable, but a recipe deploy does not test whether your chosen scripts are actually compatible with each other, or whether your server.cfg is tuned for the player count you are targeting rather than left at defaults. That gap between "it started" and "it is stable with real players connected" is where most first launches actually stall.

If you want a second set of eyes on your configuration before launch, a Server X-Ray reviews your existing setup, and a scoped custom build engagement covers configuration, script compatibility, and testing beyond what a recipe deploy checks on its own.

The bottom line on setting up txAdmin

Getting txAdmin running is genuinely a few clicks: link your account, run a recipe, paste in a license key. Where new server owners lose time is afterward, tuning server.cfg for real traffic, reading the Resources tab correctly when something misbehaves, and knowing which of the common errors above actually applies before troubleshooting blind. Get the first-run setup right and the panel does most of the ongoing maintenance work for you.