Skip to main content
Most FiveM frameworks (ESX, QBCore, QBox, ND) need a MariaDB database. On Lumix Solutions, that’s a one-click provision in the Databases tab.

​
1. Create the database

In Lumi-Panel:
  1. Open Databases.
  2. Click New Database, give it a name like fivem, leave connection from as %.
  3. Save the Endpoint, Username, and Password - you’ll need them next.
You can also manage it through phpMyAdmin at db.lumixsolutions.org using the same credentials.

​
2. Import your framework’s schema

Sign in to db.lumixsolutions.org, select your database in the left sidebar, click Import, and upload your framework’s .sql file (e.g. ESX’s legacy.sql, QBCore’s qb-core.sql).

​
3. Configure the connection string

In server.cfg:
Replace USERNAME, PASSWORD, HOST, PORT, and DATABASE with the values from the Databases tab.

​
mysql-async (legacy)

​
Configuring the database in txAdmin

When you run through txAdmin’s setup wizard (or change the database later under Settings → Server), it asks for the database host, port, username, password, and database name separately.
Use the Endpoint from the Databases tab - not your server’s game IP. Your FiveM server and the database run on different IPs. Typing your server’s IP here will fail to connect every time.
The Lumi-Panel Endpoint looks like DB_HOST:DB_PORT (for example db.example.lumixsolutions.org:3306). Split it into the two fields txAdmin asks for: If you’d rather paste a single string, the JDBC connection string field in Lumi-Panel already has every value baked in:
Use that as a reference - the values between the symbols are exactly what each txAdmin field wants.

​
4. Restart

Restart the server from the Console. On boot you should see something like:
If you see ECONNREFUSED, Access denied, or Unknown database, walk through Startup Issues → Database connection refused.

​
Best practices

  • Never commit credentials. Keep server.cfg out of public repos, or use a separate secrets.cfg that’s gitignored.
  • Rotate the password from the Databases tab if you suspect a leak - then update server.cfg and restart.
  • Back up before big changes. Use phpMyAdmin’s Export or trigger a panel-wide Backup before running schema migrations.