Create a RedM server with FXServer and txAdmin using a RedM-compatible recipe, then verify a RedM client can join before adding gameplay resources. FiveM and RedM share server tooling, but GTA V resources and game-build values are not interchangeable with Red Dead Redemption 2.
Prepare the host and accounts
Use a host supported by the chosen FXServer/RedM framework release, enough storage for its resources and database, and control over the assigned TCP/UDP game endpoint. Players need the game/client required by the official RedM site.
Create a Cfx.re account and obtain the required server registration through Cfx.re Portal. Keep keys and setup PINs private. Preserve access to the host while changing network settings; expose txAdmin only through your intended protected administration path.
Install FXServer and start txAdmin
Download the server files through the official txAdmin setup guide for your operating system. Keep server runtime files separate from persistent server data.
On Windows, launch the extracted FXServer.exe according to that guide. On Linux, use the supplied run.sh from the extracted runtime directory. Follow the printed txAdmin setup address/PIN and link your account. Do not add a manual +exec argument when the intended startup is txAdmin’s setup mode.
Choose a RedM recipe
Select a recipe documented by the actual RedM framework you intend to use, or follow its official installation instructions. Check the recipe source and its current dependencies before allowing it to download or import data.
Verify that the generated startup configuration selects RedM with gamename set to rdr3, rather than a GTA V server. Keep the recipe’s documented startup placement. Do not paste a FiveM configuration or an arbitrary GTA game-build number over it.
Configure persistence and networking
Choose a persistent server-data directory and record its active configuration path. If the framework needs MariaDB/MySQL, create a separate database and user with the required permissions; keep the database off the public game endpoint.
Set the game port assigned by your host and permit the required TCP/UDP access through its network. Use the valid license privately in the generated configuration. Select player capacity from current entitlement and measured workload, not a generic number from a guide.
Test before adding resources
- Start the server and resolve the first dependency, configuration or database errors.
- Connect with the RedM client from outside the host network.
- Create a test character if the framework provides characters, then spawn and complete one basic action.
- Reconnect and restart the server. Verify character and inventory persistence where applicable.
- Test an ordinary player account against administrative actions; confirm denial.
Add one resource at a time
Read its RedM/framework/version requirements and license. Put the complete resource in the persistent resources directory, preserve its manifest and ensure dependencies start first. Apply documented database changes on a test copy with a backup.
Do not assume FiveM maps, scripts, natives or clothing files work in RedM. Test the exact interaction, its failure cases and saved state before adding the next resource.
Operate a recoverable server
Back up the runtime version record, txAdmin profile, configuration, resources and database as a matching set. Rehearse restoring to a separate instance. During updates, preserve a working release and check public connection, gameplay, permissions and persistence before reopening normal play.
For a concrete framework recipe, follow VORP Core’s official txAdmin installation. It documents the Remote URL Template and database setup steps.