txAdmin for FiveM
The web panel bundled with every FXServer build: process management, recipes, players, bans, scheduled restarts and live console.
txAdmin ships inside the server artifacts, which makes it the one tool essentially every FiveM server runs. It creates the server from a recipe, keeps the process alive, schedules restarts, handles bans and warnings, and gives staff a browser console. For anyone building a loading screen it matters for one specific reason: txAdmin's scheduled restart warnings and its deployer are what decide how often players see that screen.
At a glance
| Maintainer | tabarra |
| Latest release | v8.1.1 · 2026-06-05 |
| Last code change | 2026-08-05 |
| Licence | MIT |
| Written in | TypeScript |
| GitHub stars | 928 |
| Status | Active |
Figures read from the repository on 2026-09-22.
Why servers run it
- It creates a playable server from a recipe in minutes, including QBCore and ESX.
- Auto-restart with in-game warnings, which is the difference between a scheduled restart and a mass disconnect.
- Ban and warn management with a real database behind it rather than a text file.
- A live console and a resource list you can restart from a browser on your phone.
- Player analytics, including how long people stay — which is the number a loading screen actually moves.
Installing txAdmin
1. It is already installed
Run FXServer.exe (or the Linux run.sh) and txAdmin starts on port 40120. There is nothing to download.
2. Link your Cfx.re account
First run gives you a PIN in the console. Match it in the browser and link the account that will own the server.
3. Pick a recipe or an empty server
The recipes install a full framework. 'Remote template' and 'empty' are the other two starting points.
4. Set the restart schedule
Settings → Restarter. Pick times, and leave the in-game warnings on — players who get a countdown come back, players who get dropped do not.
5. Lock it down
Do not expose port 40120 to the internet without a reverse proxy and HTTPS. The panel controls the whole server.
Working examples
server.cfg — the pieces txAdmin manages for you
# txAdmin writes and owns these. Editing them by hand is how you lose them.
# Your own settings go below, and survive.
ensure mapmanager
ensure chat
ensure spawnmanager
ensure sessionmanager
ensure basic-gamemode
ensure hardcap
# Your loading screen, started like any other resource
ensure my_loadingscreenReading the restart warning from a script
-- txAdmin announces scheduled restarts on this event, which is the right
-- hook for a 'server restarting' overlay rather than a timer of your own.
AddEventHandler('txAdmin:events:scheduledRestart', function(data)
-- data.secondsRemaining, data.translatedMessage
SendNUIMessage({ action = 'restartWarning', seconds = data.secondsRemaining })
end)What goes wrong
Port 40120 open to the world is a full server compromise waiting to happen. Put it behind a reverse proxy with HTTPS and a strong password, or bind it to localhost and reach it over SSH.
txAdmin owns part of server.cfg. Hand-editing the block it manages means your change disappears on the next settings save.
Recipes pin versions. A recipe run a year ago installed a year-old framework; there is no update button.
The restart warning is a resource-level event, not a game feature. If your loading or HUD scripts do not listen for it, players get no notice.
txAdmin — questions people ask
Do I need txAdmin?
Where are the txAdmin docs?
Does txAdmin control the loading screen?
Runs alongside
The official base resource set every FiveM server starts from: mapmanager, chat, spawnmanager, sessionmanager, hardcap and friends.
An in-game admin menu with ace-based permission tiers — the usual choice when txAdmin's web panel is not enough and vMenu is too much.
The MySQL wrapper the modern FiveM stack runs on: promise-based, prepared-statement aware and a drop-in replacement for mysql-async.