Decide what the first test should prove

Use a private test with two or three teammates to answer a short list of questions. Can everyone connect using the intended GTA V edition? Are voice and spawning usable? Can a moderator find the community’s reports, and can the designated operator restart the server? Keep the test scope small enough that you can repeat it after a configuration change. Save your initial configuration separately so that a failed experiment has a known recovery point.

Install the recommended server build

Download Cfx.re’s recommended server build for the edition you want to test. On Windows, start FXServer.exe for Legacy or cfx-server.exe for Enhanced. For Enhanced, check the Visual C++ prerequisite listed by Cfx.re before the first start.

Deploy the default recipe

These steps cover a Windows test server. Open the local txAdmin page shown in the FXServer console and enter the first-run PIN from that console. Link your Cfx.re account and set a backup password. In Popular Recipes, choose the CFX Default FiveM template, check the data location and open Recipe Deployer. Use the registration key from the official Cfx.re Portal, run the recipe and select Save and Run Server once deployment finishes.

Keep the backup password and the registration key in private storage. Read the startup console before adding resources. Other recipes can require a separate database.

Run a rehearsal before opening applications

First join from the matching FiveM client on the same machine or trusted LAN. If you later allow testers to join from elsewhere, configure and check the player allowlist first. Keep the txAdmin panel accessible only to authorized operators.

With your invited team, check voice, a reconnect and a restart by the operator who holds that permission. Record which changes were active during the test and which problems persisted after restart. Add custom resources one at a time and repeat the same rehearsal. Decide who can edit settings, who handles reports and where those reports go. Review the platform guidance and resource permissions before making the server public.

Record a usable rollback test

Write down the server build, the recipe, which resources were active and what worked before the change. Ask a second teammate to join after you restore the saved configuration. If a custom script depends on a database, keep the matching data backup and configuration together and test the restoration on the private instance. For permissions, give the moderator only the tools needed for reports and routine actions, using the official txAdmin permissions reference. Record who is allowed to restore or change resources before granting access.