txAdmin Login (localhost:40120), Setup and Dashboard for FiveM

txAdmin is the free web panel and in-game admin menu built into FXServer, the FiveM server software, and it is where you start, restart and moderate your server from a browser. Most people who look it up want the txAdmin login address, a way past the PIN screen, or a way back in after losing a password, so this guide starts there.

Quick answer: There is no central txAdmin login site, because every server runs its own panel. Start FXServer without +exec server.cfg, then open http://localhost:40120 on the computer that runs it, or http://your-server-ip:40120 from anywhere else. The first time, type the 4-digit PIN from the server console and link your Cfx.re account to become the master admin. After that, txAdmin login works with the Login with Cfx.re button or your username and backup password. The current version is txAdmin 8.1.2 from 23 October 2026: the Latest FXServer build 38055 ships it, while the Recommended build 35245 still has 8.1.1.

Everything below was checked again on 31 October 2026 against txAdmin's GitHub repository, its docs and source code, the official FiveM docs and Cfx.re's artifact version list.

txAdmin at a glance

txAdmin login and localhost:40120

Each server runs its own txAdmin, so the login page is on your server, on TCP port 40120 unless you or your host changed it.

Which address to open

When txAdmin is ready, the FXServer console prints a box with "Please access:" and the address to use. txAdmin's startup code fills it in like this:

localhost always means the computer your browser runs on, so http://localhost:40120 only works on the machine that runs FXServer. Type http://, not https://: txAdmin has no built-in HTTPS, and its feature graveyard points you to a reverse proxy or a Cloudflare Tunnel if you want it. The old monitor-xxxxx.users.cfx.re address was retired, so bookmarks to it no longer work.

The first login and the PIN

While txAdmin has no admin accounts, the box also says "Use the PIN below to register:" above a 4-digit PIN. On Windows your browser opens the PIN page with the PIN filled in; elsewhere you type it. You then link your Cfx.re account and set a backup password, which makes you the master admin. The setup steps below show each screen.

Every start of the FXServer process makes a new PIN, so if you lost it, scroll up in the console or restart the process. On a hosted server, check the console in your host's panel. "Wrong PIN." means a typo or an old PIN. "Master account already configured." means someone already finished this step, so use the normal login.

Logging in after that

The login page has two buttons, Login for a username and password and Login with Cfx.re. The master account's username is your Cfx.re name, with the backup password you set. Staff get a temporary password that txAdmin shows once and they must change at first login. If your host created your account with your Cfx.re ID, use Login with Cfx.re; if the account has no password yet, txAdmin asks you to set one.

If localhost:40120 does not load

1. Check that txAdmin runs. It only starts when FXServer runs without +exec server.cfg, and it stops when you close FXServer. "The txAdmin server shut down." on the login page means exactly that.
2. Check the machine. localhost only reaches a txAdmin on the computer in front of you, so a VPS or hosted server needs its IP address or your host's link.
3. Open TCP 40120 in the server's firewall and at your provider, as the console asks on Linux. A browser on the same machine does not need it.
4. "Failed to start HTTP server, port 40120 is already in use." means another txAdmin already runs there. Stop it, or give the second server its own port and txData folder with TXHOST_TXA_PORT and TXHOST_DATA_PATH, as the environment config docs recommend. The old +set txAdminPort convar is deprecated.
5. If TXHOST_INTERFACE is set to a LAN or public IP address, txAdmin listens only on that address, so localhost gets no answer. The box shows the address to use.

txAdmin login errors

Forgot your txAdmin password

Click Login with Cfx.re instead: a master account made through the PIN step is linked to Cfx.re, and the password is only a backup. The login page has no reset link, and changing a password under your account asks for the current one. A regular admin without a linked Cfx.re account gets a new temporary password when the master removes and adds them again on the Admins page.

If the master's Cfx.re account is gone, or the server has a new owner, start the master setup again:

1. Stop FXServer completely, with the host's stop button on a hosted server. Restarting the server from inside txAdmin is not enough.
2. In the txData folder, rename admins.json to something like admins.old.json. On Windows the folder sits next to your server folder (for example C:\FXServer\txData), on Linux in the folder with run.sh, unless you or your host moved it.
3. Start FXServer again. With no admins file, txAdmin prints a new PIN. If your host presets the master account, txAdmin creates that account again instead, so ask the host to change it.
4. Link the new owner's Cfx.re account, then add the other admins again.

The order matters. A running txAdmin keeps its admin list in memory: it checks admins.json every 15 seconds, writes its own copy back over an edited file, and saves the file again whenever an admin account changes. Renaming the file also removes every other admin account, so keep the old copy until your staff are back in.

Do you need to download txAdmin?

No. txAdmin has been part of FXServer since early 2020, and its README says there is nothing to download or install: run FXServer without a +exec server.cfg argument and FXServer starts txAdmin for you. Every server artifact on the Server Download page already contains it.

The same goes for updates. You get a newer txAdmin by updating your FXServer artifacts, not by installing txAdmin on its own, and the panel shows a warning bar when an update is out. GitHub attaches a monitor.zip file to its releases, but a normal server never needs it, and there is no reason to fetch a "txAdmin download" from any other site.

Keep the artifacts current anyway. Cfx.re says unsupported artifacts older than three months can no longer be joined from the server browser.

Starting FXServer with +exec server.cfg gives you a server without txAdmin. That manual route is the one our guide on how to make a FiveM server follows.

txAdmin 8.1.2: what changed and which build has it

txAdmin 8.1.2 came out on 23 October 2026 with a single fix, listed in its release notes as "core/webserver: reject compressed request bodies". txAdmin's web server now refuses any request with a compressed body, with HTTP status 415 and "Unsupported Content-Encoding", before it reaches the panel. The commit calls this a precautionary mitigation for CVE-2026-111497, a buffer overflow in the Brotli decoder published on 22 October 2026. The panel's own requests are not compressed, so daily use does not change.

Your FXServer build decides which txAdmin you have. Cfx.re's version list for Windows and Linux, the same list txAdmin checks for updates, showed this on 31 October 2026:

To run 8.1.2 now, choose Latest on the Server Download page and update your artifacts. On Recommended you keep 8.1.1 for now, and the panel shows a warning bar: "A patch (bug fix) update is available for txAdmin." The bottom of the left sidebar shows what you run, for example tx: v8.1.1 | fx: b35245. Keep in mind that Cfx.re's support timeline covers a Latest build until two weeks after the next release in line, against six weeks for Recommended, so Latest means updating more often.

On a server you manage yourself, you can also limit TCP 40120 to your admins' IP addresses in the firewall. Players join on the game port, and the in-game menu reaches txAdmin inside the server at 127.0.0.1 by default, as txAdmin's FXServer launcher sets it.

How to set up txAdmin for the first time

Before you start, generate a server registration key in the Cfx Portal. It starts with cfxk_, and the deployer asks for it. Our Cfx Portal guide shows where keys live now that Keymaster is gone.

These steps follow the official txAdmin setup guide, with the Linux equivalents added.

1. Download the Recommended build from the Server Download page: server.7z for Windows, fx.tar.xz for Linux. Pick Latest instead if you want txAdmin 8.1.2 right away. For FiveM for GTAV Enhanced the files are called cfx-server_win_x64.zip and cfx-server_linux_x64.tar.xz, and Windows needs the Microsoft Visual C++ 2017 Redistributable installed first.
2. Extract it into its own folder, for example C:\FXServer\server with 7-Zip or WinRAR, or with tar xf fx.tar.xz on Linux.
3. Start FXServer with no arguments. On Windows, double-click FXServer.exe (cfx-server.exe on Enhanced). On Linux, run bash run.sh in that folder.
4. Wait for the "Please access:" box with the panel address and the PIN. On Windows your browser opens by itself with the PIN filled in. On Linux, open http://your-server-ip:40120 yourself.
5. Type the PIN, click Link Account, sign in with your Cfx.re account (the one you use on forum.cfx.re) and click Yes, Allow.
6. Set a backup password of 6 to 128 characters, add your Discord user ID if you like (the number, not your name), tick the box for the Creator PLA and save. This creates your master account.
7. Name the server, in 18 characters at most. txAdmin uses this name in its own interface and in chat and Discord messages, and recipes also write it into server.cfg.
8. Choose a deployment type and a recipe, confirm the folder it suggests, and open the Recipe Deployer.
9. Work through its four steps: Review Recipe, Input Parameters (your cfxk_ key, plus database details for framework recipes), Run Recipe and Configure server.cfg.
10. Click Save & Run Server.

Players connect on the game port, which the deployer sets to 30120 by default, so open that one for them and keep 40120 for your admins.

Which deployment type and recipe to pick

The setup page offers four deployment types:

• Popular Recipes, marked as recommended. On 31 October 2026 the FiveM entries in the recipe index that this page loads are FiveM Basic Server (CFX Default), ESX Legacy, Qbox, vMenu, StreetKings and WarfareTacticsV.
• Existing Server Data, for a server.cfg and resources folder you already have. On a remote machine, upload them first.
• Remote URL Template, a recipe file from a link, which you can edit before it runs.
• Custom Template, for writing or pasting your own recipe.

QBCore is no longer a Popular Recipe. txAdmin's developer removed it from the index on 29 October 2026, and the index's README now lists it as deprecated; the commit gives no reason. The QBCore project still publishes its own recipe, so to deploy QBCore with txAdmin, paste this link into Remote URL Template:

https://raw.githubusercontent.com/qbcore-fivem/txAdminRecipe/main/qbcore.yaml

Recipes download code, and the framework ones set up a database, so a recipe from a link gets a red warning in the deployer: "Only run Recipes from trusted sources". If a recipe stops with a 401, 403 or 429 error while downloading, GitHub is limiting how often txAdmin can call it, as the recipe docs explain. Run the recipe again later.

The CFX Default recipe needs no database. ESX Legacy, Qbox and the QBCore recipe connect to a database while they deploy, so have its host, port, username, password and database name ready. Our ESX vs QBCore vs Qbox comparison helps you choose between the three.

One thing changed on 21 October 2026: the name, description, tags, language and images players see in the server list now come from the Cfx Portal instead of server.cfg. Servers deployed from the default recipe before that date got placeholder text in server.cfg, so check what the Portal shows for your key. Our Missing server data fix walks through it.

The txAdmin dashboard and panel pages

The web panel has a sidebar on the left with your server's pages and its start, stop and restart buttons, a top bar for players, staff and settings, and a live player list on the right. Pages your account has no permission for are greyed out.

Dashboard

The home page shows uptime and the median player count over the last 24 hours, the memory used by FXServer and by txAdmin's own Node.js process, a chart of player disconnects over the last six hours, and a performance chart of the server threads next to the player count. The performance chart needs 30 minutes of runtime data before it draws anything.

Live Console

The FXServer console in your browser, with command history, search and a log file. Typing commands needs the Console: Write permission, and that permission can run anything on the server.

Resources

Every resource with its state. Start, stop or restart one without typing ensure or restart in the console.

Server Log

What happens inside the game: joins and leaves, deaths, chat, explosions, menu actions and commands. Scripts can add their own lines through a txAdmin logging event.

CFG Editor

Your server.cfg in the browser, for adding an ensure line or changing a convar without SFTP. server.cfg is read when the server starts, so restart afterwards.

Players and History

Players is txAdmin's own player database, no MySQL needed. Search by name, notes or identifiers, filter for things like banned or online players, and open a player to see play time, identifiers, notes and past actions. History lists every warn and ban with its action ID, searchable by ID, reason, player identifiers or admin, and you can revoke actions from there.

Player Drops

Why players leave. A timeline of disconnects sits above breakdowns of the top crash reasons, players kicked by resources, and changes such as a new game build or a different set of boot resources. After an update that makes people crash, look here first.

Allowlist

Approved players and pending join requests when an allowlist mode is on. Before v8.1.0 this page was called Whitelist.

Admins

The Admin Manager, where you add staff and choose their permissions. More on that under daily tasks.

Settings

Tabs for General, FXServer (restart schedule, server data folder, OneSync and quiet mode), Bans, Whitelist (the allowlist settings), Discord, and Game (the in-game menu and its notifications).

System

Master Actions (database backup, database cleanup and revoking allowlist approvals, for the master account only), Diagnostics (a report on txAdmin, the host, the server and its processes, handy when you ask for help), the Console Log, and the Action Log with everything your admins did.

The in-game menu

Type /tx or /txadmin in chat, or bind Open Main Page under Settings, Key Bindings, FiveM in the game. No key is bound by default, and /tx 12 jumps straight to player 12. The menu docs are clear that it only opens for admins whose txAdmin account has their Cfx.re or Discord identifier attached.

From the menu you can toggle noclip, god mode and super jump, teleport to a waypoint, to coordinates and back, spawn, fix, delete or boost a vehicle, heal yourself or everyone, send announcements, reset a world area and show player IDs. Open a player to go to them, bring, spectate, freeze, warn, message or ban them. Heal may not revive a dead player on ESX or QBCore: the menu docs explain that frameworks track death themselves, so txAdmin sends a txAdmin:events:playerHealed event for their scripts to handle.

If /tx does nothing, the menu is probably switched off under Settings, Game, Menu. If you get an authentication error, type /txAdmin-reauth.

Daily admin tasks in txAdmin

Scheduled restarts

Set fixed restart times in Settings, FXServer, Restart Schedule, as 24-hour HH:MM times in the server's timezone. txAdmin warns you when your browser sits in a different timezone. Players get a warning 30, 15, 10, 5, 4, 3, 2 and 1 minutes before the restart, and the warnings also go to Discord if the bot has a warnings channel.

For a one-off restart, use the schedule box in the left sidebar: +15 restarts in 15 minutes and 23:30 restarts at 23:30. The same box cancels the next restart and turns it back on.

If your framework does not save players on shutdown, a script can listen for txAdmin:events:scheduledRestart and save first; the events docs show an example. Separately, txAdmin restarts FXServer by itself after a crash or a hang.

Kicks, warns and bans

Open the player from the player list, the Players page or /tx in game. Kick and DM only work while the player is online. A warn stays on the player's screen until they acknowledge it, and if they are offline or leave first, txAdmin shows it again the next time they join.

A ban needs a reason of at least 3 characters and a length: 2 hours, 8 hours, 1 day, 2 days, 1 week, 2 weeks, permanent or a custom duration. Bans match the player's identifiers and, by default, their hardware ID tokens; txAdmin's settings note that most players have 3 to 6 of those. Two options under Settings, Bans deserve a minute of your time. Ban Templates turn the reasons and lengths you use every week into a dropdown. The Ban Rejection Message points banned players to discord.gg/example until you put your real appeal link in.

The allowlist (whitelist)

txAdmin renamed the whitelist to allowlist in v8.1.0. Pick a mode in Settings:

With Approved License, a player who tries to join gets a request ID such as R1234. Approve it on the Allowlist page or with /allowlist request in Discord. With any mode on, the server list shows a lock next to your server name. In every mode except Admin-only, players can also read your Allowlist Instructions there.

Backups

txAdmin backs up one thing: its own player database. As the master account, open System, Master Actions and click Backup Database to download playersDB.json, which holds all players, bans, warns and allowlist requests. txAdmin itself suggests doing this every once in a while.

It does not back up your resources, your server.cfg or your MySQL or MariaDB database. On an ESX, QBCore or Qbox server that database holds your characters, money and inventories, so it needs backups of its own. Our guide to automating FiveM server backups covers database dumps and file copies. Copying the whole txData folder now and then keeps your admins, settings, logs and player database together.

Staff accounts and permissions

Add staff on the Admins page. Give each person a username plus their Cfx.re forum name or fivem: ID, their Discord user ID, or both, then tick permissions. txAdmin shows a temporary password once, and the new admin has to change it at first login. Attach Cfx.re or Discord even for staff who log in with a password, because without one of them the in-game menu will not open for that admin.

Nobody can hand out permissions they do not have, the master account cannot be deleted, and other admins cannot edit it. A sensible starting point:

Treat Console: Write as full access, because it runs any server command, and give Manage Admins only to people you would trust to add and remove staff. The full list with internal names is in the permissions docs.

Discord integration

Under Settings, Discord, switch the bot on and fill in its token and your Discord server (guild) ID. The bot needs the Server Members intent, which you turn on in the Discord Developer Portal. A Warnings Channel ID makes it post announcements such as restart warnings.

Then use its slash commands. /status add in a channel posts a status embed that updates every minute and, by default, shows server status, player count, the next restart and uptime. /allowlist approves players, and /info looks someone up in txAdmin's player database. txAdmin works through this bot, not through webhooks.

Common txAdmin problems and fixes

Login, PIN, password and port 40120 problems are covered in the login section at the top. Two more come up often.

txAdmin looks locked

• A setting that says "This setting is locked and cannot be changed." has been fixed by your host. Ask them about it.
• Greyed-out pages mean your admin account lacks that permission. The master account can add it for you.
• Players who are turned away, or see a lock next to your server in the list, are hitting an allowlist mode. Admin-only (maintenance mode) keeps out everyone who is not staff, so set the mode back to Disabled when your maintenance is done.

"Failed to start in time" during boot

txAdmin waits 1.5 minutes by default for each resource to start before it restarts the server. If a heavy resource trips that limit, raise Resource Starting Tolerance under Settings, FXServer, in the advanced options.

txAdmin on a hosted server

A game server host runs the same txAdmin, but txAdmin has environment variables built for providers that preset parts of it. Depending on your host:

• txAdmin may listen on a port other than 40120, and the host can fix the game port.
• The slot count can be capped at what your plan allows.
• Database details can be filled in for you in the deployer, which then notes that the provider auto-filled them.
• The host can create your master account on the first start, tied to your Cfx.re ID, so you skip the PIN and use Login with Cfx.re.
• Quiet Mode can be forced on, so server output only shows in the Live Console.

Some things txAdmin does not do on any host. It has no file manager and cannot upload resources, it has no database manager, and it does not back up your files. You upload through the host's panel or SFTP and pick Existing Server Data if you bring your own server. To redeploy from scratch, Settings, FXServer, Reset Server Data Path takes you back to the setup page; txAdmin says this "will not delete any resource files or database".

Your host's start and stop buttons control the whole FXServer process, txAdmin included. txAdmin's own restart button only restarts the game server inside it, which is why a master reset needs the host's stop button.

On our FiveM hosting txAdmin comes pre-installed and you add your own Cfx.re license key from the Portal. QBCore and ESX install from the control panel, where you also edit server.cfg, install scripts and reinstall without SSH, and larger packs go up over SFTP. If you get stuck in txAdmin, our support answers from 08:00 to 20:00 UTC by live chat, Discord and email.

Plan for one Cfx.re rule whichever host you pick: more than 48 slots needs an Element Club Argentum subscription or higher on your Cfx.re account. Up to 48 players needs nothing extra.

FAQ

Where is the txAdmin login page? On your own server, not on a central site. Open http://localhost:40120 on the computer that runs FXServer, or http://your-server-ip:40120 from another one. On a game host, use the txAdmin link in the host's panel.

What is localhost:40120? The txAdmin panel on your own computer: localhost is the machine your browser runs on, and 40120 is txAdmin's default TCP port. It only answers while FXServer runs on that machine without +exec server.cfg. Players use the game port, 30120 by default.

How do I reset my txAdmin password? Use Login with Cfx.re if your account is linked, because the login page has no reset link. The master can remove and re-add staff to give them a new temporary password. For the master account itself, stop FXServer, rename txData/admins.json, start it again and claim the server with the new PIN.

Is there a txAdmin download? Not a separate one for normal use. txAdmin ships inside every FXServer artifact, so you get it, and its updates, from the Server Download page on docs.fivem.net. GitHub lists a monitor.zip with its releases, but you do not need it to run a server.

How do I open txAdmin in game? Type /tx or /txadmin in chat, or bind Open Main Page in the FiveM key bindings. Your txAdmin account needs your Cfx.re or Discord identifier attached, or the menu will not open.

Which txAdmin version is current? v8.1.2, released on 23 October 2026. On 31 October 2026 it ships in the Latest FXServer build (38055), while the Recommended build (35245) still has v8.1.1, so you get 8.1.2 by switching to Latest or by waiting for Recommended to move.

Sources

All opened on 31 October 2026:

• txAdmin on GitHub: repository and README, v8.1.2 release, v8.1.2 fix commit, v8.1.1 release, v8.1.0 release, MIT licence
• txAdmin docs: environment config, feature graveyard, recipes, in-game menu, events, permissions, Discord status embed, custom server log
• txAdmin source: startup box, login page, login errors, password check, PIN check, password change, rate limiter, web server, admin store, admin manager, update check, warning bar, sidebar, FXServer launcher, setup page, deployer, restart schedule
• txAdmin recipes: recipe index, QBCore removal commit, QBCore's own recipe
• Cfx.re: version lists for Windows and Linux, Server Download, Setting up a server using txAdmin, End of Support/End of Life, 48-slot limit, Cfx Portal
• NVD: CVE-2026-111497