txAdmin in 2026: Setup, Scheduled Restarts, Backups and Recovery

If you run a FiveM server, you already run txAdmin whether you set it up deliberately or not. It is the official server management platform built by Cfx.re, used by tens of thousands of servers, and it is the panel that starts your server, restarts it on a schedule, monitors resource usage, and handles bans. This guide walks through a clean first-boot setup, the restart and backup settings that keep a live server stable, and what to do when access breaks.

The important thing to understand before anything else is that txAdmin is not a separate download anymore. It ships inside the server build, so most of the work is configuration, not installation.

What txAdmin actually is

txAdmin is a web dashboard and in-game admin menu that sits in front of FXServer, the FiveM server process. It gives you a browser panel to control the server instead of typing console commands by hand. The core jobs it handles:

• Starting, stopping and restarting the server, with a graceful shutdown that lets resources flush data before the process ends
• A recipe-based deployer that can stand up a fresh server in under a minute
• Live console output and per-resource CPU and RAM monitoring
• Scheduled restarts with automatic in-game warning announcements
• A self-contained player database for bans and warnings that does not require its own MySQL setup
• An in-game admin menu with permissions, plus Discord integration

1. First-boot setup

Setup is mostly a guided wizard. The flow is the same on Windows and Linux, with the obvious difference in how you launch the binary.

Get a server build

Download a recent recommended artifact from the official Cfx.re artifacts listing. On Windows you extract the archive and run FXServer.exe. On Linux you extract it and run the run.sh script. You do not need to point it at a server.cfg for the very first launch - txAdmin starts on its own and builds your configuration through the wizard.

Open the panel

txAdmin runs its web panel on TCP port 40120 by default. Open a browser and go to:

http://YOUR_SERVER_IP:40120

If you are setting up on your own machine, that is http://localhost:40120. On a remote box, make sure port 40120 is allowed through the firewall. Note that this is a different port from the game port, which is 30120 by default - players connect on 30120, and you administer on 40120.

Link your Cfx.re account

On first boot, txAdmin asks you to link a Cfx.re account and create an admin login. It also creates a txData folder, which is where it stores your server configuration, the player database, logs and backups. This folder is the heart of your txAdmin install. Knowing where it lives matters later, both for backups and for recovery.

Deploy or import

The wizard then offers the recipe deployer. Picking the default FiveM template downloads a working base server in well under a minute, which is a reasonable starting point if you are building from scratch. If you already have a configured server folder, you point txAdmin at your existing server.cfg instead and it manages that.

2. Scheduled restarts

A FiveM server accumulates memory over hours of play. Scheduled restarts clear that and keep tick times stable. txAdmin handles this natively, so you should never need a third-party cron job for it.

You configure restarts in the txAdmin settings under the scheduled restarts section. Add times in 24-hour format, for example:

00:00
06:00
12:00
18:00

That gives a restart every six hours, which is a common cadence. Servers with lighter loads often run every twelve hours instead. The right number depends on how fast your resources leak memory, which you can watch in the txAdmin monitoring graphs.

Restart warnings

txAdmin automatically warns players before each scheduled restart with an in-game countdown, so nobody is dropped without notice. If you would rather show the countdown through your own UI, you can suppress the default announcement and listen for txAdmin events instead:

# In server.cfg, hide the built-in announcements
setr txAdmin-hideDefaultAnnouncement true
setr txAdmin-hideDefaultScheduledRestartWarning true

Your resources can then subscribe to the txAdmin restart and announcement events and render the warning however your server theme prefers. For most servers the default countdown is fine and you can skip this entirely.

3. Backups: do this before you have anything to lose

This is the part new owners skip and later regret. A FiveM server has live state. Players earn money, buy vehicles, store items in inventories, claim houses and accumulate bans, and all of that is written to disk and to your database while people play. Lose it and you lose your community's progress.

What txAdmin backs up

txAdmin can back up its own txData folder on a schedule, which preserves your server configuration, the player and ban database, and your admin setup. In recent builds there is a dedicated backups area in settings where you point backups at a local folder, and many hosts let you push them off the machine as well.

Two things worth being clear about:

• The txData backup is not your MySQL backup. If your scripts use an external MariaDB or MySQL database for player data, that database needs its own backup routine. txAdmin's master actions include a database backup option, but you should still schedule regular dumps of your SQL database independently.
• Off-site copies matter. A backup sitting on the same disk as the live server dies with that disk. Keep at least one copy somewhere else.

A workable backup routine

1. Enable txAdmin's scheduled backup of txData.
2. Add a separate scheduled dump of your SQL database, for example a nightly mysqldump on Linux or a scheduled export on Windows.
3. Copy the most recent backups off the server to separate storage on a schedule.
4. Once - actually do this once - restore a backup onto a test environment to confirm it works. An untested backup is a guess, not a safety net.

4. Master actions and the player database

txAdmin's settings include a master actions area, which holds the heavier operations you do not want behind a normal staff role. From there you can make a database backup, clean the database, reset the FXServer configuration, and set how long inactive players stay on a whitelist before they are removed.

Bans live in txAdmin's own database and are tied to hardware identifiers - the player's license, IP and HWID token - rather than just a name. That makes them meaningfully harder to evade than a simple name or in-game kick. Combined with the action log, which records who did what in the panel, this gives you both enforcement and accountability for your staff.

Security goes hand in hand with this. Locking down the panel, hardening your events and keeping ban evasion difficult are all part of the same job. Our guide on stopping cheaters and securing a FiveM server covers the server-side side of that picture in detail.

5. Recovery: getting back in when access breaks

Things go wrong. You lose your admin password, someone who should not have access still has it, or the server starts from the wrong folder and suddenly "all your data is gone" when in fact it is just looking at the wrong txData. Most txAdmin emergencies fall into a few categories.

Lost or compromised admin access

txAdmin can regenerate master credentials from the server console on the machine itself, which is why physical or SSH access to the host is the real key to the kingdom. If you suspect someone has unauthorised panel access, the correct response is to reset the txAdmin admin setup immediately from the console and re-link a fresh account, then review the action log for what they touched.

"My data disappeared" after a move

A very common false alarm: you copied the server to a new folder or changed the launch path, started FXServer from the wrong place, and txAdmin generated a brand new empty txData. Your real data is usually still sitting in the old folder. Before assuming the worst:

• Stop the server.
• Confirm which txData folder txAdmin is actually using.
• Start consistently from the intended artifact path and data path so it loads the right configuration.

Restoring from a backup

If something genuinely corrupted, this is where the backups you set up earlier pay off. Stop the server, replace the damaged txData with your most recent good copy, restore your SQL database from its dump, and start again. Because you tested the restore path beforehand, this is a routine operation rather than a panic.

A practical txAdmin checklist

• Run a recent recommended server build - txAdmin is already inside it
• Reach the panel on port 40120, keep it off the public internet
• Link a Cfx.re account and note where your txData folder lives
• Set scheduled restarts every 6 to 12 hours with warnings enabled
• Enable txData backups and a separate SQL database dump
• Keep at least one backup copy off the server
• Do one test restore so you know the process works
• Use HWID-based bans and review the action log regularly
• Keep console or SSH access secure - it is your recovery path

Conclusion

txAdmin does a lot of the unglamorous work that keeps a FiveM server alive, and most of it is already running the moment you start a modern server build. Spend an hour on the parts that matter - sane restart times, real backups you have actually tested, locked-down panel access, and a clear recovery plan - and you turn txAdmin from a panel you ignore into the thing that saves you on the day something breaks.

Set it up properly once, verify it works, and revisit the settings whenever you change hosting or add major systems. The owners who never have a bad week are the ones who prepared for it before it arrived.