How to Set Up txAdmin on Your FiveM Server

Your server deploys with txAdmin running and the game server deliberately held back. Five steps in the wizard bring it online, and one of them, the database screen, is where nearly everyone stops. The values are on this page.

First: an offline server is normal here

A fresh FiveM deploy starts txAdmin and nothing else. The game port stays silent on purpose until you have claimed the admin account, supplied a licence key and chosen a server build, because a FiveM server with none of those cannot start. So for the first few minutes after deploying, your dashboard showing the server as not yet accepting players is the expected state rather than a fault.

The dashboard says as much: the server card turns amber with Action needed: finish setup in txAdmin, and opening it gives you the txAdmin link and the PIN described below. Nothing on this page needs a support ticket.

The five steps

1. Open txAdmin

You do not need to find an address. In your dashboard, the amber banner on the server card opens a panel with an Open txAdmin button, and the same button sits on the Players tab once you click Manage. It points at your server’s own txAdmin domain, which keeps working after a failover because it always resolves to whichever instance is currently primary. That is why we link it rather than printing a node IP: an IP is correct until the day it is not.

2. Claim the admin account with the PIN

On its first run txAdmin asks for a PIN that it prints only to the server console, and then asks you to create a master admin username and password for the panel itself. On a managed server that console is not something you would normally see, so the dashboard reads the PIN out of the container log and shows it in the same panel as the txAdmin button, ready to copy.

The master admin login is not your Flux account, not your Cfx.re account and not the database password. It is a third credential, it is the way back into your panel, and nobody can reset it for you. Store it before moving on. If the PIN has expired by the time you use it, restart the server from the dashboard and a fresh one is printed.

3. Add your cfx.re licence key

The wizard asks you to link a Cfx.re account and paste a server key. Generate a free one at portal.cfx.re and paste the cfxk_ value. The key is issued to your account rather than ours, which is the reason the server is yours to move; the deployment sets NO_LICENSE_KEY=1 so that it is supplied here rather than baked into the app. If you ever regenerate the key, you can change it later without walking the wizard again: it is a field in the Server Settings tab of the management panel.

4. Configure the database connection

This is the step that produces the most support tickets, and it has exactly one correct answer. txAdmin’s auto-detect will not find your database, so enter these values by hand on the Database screen:

Field	Value	Why
Host	operator	The sync operator, not the database container
Port	3307	What the operator listens on inside your app
Username	root	Set by the spec, not editable
Password	MYSQL_ROOT_PASSWORD	The one you chose at deploy. Reveal it in Deployment Settings
Database	fivem	Created empty for you before the server starts

Host is the sync operator rather than the database container, the password is the one you chose at deploy, and the database itself is created empty for you before the server starts.

The password lives in the management panel under Deployment Settings, as MYSQL_ROOT_PASSWORD, with a reveal button and a copy button. The panel also prints these four fixed values on a card beside it, so you can copy them straight into txAdmin without coming back here.

Two guesses are worth naming because both are wrong and both look right. Host is not localhost: txAdmin and the database are separate containers. Host is also not mariadb, even though there is a component with that name. Everything goes through the operator, which is what replicates each write to the other instances; writing straight to one MariaDB would desync your city and lose it on a failover.

5. Choose a server build

The last screen offers a recipe or an empty server. A recipe such as qbcore, qbox or ESX downloads the framework, its resources and its SQL schema and imports the schema into the database you just connected, which is the fastest route to a working roleplay server. The blank option suits anyone migrating a build they already have. Either way txAdmin then downloads the FiveM artifact, writes server.cfg and starts the server, and your dashboard turns green within a few minutes.

If txAdmin says it cannot connect

Check the host and port first, because localhost and mariadb are the common guesses and neither works. If those are right, it is a password mismatch. The database is provisioned with MYSQL_ROOT_PASSWORD and the operator authenticates with DB_INIT_PASS, and the two must be identical for the database to initialise at all. The panel keeps them linked for exactly that reason: editing one rewrites the other, and the field is marked as linked so the behaviour does not look like a form refusing your input. What you type into txAdmin has to be that same value.

Getting back in later

After the wizard, txAdmin is the everyday panel: live console, resources, bans, the CFG editor and scheduled restarts. The same Open txAdmin button gets you there, and you log in with the master admin account from step 2. The dashboard keeps the layer underneath: restarts and redeploys, the file browser, hardware, the database health across nodes and backups.

Not deployed yet?

txAdmin on its own address, the database created and connected before the first resource loads, and both ports published without a firewall to touch. First week free if your Flux account is new.

Frequently asked questions

What do I enter in the txAdmin database screen?

Host operator, port 3307, username root, database fivem, and the MYSQL_ROOT_PASSWORD you chose when you deployed. Enter them by hand, because txAdmin’s auto-detect does not find the operator. The password is revealed and copied from Deployment Settings in the management panel.

Why is my FiveM server offline right after deploying?

Because it has not been set up yet, and that is by design. The deployment runs with no default config and no licence key, so txAdmin comes up on its own address and the game port stays silent until you claim the admin account, add your cfx.re key and deploy a server build. It goes online a few minutes after the wizard finishes.

Where do I find the txAdmin PIN?

In your dashboard. txAdmin prints it only to the server console, so the dashboard reads it from the container log and shows it, ready to copy, next to the Open txAdmin button. If it has expired, restart the server and a new one is printed.

Can I connect to MariaDB directly instead?

No, and it is worth knowing why. Every write has to go through the operator on port 3307, which replicates it to your other instances. Pointing anything at a MariaDB container directly writes to one machine only, and that data is what you lose the next time the primary changes.

Do I have to use a recipe like qbcore or ESX?

No. A recipe is the fastest path because it imports the framework’s SQL schema into your database for you, but the blank option is there for anyone bringing an existing build. You can upload resources through the file browser and import a SQL dump afterwards either way.

I lost my txAdmin master admin password. Can you reset it?

Not from our side: that account lives inside txAdmin on your server rather than in our billing or dashboard, so we have nothing to reset. It is recoverable from the server itself, and the management panel gives you the console and the file browser you need. Open a support ticket and we will walk you through it, because it is not a reason to redeploy and lose the city.