txAdmin on Linux: Start, Secure and Fix Common Errors
txAdmin is the web interface that is built into the FiveM server files, so there is nothing separate to install on Linux. Start the server with ./run.sh without +exec server.cfg, open the address printed in the console (port 40120 by default), log in with your Cfx.re account using the one-time PIN, and deploy a recipe. Keep port 40120 restricted to your own IP.
- Install: none. txAdmin comes with the FiveM server build.
- Start: run
run.shwith no+execargument. - Address:
http://YOUR_SERVER_IP:40120by default. - First login: PIN from the console, then your Cfx.re account.
- Data folder:
txData, created on first run.
What txAdmin does
txAdmin starts and stops your server, restarts it on a crash or on a schedule, shows the live console, manages admins and players, and includes the recipe deployer that sets up a server in a few minutes. According to the txAdmin project it is a component of the FiveM server, so no separate download is needed.
Start txAdmin on Linux
- Install and extract the server build as shown in the Linux install guide.
- As the game user, run
cd ~/FXServer/server && ./run.sh. - On first start, the console prints the txAdmin URL and a PIN. FiveM creates the
txDatafolder. - Open the URL in your browser, enter the PIN, and link your Cfx.re account to create the owner login.
- Run the setup: choose a server name, deploy a recipe, enter your license key from the Cfx.re Portal, and fill in the database details if the recipe needs them.
Run it inside screen or, for a real server, as a systemd service as explained in the install guide.
Ports and secure access
txAdmin listens on TCP 40120 by default. It controls your whole server, so do not leave it open to everyone.
Option 1: allow only your IP
ufw allow from 203.0.113.50 to any port 40120 proto tcpOption 2: SSH tunnel
Do not open 40120 at all. From your PC:
ssh -L 40120:127.0.0.1:40120 [email protected]Then browse to http://127.0.0.1:40120 on your own computer.
Changing the txAdmin port or data folder
The txAdmin docs list environment variables. TXHOST_TXA_PORT sets the txAdmin port (default 40120, it cannot be 30120), and TXHOST_DATA_PATH sets where txData lives (on Linux the default is the folder that contains run.sh, so it moves with the artifacts folder). Be careful with TXHOST_INTERFACE: the docs say it also forces the game server to bind that interface, so setting it to 127.0.0.1 on a public server would stop players connecting. Use the firewall or a tunnel instead.
The FiveMRides panel Protection addon can close admin ports to the public for you. See the panel page.
Recipes: QBCore, ESX and others
A recipe is a script of steps that downloads resources and writes a server.cfg. The deployer lists the recipes available in your txAdmin version; typically a default Cfx.re recipe, and community recipes for frameworks such as QBCore and ESX. Recipe names, versions and the resources they pull change over time, so read what the recipe will download before you accept it.
- Create the database first (see the database step) and enter the connection details.
- Give the recipe an empty target folder.
- Do not mix two frameworks in one server. Start with one.
- After deployment, review
server.cfgbefore you start the server.
Common txAdmin errors on Linux
| Symptom | Likely cause | What to check |
|---|---|---|
| Page does not load on port 40120 | Firewall or host firewall | Allow your IP on 40120, check the service is running, ss -ltnp | grep 40120 |
| PIN not accepted | Old PIN or a restart happened | Read the newest PIN in the console or journalctl -u fivem |
| Login with Cfx.re fails | Browser blocks the redirect, clock wrong | Allow cookies, check the server time with timedatectl |
| Recipe fails to download | No outbound HTTPS, disk full | Test with curl -I https://github.com, check df -h |
| Database connection error | Wrong user, password or host | Test with the mariadb client using the same credentials |
| Server runs but players cannot join | Port 30120 closed on UDP or TCP | Open both in ufw and the host firewall |
| txAdmin loses settings after an update | txData was in the replaced folder | Keep txData outside the artifacts folder or set TXHOST_DATA_PATH |
| Server stops when SSH closes | Started in a normal session | Use screen or a systemd service |
Updating
txAdmin is updated together with the server build. When you move to a newer build, keep txData in place so admins and server profiles remain. The FiveMRides panel automates the weekly artifact update and keeps txAdmin data, as noted in our panel release notes.
The FiveMRides Server Panel installs a FiveM server on your own Linux VPS with one command, then gives you a web panel for updates, backups and protection. One lifetime license, and it is also included with Studio Max and Unlimited. FiveMRides is independent software and is not affiliated with Cfx.re or Rockstar Games.
Questions about txAdmin on Linux
How do I install txAdmin on Linux?
You do not install it separately: it is part of the FiveM server files. Extract the build, run run.sh without +exec server.cfg, and open the URL printed in the console.
What port does txAdmin use?
TCP 40120 by default. You can change it with the TXHOST_TXA_PORT environment variable. It cannot be 30120.
How do I open txAdmin securely?
Allow only your own IP in the firewall, or use an SSH tunnel to port 40120. Do not leave it open to the whole internet.
Where is the txData folder on Linux?
By default in the folder that contains run.sh, according to the txAdmin docs. You can move it with TXHOST_DATA_PATH, which is a good idea before you switch to a new artifacts folder.
Can I run txAdmin as a service?
Yes. A systemd service that runs run.sh without +exec starts txAdmin on boot. See our install guide for a unit file.
How do I set up QBCore or ESX in txAdmin?
Use the recipe deployer, choose the framework recipe, enter your license key and database details, and let it download the resources. Recipe names change, so use the list shown in your txAdmin.
Does the FiveMRides panel replace txAdmin?
No, they work together. The panel automates the system around txAdmin: install, firewall, updates, backups and protection.