txAdmin Setup Guide (2026)
Quick answer: txAdmin is the web panel bundled with every FXServer artifact — it lives on TCP port 40120. The first time you start FXServer, txAdmin prints a 4-digit PIN to the console; open http://your-server-ip:40120, enter the PIN, create a master account, and you're done. No config.json editing required.
This page walks the entire setup top to bottom, then covers deployer recipes, scheduled restarts, Discord wiring, RedM, and the seven issues that catch most server owners.
Installation
txAdmin ships inside the FXServer artifact — there is no separate download.
Windows
- Download the latest artifact from runtime.fivem.net (Windows).
- Extract to
C:\FXServer\server. - Create an empty sibling folder
C:\FXServer\txData. Both must be writable by the user that runs FXServer. - Open a terminal in
C:\FXServer\serverand runFXServer.exe +set serverProfile default. - Watch the console — txAdmin prints a PIN line:
[txAdmin] To setup txAdmin go to http://localhost:40120/addMaster/pin?pin=1234
Linux
- Download the artifact from runtime.fivem.net (Linux).
- Extract under
/opt/fxserver/serverand create/opt/fxserver/txData. - From the
serverdirectory run./run.sh +set serverProfile default. - Same PIN line appears in the terminal — copy the URL.
First-Run: PIN & Master Account
- Open
http://your-server-ip:40120in a browser. If you can't reach it: TCP 40120 is not open in the firewall, or the bind address intxData/default/config.jsonis127.0.0.1(default-bind only on first start — change to0.0.0.0for remote access). - Paste the 4-digit PIN from the console.
- Sign in with Cfx.re ID (recommended — gives you 2FA via the Cfx.re site) or create a local username + password.
- Add your Cfx.re license key from keymaster.fivem.net in Settings → FXServer → License Key.
Lost the master account? Stop FXServer, run it once with --reset-admin (FXServer.exe --reset-admin on Windows, ./run.sh --reset-admin on Linux). A fresh PIN is printed; reclaim master with that.
Deploying a Server
txAdmin's "Deployer" creates a working server from a YAML recipe — you don't need to wire ESX, QBCore, or vRP by hand.
| Recipe | What it ships with | Best for |
|---|---|---|
| esx-legacy | ESX framework, MySQL schema, base inventory, vehicle and job scripts | Roleplay servers wanting the most plugin support |
| qbcore-framework | QBCore framework, ox_inventory option, baseline jobs | Modern roleplay with cleaner Lua APIs |
| vrp | vRP base + addons | Lightweight RP without the ESX/QB overhead |
| blank | Just FXServer + server.cfg skeleton | You're bringing your own framework |
| Custom URL | Any GitHub-raw URL pointing at a recipe.yaml | Community recipes (e.g. cfx-default-redm) |
Pick a recipe in Master Actions → Deployer, fill in the MySQL credentials when prompted, click Run. txAdmin downloads dependencies, runs SQL imports, builds server.cfg, and starts the server.
Scheduled Restarts
Restarts live under Settings → General → Scheduled Restarts. The default RP cadence is two restarts per day at 06:00 and 18:00 server local time. Each scheduled time produces three warnings (15min / 5min / 1min) before the actual restart.
To set restarts at, say, every 6 hours:
- Add four times in 24h format:
00:00, 06:00, 12:00, 18:00. - Tick Run scheduler in maintenance mode if you don't want player connections during the restart window.
- Set Boot Cooldown to 60 seconds so workers fully detach before restart.
Discord Integration
The simplest integration is the webhook for status announcements. Open Settings → Discord and paste your channel webhook URL. txAdmin will post on:
- Server starting / stopping / crashing
- Scheduled restart warnings
- Master account login from a new IP
For the bot integration (per-player join announcements, slash commands, role-gated whitelist) create a Discord bot at discord.com/developers, paste the bot token in Settings → Discord → Bot Token, and invite the bot to your server with bot + applications.commands scopes.
Player Management
The Players tab shows every player who has ever connected (even past sessions). Each row has:
- Identifiers — Steam, Discord, FiveM, License2, IP. Use these for cross-banning.
- Notes — free-text, visible to all admins. Persists across restarts.
- Warnings — counted; auto-ban triggers can be configured.
- Ban — choose duration (1h, 1d, 7d, 1mo, perma) and reason. The ban is enforced by every txAdmin-managed identifier, so banning by Steam ID also blocks the same Steam account on Discord rejoin.
RCON-Style Console Access
txAdmin's Live Console tab gives you the same surface as connecting via RCON — every say, ban, start, stop, and refresh command is available, with persistent history. For external automation (Discord bots, monitoring) use the txAdmin REST API on /api/ with the auth token from Settings → API.
Common Troubleshooting
txAdmin won't load on port 40120
Check three things in order: (1) is FXServer running — txAdmin won't start without it; (2) is the firewall open on TCP 40120 (Windows: netsh advfirewall; Linux: ufw allow 40120); (3) is the bind address 0.0.0.0? On first start it can be 127.0.0.1, in which case you can only reach it via localhost. Edit txData/<profile>/config.json and change webServer.bind.
"License invalid" on boot
Your Cfx.re license key is missing, expired, or already bound to another IP. Generate a fresh one at keymaster.fivem.net and paste it in Settings → FXServer → License Key. The server hot-reloads automatically.
Lost master account access
Stop FXServer. Run with --reset-admin. A new PIN is printed in the console — claim master via the web panel within 5 minutes (the PIN expires).
txAdmin keeps restarting itself
Check the FXServer crash log inside txData/<profile>/data/crashes/. The most common cause in 2026 is an outdated oxmysql resource — update it to v2.7+. Second most common is a bad recipe deployment that didn't import the SQL schema cleanly; rerun the deployer.
High CPU usage on the txAdmin process
Disable Live Console streaming to non-active sessions in Settings → General. Increase the metric polling interval. Move the txAdmin profile directory off a network share if you mounted one — the file watcher hammers iops.
Database connection refused after deployer
The recipe expects a MySQL/MariaDB instance reachable from the server. Verify mysql_connection_string in server.cfg, confirm the user has the fivem schema, and check that your DB host allows external connections (or run mariadb-server locally and point at 127.0.0.1:3306).
Discord bot doesn't respond
Confirm the bot has both bot and applications.commands scopes when invited. Re-paste the bot token after Discord rotated it (any leak forces a rotation). Check Settings → Discord → Status panel — txAdmin shows the last bot heartbeat.
Best Practices
- Use Cfx.re ID for master, not local password. 2FA is enforced on the Cfx.re side and the recovery flow is faster.
- Rotate the API token quarterly. Settings → API has a regenerate button.
- Run scheduled backups via the panel. Settings → Backups can target a local folder or any S3-compatible bucket. Test the restore path at least once.
- Keep the artifact updated. Major Cfx.re releases break older recipes; subscribe to the FiveM newsletter or the txAdmin GitHub releases page.
- Don't expose port 40120 to the internet without auth. If you need remote access, front it with Cloudflare Access or Tailscale rather than opening it raw.
Next Steps
- Choose between ESX and QBCore frameworks
- Optimize FiveM server performance
- Browse other game server guides
Professional FiveM hosting: Supercraft ships every FiveM plan with txAdmin pre-configured, MySQL provisioned, scheduled restarts wired, and Discord webhook ready. Launch a FiveM server in under three minutes.