The txAdmin dashboard: every section, and what it cannot do

Short answer: the txAdmin dashboard is the web panel that already ships inside FXServer, served on port 40120. Its sections are Dashboard, Live Console, Resources, Server Log, CFG Editor, Players, History, Player Drops, Allowlist, Admins, Settings and System. It does show each player's accumulated playtime. It cannot show you a player's screen from the browser: spectating only works in-game.

What the panel is and where it opens

txAdmin is not something you install. It comes with FXServer and starts with it, serving a web interface on the port set by the txAdminPort ConVar, which the Cfx.re documentation describes as "The TCP port to use as HTTP Server. The default is 40120." It binds to 0.0.0.0 by default, meaning every interface, so if you cannot reach it the obstacle is almost always your firewall or your host's port mapping rather than txAdmin itself. The official repository is now citizenfx/txAdmin, MIT licensed, and describes itself as "The official FiveM server management platform used by over 27k servers!".

The full map of the panel

The left side covers the server, the top bar covers people. In the current version the routes are:

• Dashboard (/) — performance and player-count overview.
• Live Console (/server/console) — the FXServer console, live, with a command input.
• Resources (/server/resources) — start, stop and restart resources.
• Server Log (/server/server-log) — joins, chat, deaths, commands and explosions.
• CFG Editor (/server/cfg-editor) — edit server.cfg from the browser.
• Players, History, Player Drops, Allowlist — the people side, in the top bar.
• Admins and Settings — permission-gated.
• System — a dropdown with Master Actions, Diagnostics, Console Log and Action Log.

If a guide you are reading shows a "Whitelist" entry, it predates version 8.1.1, where it was renamed to Allowlist. The old /whitelist path still exists purely as a redirect.

What the Dashboard front page actually tells you

Less than people expect. The front page renders four cards: player drops, server stats, and two performance graphs. The stats card shows exactly four numbers — Uptime 24h, Median Players 24h, FXServer Memory and Node.js Memory. There is no per-player metric anywhere on it. If the server has not been configured yet you get redirected to the setup flow instead, which is why some people never see this page at all.

Players and History: what the list contains

The Players table has four columns: Display Name, Play Time, First Joined and Last Connection, and you can sort by any of the last three. Above it there are four aggregate counters — Total Players, Players Last 24h, New Players Last 24h and New Players Last 7d. Search works by name, by notes or by player IDs (license, Discord, Steam and so on), with filters for admins, online players, allowlisted IDs and more. History is the separate record of admin actions taken against players: warns, kicks and bans.

Does the txAdmin panel show playtime?

Yes. This is worth stating plainly because a lot of pages, including some selling playtime scripts, claim otherwise. The Players table has a sortable Play Time column, and the underlying value lives as playTime in txData/playersDB.json. If all you need is "how long has this person played in total", txAdmin already answers it and you do not need anything else.

What it stores is a single cumulative counter per player. There is no session history, no per-day or per-week breakdown, and no way to ask when those hours happened. That is the limit worth knowing before you go looking for a tool: the question txAdmin cannot answer is not "how many hours" but "how were those hours distributed". Our guide on reading playtime from txAdmin covers where that file sits and how to work with it.

Can you watch a player's screen from the panel?

No. This is the other question people arrive with, and the answer is a clean no. txAdmin has a Spectate feature, but it lives in the in-game admin menu, requires the players.spectate permission, and requires the admin to be connected to the server as a player. There is nothing in the web panel that renders a player's view, and there is no recording. If your moderators work from a browser rather than from inside the game, that gap is real and txAdmin is not going to close it.

Live Console, Server Log and CFG Editor

These three are the ones that touch the running server, and they are the reason you should think twice before handing panel accounts out. Live Console is the FXServer console with a command input, so anyone who reaches it can run server commands. CFG Editor writes server.cfg from the browser. Server Log is read-only, and it is the one you will actually use day to day: joins, disconnects, chat, deaths, commands and explosions. We cover that one in depth in txAdmin logs and events.

An honest summary of what txAdmin does and does not do

Where FiveMonitor fits

In the three "no" rows, and nowhere else. FiveMonitor is not an anticheat and does not replace txAdmin: you keep txAdmin for running the server. What it adds is the browser-side view your moderators need — a player's live screen with no FPS cost to the server, and their playtime read from the playersDB.json txAdmin already maintains — through sub-accounts with Discord sign-in, so nobody needs a txAdmin credential to look at a player. Plans start at 9.99 EUR/month, 7-day free trial, no card. See the features or start the trial.