txAdmin login: there is no default password

Short answer: txAdmin has no default username and no default password. On first boot it prints a 4-digit PIN in the FXServer console, you enter that PIN at http://localhost:40120, link a Cfx.re account, and then you choose your own username and password. If you have lost access, stop FXServer and delete txData/admins.json to start that process again.

What the console actually prints on first boot

When txAdmin starts and finds no admins file, it generates a random four-digit PIN and prints a block that ends with the line Use the PIN below to register:, followed by the PIN itself. Above it you get All ready! Please access: and the URLs it is listening on. On Windows it also opens your browser on the registration page by itself. The PIN is generated in core/modules/AdminStore/index.js with a plain Math.random() call, so it is different on every boot and there is nothing to look up: if you did not catch it, scroll the console up or restart the server.

Does the txAdmin PIN expire?

No. A widely copied hosting article claims the PIN expires after five minutes, and search summaries repeat it. There is no timer anywhere in the code. The PIN is held in memory and compared on submit, and the only thing that invalidates it is creating the master account, which sets it to undefined. It also dies when the process dies, so restarting FXServer gives you a new one. That means you are not in a hurry, but it also means the PIN is live for as long as the server is up: if your panel port is reachable from the internet and you have not registered yet, somebody else can claim your master account. Register immediately, or keep the port closed until you do.

Creating the master account needs a Cfx.re account

There is no way to create the first admin with just a local username and password, whatever the hosting guides say. After the PIN is accepted, txAdmin returns an OAuth URL to idms.fivem.net, you approve the request, and only then do you pick a name and a password between 6 and 128 characters. Your FiveM identifier is mandatory in that step; linking Discord is optional. Cfx.re is the only identity provider txAdmin supports, and Discord is not a login method for the web panel, even though it can be linked to your account afterwards.

How you sign in afterwards

The same admin has two routes: username and password, which txAdmin's own documentation calls the backup password, or the Cfx.re button if the account has a FiveM ID linked. If the password fails you get Wrong username or password!, deliberately identical whether it was the username or the password that was wrong. If the Cfx.re button fails, the errors are more specific and worth knowing: clock_desync means your server clock has drifted, and timeout means the machine could not reach idms.fivem.net at all.

Where the credentials live

In txData/admins.json — at the root of txData, not inside txData/default. Several hosting guides get this wrong; the profile folder holds configuration, not admins. Each record carries the username, a master: true flag for the first account, a bcrypt password_hash that always starts with $2, a password_temporary flag, and the linked Cfx.re provider data. Passwords are never stored in plain text, so there is nothing in that file you can read and reuse.

You have lost access: what to do, in order

1. If another master account exists, ask them to reset yours from Admin Manager. It generates a 20-character temporary password shown exactly once. An account flagged as temporary can then change its own password without entering the old one.
2. If nobody else has access, stop FXServer first. This step is not optional. With the server running, txAdmin watches admins.json by SHA1 hash and puts it back, logging The admins.json file was modified or deleted by an external source, txAdmin will try to restore it. People conclude the method does not work when in fact they never stopped the server.
3. Delete txData/admins.json, start FXServer again, and read the new PIN from the console. You are back at first-boot registration.

One thing you will read elsewhere and should ignore: there is no --reset-admin flag. txAdmin does not parse command-line arguments for anything like it, and the ConVars it does read are unrelated. Running it does nothing except make you think the reset failed.

When localhost:40120 does not open

Usually because localhost means the machine you are typing on, not the machine running the server. If FXServer is on a VPS or a managed host, that address will never reach it. txAdmin binds to 0.0.0.0 by default, so the port is listening; what stands between you and it is your firewall, your host's port mapping, or the fact that a managed panel publishes txAdmin on a different external port. Do not solve this by opening 40120 to the world — reaching txAdmin safely covers the reverse proxy, VPN and tunnel options.

Do not hand the master account to your staff

The recovery process above is the reason. The master account is a single point of failure whose reset requires stopping the server and editing files on disk, so the more people who hold it, the worse that day goes. And any txAdmin admin, even with permissions trimmed, is inside a panel that can restart the server and edit its configuration.

Most of your staff do not need that. A moderator usually needs to look: watch what a player is doing and check how long they have played. That is the split FiveMonitor is built around — your moderators get their own sub-accounts with Discord sign-in, they watch player screens from the browser and read the playtime txAdmin already records in playersDB.json, and nobody hands out a panel credential or opens port 40120 to another person. To be clear about scope: FiveMonitor is not an anticheat and does not replace txAdmin. You keep txAdmin for running the server.

Plans start at 9.99 EUR/month, with Pro at 15.99 EUR/month for unlimited players, a 7-day free trial and no card required. Compare the available plans or create your account and start the free trial.