How do you configure a RedM server? The server.cfg file

An entire RedM server is steered from a single text file: server.cfg. A comma in the wrong spot, a misplaced ensure, a forgotten build, and the server stays silent. Rather than a dry list, let's see this file as a musical score: every line has to fall at the right moment.

The identity trio: license, build, port

• sv_licenseKey: your cfx.re key. Missing or invalid, nothing starts.
• set gamebuild: locks the expected RDR2 build; a mismatch stops your players from connecting.
• endpoint_add_udp / endpoint_add_tcp: the network listening, on port 30120 by default.

The public face

sv_hostname sets the name shown in the RedM server list, and sv_maxclients the number of slots. The latter must stay consistent with your CPU and your RAM: opening 64 slots on a small configuration is programming the lag.

The order of the ensures, the most sensitive point

This is where 90% of RedM configurations fail. The ensure lines are read top to bottom, so the dependencies come first: the MySQL connection, then oxmysql, then the VORP core, and only afterward the resources that depend on it. Swapping two lines is enough to crash the chain.

Permissions: the ace system

Admin rights go through the CitizenFX ace system (add_ace, add_principal) and the txAdmin roles. Hand them out sparingly: an admin principal granted too broadly is a direct hole in your RP.

Treat server.cfg like code: comment each block, keep the dependencies grouped at the top of the file, and never drop a VORP ensure below oxmysql. A readable file means a server you fix in two minutes.

Editing it without touching it by hand

On a Fly-Serv RedM server, FlyPanel and txAdmin open server.cfg in a clear editor and restart with one click, no FTP. Make sure you've properly followed the RedM installation beforehand, continue with adding scripts, or start a new server from 1,99 €/month.