ACLClouds
ACLClouds

How do I enable txAdmin and deploy a recipe on a FiveM server?

Enable txAdmin from the Startup page, sign in with the PIN code, deploy an ESX or QBCore recipe, update the artifacts and get the server listed in the

txAdmin is the web administration panel shipped with the FiveM server (FXServer). It deploys a server recipe, restarts the server on a schedule, shows the connected players and handles bans. On ACLClouds it is disabled by default: the server runs server.cfg directly. Once enabled, txAdmin starts FXServer itself, on a port reserved for your server.

Step-by-step procedure

  1. Enable txAdmin

    Stop the server, open “Startup” and set the “Enable txadmin” variable (TXADMIN_ENABLE) to 1. The “txAdmin Port” variable cannot be edited: this port was reserved for your server when it was created and is listed in “Network”, next to the primary port.

  2. Get the address and the PIN code

    Start the server and read the console. txAdmin prints the address of its interface, http://IP:PORT with the txAdmin port, and a 4-digit PIN code as long as no administrator is registered.

  3. Create the administrator account

    Open this address in your browser, enter the PIN, then link your Cfx.re account and choose a backup password. This first account is the “master” account: it has every permission and can invite the rest of the team.

  4. Deploy a recipe

    The setup wizard offers a popular recipe (CFX Default, ESX Legacy, QBCore…), a template from a URL or an existing server folder. For ESX or QBCore, first create a database in “Databases”, then enter its host, user, password and name when the deployer asks for them.

  5. Check the game port

    Before starting the server, open the recipe’s server.cfg in the txAdmin editor: the endpoint_add_tcp and endpoint_add_udp lines must use the primary port shown in “Network”. Replace 30120 if it is not your port.

  6. Start and check

    Start the server from txAdmin and wait for the Server license key authentication succeeded line in the live console. Then connect in game with the IP address and the primary port.

server.cfg lines to check

endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"
sv_hostname "My RP server"
sets sv_projectName "My RP server"
sets sv_projectDesc "Serious roleplay, whitelist open"
sets locale "fr-FR"
sets tags "roleplay, esx, serious"
sv_maxclients 48
load_server_icon logo.png

What txAdmin changes on ACLClouds

Without txAdmin, the startup command runs the server.cfg at the root of the server, and on every start the panel rewrites the name, the slot count, the license key and the endpoint lines in it from the “Startup” variables. With txAdmin, FXServer loads the recipe’s server.cfg, stored in the txData folder: you edit that file in the txAdmin editor or in “Files”.

The two tools work together: the panel keeps the console, the files, the backups and the startup variables; txAdmin adds recipes, scheduled restarts, the player list and moderation.

  • The txAdmin port is assigned automatically when the server is created and does not change.
  • txAdmin data (accounts, bans, settings) lives in the txData folder: keep it in your backups.
  • The current RedM template runs server.cfg directly, with no txAdmin option.

Update the FiveM artifacts

The artifacts are the FXServer server files, published by Cfx.re as numbered builds; txAdmin ships with them. The “fivem version” variable (FIVEM_VERSION) picks the installed version: recommended (the default), latest, or a specific build number taken from the Linux artifacts page.

The version only changes at install time: edit the variable, take a backup, then run “Settings” > “Reinstall Server”. The script downloads the new artifacts and keeps the existing server.cfg. A build number that cannot be found falls back to recommended.

  • Stay on recommended for a production server and test latest on a separate server.
  • After an update, read the console: an old resource may need a newer version of its framework.

Get the server into the FiveM server list

The FiveM server list shows servers with a valid license key that announce themselves to Cfx.re. Your server usually appears a few minutes after it starts. To be found, take care of the sets variables in server.cfg: project name, description, locale and tags feed the filters and the search.

  • sv_master1 "" removes the server from the list: delete or comment out this line for a public server.
  • load_server_icon logo.png shows a 96 × 96 pixel PNG icon placed next to server.cfg.
  • sv_endpointPrivacy true hides the server’s IP address in the list.

Which plan for a FiveM server?

As of 17 November 2026, three ACLClouds plans run FiveM: Dev (2.5 vCPU, 6 GB of RAM, 50 GB of storage, 1 database) at €2.49 a month incl. VAT with no commitment, City (4.5 vCPU, 10 GB of RAM, 80 GB, 2 databases) at €5.49 and Empire (7 vCPU, 16 GB of RAM, 120 GB, 3 databases) at €9.99, or €1.99, €4.39 and €7.99 a month on a one-year term. An ESX or QBCore recipe with a few dozen scripts fits on City; Dev suits testing and small groups.

Quick check

  • The console shows the txAdmin address with the port listed in “Network”.
  • The master account can sign in to txAdmin.
  • The endpoint lines of server.cfg use the primary port.
  • The server answers in game and shows up in the FiveM list.

Frequently asked questions

The txAdmin page does not open, what should I check?

Use the txAdmin port shown in the console and in “Network”, not the game port, with an http:// address rather than https://. Also check that TXADMIN_ENABLE is really 1 and that the server was restarted after the change.

I lost the PIN code, how do I get another one?

As long as no account has been created, txAdmin prints a PIN on every start: restart the server and read the console again.

I lost access to the master account, what can I do?

Stop the server, open “Files” and delete txData/admins.json, then restart: txAdmin assumes no administrator exists and prints a new PIN. Recipes, settings and bans stay in place; the other administrator accounts must be created again.

The server starts but nobody can connect, why?

A recipe’s server.cfg often listens on 30120. Replace this port with the primary port from “Network” in the endpoint_add_tcp and endpoint_add_udp lines, then restart from txAdmin.

Can I go back to starting without txAdmin?

Yes. Set TXADMIN_ENABLE back to 0: the server runs the server.cfg at the root again. Copy your ensure lines and settings into it if you changed them in the recipe’s file.