4 min read
Install QBCore on Linux with txAdmin
Use a dedicated service account, a separate test profile, and an empty database. The QBCore txAdmin recipe supplies the resource list and schema; this page explains the host-side checkpoints.
What was checked
The recipe source was reviewed at commit 0f4f6d96bf707ef9de123afd59a4233504befab1. The commands and checkpoints below have not been executed on a FiveM host for this guide. Check artifact and distribution requirements before deployment, including differences between GTA V Legacy and Enhanced.
Conceptual diagram; verify the behavior against your installed resource version.
Before you begin
Have a Cfx.re server license key, SSH access, a running MySQL or MariaDB service, and the tools required to extract the selected artifact. The Cfx.re Linux instructions describe the artifact layout. This guide uses txAdmin instead of their manual server.cfg launch path.
Create a dedicated account
Create a service account using your distribution's account-management tools. Run the following commands as that account, not root. Keep binaries, profile data, and backups separate; grant write access only where required.
mkdir -p ~/FXServer/server
cd ~/FXServer/serverCheckpoint: the service account can write to this new directory, and it is not an existing production profile.
Install a current server artifact
Download the recommended Linux artifact from the Cfx.re artifacts service into that directory. Record the artifact build number rather than copying a stale hardcoded download URL.
For the fx.tar.xz artifact layout, extract the full archive and start txAdmin:
tar xf fx.tar.xz
bash ./run.shUse the actual archive name from the download. Start without +exec server.cfg during initial txAdmin setup. Open the URL printed in the terminal, complete account linking, and set an administrator password. For a remote host, use an access-controlled administration path rather than exposing the panel broadly. Keep the process running during setup.
Checkpoint: txAdmin opens and lets you create a test profile. Record the profile's data directory; do not assume it is the binaries directory.
Prepare an isolated database
Create an empty database such as qbcore_test and an application account such as qbcore_app with access scoped to that database. Keep the database on a private interface or loopback when it shares the host. txAdmin does not install the database service.
Test the account using the same connection settings that the deployer will use. Where the MariaDB command-line client is installed, this example prompts for the password instead of putting it in shell history:
mariadb --host=127.0.0.1 --user=qbcore_app --password qbcore_testUse your actual host, account, port, and database. Select the existing test database in txAdmin's database options; the account must be able to import the schema there. Do not broaden grants to all databases to bypass an access error.
Checkpoint: the application account connects to the selected empty database. Keep passwords and the generated connection string out of Git, screenshots, and shared logs.
Deploy through txAdmin
Select QBCore from the available recipes and verify the repository is qbcore-fivem/txAdminRecipe. Review the YAML and enter your Cfx.re license key and database options when prompted.
The reviewed recipe installs resources including oxmysql and imports qbcore.sql. Let those tasks finish successfully; do not rerun a fresh-install recipe over production data or import an invented qb-core/server/database.sql path.
Review the generated server.cfg in the profile's data directory. Verify endpoints and the private database setting, preserve the initial resource start order, then save and run the server.
Checkpoint: the recipe reports no failed tasks and the game-server console has no unresolved SQL or dependency errors.
Verify and supervise
Connect from FiveM on your gaming machine using the server's reachable address and configured game port. 127.0.0.1 on the gaming machine does not refer to a remote Linux server.
Create a test character, disconnect, reconnect, and verify persistence. Restart the profile through txAdmin and check again. Complete the first-boot checklist before customizing resources.
Only after manual startup works, configure your service manager with the verified startup command, explicit working directory, service account, restart policy, and log destination. Test stop and restart behavior before enabling it at boot.
Linux checks
Expose only the configured game ports needed by players. Keep database and administration access restricted. Back up the database and server files separately, test a restore on staging, and monitor disk space and restart loops.
sv_enforceGameBuild selects the clients' GTA game build; it does not pin the FXServer artifact. See the artifact/build explanation.
If a checkpoint fails
| Symptom | Check next |
|---|---|
| Archive extraction or startup fails | Check the artifact filename, complete extraction, distribution requirements, permissions, and terminal error. |
| txAdmin opens but the game does not | Check the selected profile and first game-server console error. The panel running alone is not a successful game-server boot. |
| Database access denied | Test the exact account/host/database combination and database-scoped grants. Keep the database private. |
| Table, resource, or export missing | Inspect the failed recipe task, selected database, and resource start order. |
| Remote player cannot connect | Check the game endpoint and relevant firewall/provider rules with connection troubleshooting. |
Do not copy an unreviewed systemd unit
Paths and startup requirements vary by host. Do not run a second game-server process alongside txAdmin's managed process or replace a working service definition without testing on a separate profile.
Sources and next steps
Source references: Cfx.re Linux artifact setup, txAdmin startup behavior, and the reviewed QBCore recipe. Some recipe dependencies follow moving branches; record the installed resource versions as well.
Next: first-boot checks → resource documentation → safe update workflow.
Found an issue in this guide?
Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.
