Manual Installation (without txAdmin)

Prepare the server buildCopy Anchor Link

Download the latest server build for your OS from runtime.fivem.net and extract it into its own folder, for example C:\FXServer\server or /opt/fxserver/server. ESX Legacy refuses player connections on builds older than 10188, so do not use an old build.

Create a separate data folder next to it, for example C:\FXServer\esx-server. Your server.cfg and resources folder go there.

Create the databaseCopy Anchor Link

Create an empty database with the utf8mb4 character set. In HeidiSQL, DBeaver or the MariaDB console:

CREATE DATABASE `es_extended` CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

-- Optional but recommended: a dedicated user instead of root
CREATE USER 'esx'@'localhost' IDENTIFIED BY 'change-me';
GRANT ALL PRIVILEGES ON `es_extended`.* TO 'esx'@'localhost';
FLUSH PRIVILEGES;

legacy.sql does not contain a CREATE DATABASE statement. You must create the database first and import the file into it.

Download ESXCopy Anchor Link

Download these repositories (use the latest release, or the main branch if you know what you are doing):

The recipe also adds ox_lib, pma-voice (voice chat), bob74_ipl (interiors), sd-phone and sd-phone-props. They are not required by es_extended, but you probably want voice and interiors on a roleplay server.

Import legacy.sqlCopy Anchor Link

Import [SQL]/legacy.sql into the database you created. In HeidiSQL: select the database, then File > Run SQL file. From the command line:

mysql -u esx -p es_extended < "legacy.sql"

The file creates the core tables (users, items, jobs, job_grades, licenses, owned_vehicles and more) and the tables used by the official addons (addon_account, billing, datastore, vehicles, banking and others).

Copy the resourcesCopy Anchor Link

Put the folders into resources. Folder names in square brackets are categories: FiveM searches inside them, and you can start a whole category with ensure [name].

Check that each resource folder directly contains its fxmanifest.lua. A common mistake is a double folder like oxmysql/oxmysql/fxmanifest.lua after extracting a zip, or a version suffix like es_extended-main. The folder name is the resource name, so es_extended must be called exactly that.

Write server.cfgCopy Anchor Link

Start from the server.cfg that ships in esx_core. The important part is the order at the end:

set onesync on
set mysql_connection_string "mysql://esx:change-me@localhost:3306/es_extended?charset=utf8mb4"

## Default resources
ensure chat
ensure spawnmanager
ensure hardcap

## Database driver and library first
ensure oxmysql
ensure esx_lib

## ESX core
ensure es_extended
ensure [core]

## Standalone resources and addons
ensure [standalone]
ensure [esx_addons]

oxmysql lives inside [standalone], so ensure [standalone] lists it a second time. The official recipe uses the same layout. The explicit ensure oxmysql line is what guarantees it starts before es_extended, so keep oxmysql and esx_lib above es_extended as shown.

Add your license key (sv_licenseKey), endpoints and the admin ACEs. The full file is explained in server.cfg for ESX.

Start the serverCopy Anchor Link

From the data folder, start the build and point it at your config:

# Windows (run from C:\FXServer\esx-server)
C:\FXServer\server\FXServer.exe +exec server.cfg

# Linux (run from /opt/fxserver/esx-server)
bash /opt/fxserver/server/run.sh +exec server.cfg

On the first start you should see oxmysql connect to your database, then es_extended run its migrations. If it prints Server restart required!, stop and start the server once.