What txAdmin actually is
txAdmin is the official web based management panel for FiveM and RedM servers. It is not a separate download. It is bundled inside every FXServer build, which means the moment you have the server artifacts, you already have txAdmin. Its job is to start and stop your server, watch the console, manage resources, schedule restarts, handle bans and warnings, and write your server.cfg for you.
Understanding that one fact saves a lot of confusion. People search for how to install txAdmin as if it were a standalone program. The real task is installing FXServer, then letting txAdmin run on first launch.
How the pieces fit together
There are three layers. FXServer is the engine that runs the actual game server process. txAdmin is the supervisor that launches and monitors FXServer through a web interface. Your server data (resources, the database, and server.cfg) lives in a folder txAdmin calls the txData directory. txAdmin reads and writes that folder but keeps itself separate from it, which is why you can wipe and rebuild a server without touching the panel.
Step 1: Download the FXServer artifacts
Artifacts are the compiled FiveM server builds. They are versioned by number and published on the official runtime servers.
- Windows: download the latest recommended build from the FiveM artifacts page (
runtime.fivem.net/artifacts/fivem/build_server_windows/master/). The file is a.7zarchive containingFXServer.exeand supporting files. - Linux: use the matching build under
build_proot_linux. The archive containsrun.shand thealpineruntime folder.
Pick the build marked recommended (the green or latest stable entry), not the absolute newest, and not an old pinned build. Mismatched or outdated artifacts are the single most common cause of a server that refuses to start.
Create a clean folder for the server binaries, for example C:\FXServer\server on Windows, and extract the archive into it. Keep this folder separate from where your server data will live.
Windows prerequisites
On Windows you need the Visual C++ 2019 redistributable (x64) installed. Without it FXServer fails to launch with a missing DLL error. Linux builds run inside a self contained proot environment, so you mainly need a 64 bit distribution and glibc compatible kernel.
Step 2: Run FXServer for the first time
Make a second folder for your data, for example C:\FXServer\txData. Then start the server.
On Windows, run FXServer.exe directly. On Linux, run ./run.sh. Because no server.cfg exists yet, FXServer hands control to txAdmin instead of trying to boot a game server.
The console prints a line telling you txAdmin is starting and that the interface is available at an address. By default that is:
http://localhost:40120
Port 40120 is the txAdmin web panel. It is not the game port. Keep both in mind because they are different things that often get confused.
Step 3: The setup PIN and master account
Open http://localhost:40120 in a browser on the same machine. On first run txAdmin asks for a setup PIN. This is a one time, randomly generated code printed in the FXServer console window, something like 1234. It exists so that only the person with console access can claim the panel.
Copy the PIN from the console, paste it into the browser, and you move on to creating the master account. This is the top level administrator. You can register a local username and password, or link a Cfx.re (FiveM forum) account. The master account can create more admins later with scoped permissions, so use a strong password and treat it like a root login.
If you are setting up on a remote VPS and the browser is on your own PC, you will not reach localhost. Use the server's public IP with port 40120, for example http://203.0.113.10:40120, and make sure that port is open in the firewall first.
Step 4: Choose how to create the server
After the master account, txAdmin offers a deployment choice. This is where most setup guides skip the important detail.
Option A: Deploy a recipe (template)
A recipe is a YAML file that automates building a full server. txAdmin can pull a recipe that downloads a framework (such as a CFX default, ESX, or QBCore base), fetches resources from Git, runs SQL against your database, and writes a ready server.cfg. This is the fastest path to a playable server because the template does the wiring for you.
You point txAdmin at the empty txData folder, pick a recipe, and it provisions everything into a new sub folder. For frameworks that need a database you must supply MySQL connection details during deployment, so have MySQL or MariaDB installed and a database created beforehand.
Option B: Use an existing or empty folder
If you already have a server data folder (you built one manually or copied it from elsewhere), choose the local folder option and point txAdmin at it. txAdmin will use the existing server.cfg rather than generating a new one. Choose the blank option if you want to start from nothing and add resources by hand.
Step 5: server.cfg and the cfx.re license key
Whichever path you take, txAdmin produces or adopts a server.cfg file. This file defines the game port, server name, resources to start, and your license key.
Every FiveM server needs a cfx.re license key, generated for free at keymaster.fivem.net. It goes into server.cfg as:
sv_licenseKey changeme
The default game connection port is 30120 (UDP and TCP), set with endpoint_add_tcp and endpoint_add_udp lines in the config. This is the port players connect to, separate from the 40120 panel. txAdmin manages the config through its built in editor, so you rarely edit the file by hand after setup, but it helps to know where the values come from.
Once the config exists, hit Start Server in the txAdmin panel. txAdmin launches FXServer, streams the live console into the web UI, and your server appears in the server list if the license key and ports are correct.
Step 6: Open the right ports
A server that starts locally but is unreachable by friends almost always has a firewall or router problem.
- 30120 TCP and UDP must be open and, on a home connection, port forwarded to the machine. This is the game port.
- 40120 TCP only needs to be reachable from wherever you administer the panel. Many people keep it firewalled to their own IP for security.
On a VPS, open these in the provider firewall and the OS firewall (ufw on Linux, Windows Defender Firewall inbound rules on Windows).
Keeping it running
txAdmin includes a scheduled restart and a watchdog that auto restarts a crashed server, both configured in the panel under settings. For production, run FXServer as a service or inside a process manager (a Windows service, systemd unit, or pm2) so the whole stack survives a reboot. txAdmin itself comes back up with FXServer because it is the same process.
That is the full loop: artifacts give you FXServer, FXServer launches txAdmin on 40120, the PIN and master account secure the panel, a recipe or folder choice builds the server, and server.cfg plus the license key and port 30120 make it playable.