Setting up a FiveM server is not as complicated as it used to be. txAdmin is now bundled directly with FiveM server builds, and it walks you through most of the setup automatically. This guide covers the full process from scratch.
Note: Keymaster has been replaced by the Cfx.re Portal as of December 2025. License keys are now generated and managed exclusively through portal.cfx.re.
If you want the fastest path to a running server, a hosting provider is the easiest option. Most FiveM-compatible providers come with FiveM pre-installed and txAdmin pre-configured. The official list of approved providers can be found at docs.fivem.net.
After ordering, you typically get access to txAdmin through the hosting panel. Log in, link your Cfx.re account, paste your license key, and the server is ready to configure.
The tradeoff is monthly cost and less control over the underlying machine.
This option gives full control over the server environment. It takes a bit more setup but is not difficult.
Go to the FiveM artifacts page:
Download the latest recommended build. Extract the contents to a folder, for example C:\FXServer\server on Windows.
On Windows, double-click FXServer.exe. On Linux, run the appropriate start script.
When the server starts for the first time, it opens txAdmin automatically in your browser at http://localhost:40120.
txAdmin will show a PIN and prompt you to link your Cfx.re account. Click Link Account, log in at the Cfx.re portal, and authorize the connection.
Set a password for the txAdmin admin account. This is separate from your Cfx.re account password and is specific to this server.
txAdmin will walk you through the initial setup wizard:
After filling in the details, click Run Recipe. txAdmin will download and configure everything automatically.
Review the server.cfg file txAdmin generates. If everything looks correct, click Save and Run Server.
The server will start. Players can connect via direct connect using the server's public IP and port 30120.
For the server to be visible outside the local network, forward these ports to the server's local IP:
| Port | Protocol | Purpose |
|---|---|---|
| 30120 | TCP + UDP | Main game connection port |
| 30110 | UDP | Optional (peer-to-peer voice) |
If the server does not appear in the server list after starting, port forwarding is usually the cause.
Most RP servers run on a framework. Here is a quick overview:
Framework choice is mostly preference and depends on what scripts are planned for the server.
Once the server is up, the next steps are:
resources/ and registering them in server.cfg with ensure script-nameserver.png in the root server folder| Issue | Likely Cause |
|---|---|
| Server does not appear in browser | Port 30120 not forwarded, or firewall blocking it |
| txAdmin not loading in browser | FXServer did not start correctly, check console output |
| License key rejected | Key not generated from Portal, or already in use on another server |
| Recipe fails during setup | Network issue or missing permissions on the install path |