How to Set Up a FiveM Server with txAdmin

Set up a FiveM server by installing the recommended FXServer artifact for your operating system, launching its bundled txAdmin, completing the setup wizard and testing a base recipe before adding resources. txAdmin is included with FXServer; a separate third-party admin download is unnecessary. Keep game traffic and administration access configured separately.

Before you begin

The procedure below follows Cfx.re’s Windows setup path for a GTA V Legacy server. Use the matching official instructions for Linux or GTA V Enhanced; current Enhanced downloads and executable names differ. On a managed game panel, use its supported deployment workflow rather than replacing its process supervisor with a second installation.

You need a Cfx.re account and server registration/license details from the official portal, permission to run the server, a writable installation location and a way to control inbound network access. Keep registration secrets out of screenshots, public repositories and support posts. Record the selected artifact build and installation date.

1. Install and launch the official artifact

Create a dedicated directory such as C:\FXServer\server for the binaries. Keep unrelated personal files out of it.
Use the Windows artifact link in the official setup guide and choose its recommended build. Extract the complete archive; do not copy only the executable.
Run FXServer.exe using the txAdmin setup workflow, without a legacy +exec startup command. Follow the local setup URL and PIN shown in its output.
Complete account linking and create strong administrator credentials. Save recovery information securely before continuing.

The documented default txAdmin web port is TCP 40120. A localhost URL on the server refers to that server, not your own laptop. Prefer local access, a private network or a securely authenticated tunnel; do not expose the admin port to everyone simply to make the setup screen reachable.

2. Deploy a small known starting point

In the wizard, name the server and choose a recipe. For a connectivity baseline, the CFX Default recipe keeps the first test simpler than a large framework stack. Review the recipe and its downloads before running it. Complete the requested registration settings, deploy and inspect the resulting server configuration.

Record the actual profile directory, server-data directory, server.cfg and txData location. These are different from the artifact binaries. A framework recipe may introduce a database and credentials; include those in the inventory rather than assuming txAdmin stores every part of the service.

3. Check game and admin access separately

Common defaults; use your actual assigned ports
Purpose	Documented default	Access policy
FiveM game endpoints	TCP and UDP 30120	Permit player traffic to the selected game allocation.
txAdmin web interface	TCP 40120	Restrict to trusted administration paths.
Database, when required	Depends on the database configuration	Keep private to the services that need it.

Verify the endpoint entries in server.cfg and both the host and provider firewall. A successful TCP check does not prove UDP is allowed. Port forwarding may also be required behind NAT. Do not change a provider-assigned bind address to a public address that is not actually present on the machine.

4. Verify before installing a framework

Start through the intended supervisor and inspect the console for registration, resource or port-binding errors.
From a permitted external player network, open the FiveM F8 console and connect to the actual public address and game port.
Confirm a player can join and that the base resources start. Direct connection is a clearer initial check than waiting for a server-list entry.
Perform a clean stop/start and repeat the connection test. Record the artifact, recipe and configuration that passed.
Back up this baseline before adding a framework, resources or database migrations.

# FiveM client F8 console; replace the example address and port
connect YOUR_SERVER_IP:30120

If the first connection fails

An unreachable admin page and an unreachable game endpoint are separate failures. Check the process and listener first, then address/port allocation and network rules. For a registration error, inspect the exact console message and official portal configuration. For a resource failure, preserve the first error rather than reinstalling the entire server.

Next, follow resource installation and troubleshooting and set up file and database recovery. Compare FiveM hosting options once you know the framework, access and administration requirements. This procedure is documentation-checked; it is not a report of an EnderHost runtime test.