txAdmin is bundled with FXServer, so you do not download it as a separate RedM resource. Download and extract a current FXServer artifact on a supported Windows or Linux machine, launch it once without +exec server.cfg, then open the panel URL and enter the one-time setup PIN printed in the console. Link the owner’s Cfx.re account, create the txAdmin master account, and either deploy a RedM recipe into an empty directory or attach an existing server-data folder.
What txAdmin does on a RedM server
txAdmin is the administration layer that starts and monitors FXServer and gives you a browser panel for player management, permissions, scheduled restarts, logs, console commands and operational controls. It is part of the FXServer distribution. The official txAdmin documentation states: “You do not install txAdmin as a separate resource: it is already included with FXServer.” Downloading a second resource or placing a txAdmin folder in resources is unnecessary and can create confusing, unsupported installations.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
RedM is the game target, while FXServer is the runtime and txAdmin is its management interface. A working panel alone does not make a server a RedM server: the selected recipe, server.cfg, resources and enforced game build must all target Red Dead Redemption 2. Treat the panel, game configuration and networking as related but separate layers.
What you need before starting
- A supported Windows or Linux host with terminal access or a provider control panel that can start FXServer.
- A Cfx.re account for the server owner. The account used during setup becomes the txAdmin master account.
- A server registration key from the Cfx.re Portal.
- A writable directory for the FXServer artifact and, for an existing installation, the server-data and txData directories.
- Database connection details if the RedM framework or recipe you choose stores data in a database.
- Permission to open or forward the panel and game ports through the host firewall, unless a managed provider controls them.
Have the registration key and database passwords available, but do not paste them into public chat, screenshots or shared configuration examples. Keep a separate record of the owner backup password created during txAdmin setup.
#1 Best Overall
Choose your deployment path first
txAdmin offers two fundamentally different setup flows. Pick the one that matches your situation before you click through the wizard.
| Situation | txAdmin choice | Directory and configuration expectation | Main risk |
|---|---|---|---|
| Brand-new RedM server | Deploy a recommended RedM-compatible recipe | Use an empty destination directory; the recipe creates resources and configuration | A recipe may install framework resources, database tasks or assumptions you have not reviewed |
| Existing RedM server | Attach an existing server | Select the current server-data directory and its configuration file | Pointing at the wrong folder can start a partial or unrelated installation |
| Self-hosted Windows | Run FXServer.exe |
Start from the extracted artifact directory | Firewall rules, file permissions and accidental shortcuts to another directory |
| Self-hosted Linux | Run ./run.sh |
Start from the extracted artifact directory with executable permissions | Missing execute permission, service-user ownership or blocked ports |
| Managed hosting | Use the provider’s startup controls and supplied txAdmin URL | Provider may preconfigure the artifact, ports and data path | Port numbers, restart behavior and filesystem access may differ from self-hosting |
For a new deployment, use a recipe whose source identifies RedM and inspect its tasks before accepting it. For a running server, attach the existing data instead of deploying a recipe over production files.
Recommended Free Tools
Install FXServer and launch txAdmin
1. Download and extract the artifact
Obtain a current recommended FXServer artifact from the Cfx.re server-setup resources. Extract it to a dedicated, writable directory rather than a temporary download folder. Keep the artifact files together; txAdmin is loaded from this FXServer installation. On Linux, ensure the account that will run the service can read and execute the files. On Windows, avoid directories where security policy prevents the server process from writing its data.
2. Start the runtime without a configuration file
The first launch must allow txAdmin to create its setup flow. Do not append +exec server.cfg on this initial start.
- On Windows, open a terminal in the extracted artifact directory and run
FXServer.exe, or start that executable from your approved startup control. - On Linux, open a shell in the same directory and run
./run.sh. If the shell reports a permission error, grant execute permission to the launcher and verify ownership before trying again. - Watch the console output. txAdmin prints a browser URL and a one-time setup PIN. Leave this process running while completing the browser setup.
Launching with +exec server.cfg too early can bypass the intended first-run flow, leaving you without the setup prompt. Add your normal configuration through the selected deployment path after the panel is initialized.
Rank #2
- Included: 1TB SSD Console, Red Dead Redemption 2, 1 x DualShock-4 Wireless Controller
- PS4 Pro Outputs Gameplay to Your 4K TV. Many Games, Like Red Dead Redemption 2, Are Optimized To Look Stunningly Sharp and Detailed When Played On A 4K TV with PS4 Pro
- Turn On Boost Mode To Give PS4 Games Access To The Increased Power Of PS4 Pro. For HD TV Enhanced Games, Players Can Benefit From Increased Image Clarity, Faster Frame Rates, And Other Enhancements
- With An HDR TV, Compatible PS4 Games Display an Unbelievably Vibrant and Lifelike Range Of Colors
- PS4 Pro Enables Game Resolution Output at Native 2160p Resolution, Stream 4K Videos, Movies, and Shows to Your PS4 Pro.
3. Open the panel
The default txAdmin panel port is TCP 40120. On the same machine, the default address is http://localhost:40120. Prefer the exact URL printed by your console because a provider, prior installation or environment setting may use another interface or port. If you connect from another computer, replace localhost with the host address only after the firewall permits the connection; do not expose the panel broadly when a restricted management network or VPN is available.
4. Complete account linking
- Enter the one-time PIN shown in the FXServer console.
- Sign in to the server owner’s Cfx.re account when prompted and approve the account link.
- Create the txAdmin master account and a strong backup password. Store that password in a password manager and do not share the owner login with staff.
- After the panel confirms setup, create individual staff accounts with only the permissions each person needs.
The PIN is a bootstrap credential, not a permanent administrator password. Treat it as private while it is displayed and invalidate or replace any exposed credentials before putting the server online.
Deploy a new RedM server with a recipe
1. Select a RedM-compatible recipe
In the txAdmin deployment wizard, choose the new-server option and select a recommended recipe that explicitly targets RedM. A recipe is a YAML task document: it can download resources, write configuration, create folders and execute database-related tasks. The wizard’s label alone is not a security or compatibility guarantee, so inspect the recipe source and task list before running it.
2. Check recipe assumptions
- Confirm that the recipe is intended for RedM rather than a FiveM-only deployment.
- Read every download, file-write and command task, including scripts fetched from external repositories.
- Check which FXServer artifact or game build the recipe expects.
- Identify whether it creates a database, imports a schema or expects an already-created database user.
- Confirm framework dependencies and the order in which resources are started.
- Verify that the destination is empty. Do not let a new recipe overwrite a production server-data directory.
3. Supply registration and database details
Enter the server registration key in the appropriate configuration step and use database credentials with only the privileges the framework requires. A recipe that needs a database can fail after downloading files if the host, port, username, password or schema is wrong. Keep those values out of screenshots and public repositories.
4. Deploy and inspect the generated files
Run the deployment only after you have a backup plan and understand its tasks. When it completes, open the generated server.cfg and any included configuration files. Check the endpoint declarations, resource names, dependency order, registration key placement, database settings and secrets. Start the server through txAdmin and read the console from the first line rather than assuming a green deployment message means every resource loaded correctly.
Rank #3
- Printed on Highest Quality Poster Paper.
- Poster measures 16" x 24" inches
Attach an existing RedM server
1. Back up before selecting the folder
Stop the existing server and copy both the complete server-data directory and the txAdmin data directory, commonly referred to as txData. Keep the copies outside the live installation. This gives you a rollback if txAdmin changes a path, a recipe is accidentally applied or a configuration edit prevents startup.
2. Point txAdmin at the real server-data directory
Choose the existing-server option in the wizard. Select the directory that contains your resources and configuration, then identify the correct server.cfg (or the configuration file that your startup process actually uses). Do not select the parent directory merely because it has a similar name. Confirm that the folder contains the resources expected by your current RedM deployment.
3. Review, then start
Inspect the path and configuration summary before saving. Verify endpoints, resource paths, dependencies and secrets. Start the attached server from txAdmin and compare its console output with the behavior of the previous startup method. If resources fail, stop the server and restore the backed-up server-data and txData directories before investigating further.
Make the configuration RedM-specific
Identify the game target
Where the setup environment exposes a game selector, choose RedM. The corresponding environment value is TXHOST_GAME_NAME=redm. A RedM-specific configuration guide also identifies set gamename rdr3 and an enforced RDR2 build in server.cfg. Check the current recipe and generated configuration for those settings instead of copying an old example unchanged; recipes and supported builds can change.
Keep game settings in server.cfg
Put resources, game rules, endpoints, framework settings and other runtime directives in server.cfg or files included by it. txAdmin’s web pages are for administration and operations, not a replacement for the game configuration. If you change a resource start line in the panel but the configuration later overwrites it, the file remains the authoritative place to correct the problem.
Rank #4
Keep administration settings in txAdmin
Use txAdmin settings for staff accounts, permissions, moderation actions, schedules, restart policies and operational controls. Create named staff accounts rather than handing out the master credentials. Review permissions after adding or removing a moderator, and remove stale accounts promptly.
Understand ports and host networking
| Purpose | Typical value | Protocol | What to verify |
|---|---|---|---|
| txAdmin browser panel | 40120 by default |
TCP | The URL printed at startup, firewall allowance and the interface on which the panel listens |
| RedM game endpoint | 30120 is typical |
TCP and UDP | Generated server.cfg, provider allocation, NAT/forwarding and firewall rules |
Port 30120 is a common game endpoint, not a promise that every host uses it. Managed hosts may allocate another port or place the server behind their own proxy. Use the endpoint shown in the generated configuration and provider dashboard. Opening only TCP can allow some control traffic while preventing players from connecting over UDP, so configure both protocols when the host requires it.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsThe panel port and game endpoint are independent. A browser that reaches 40120 does not prove that players can reach the game endpoint, and a reachable game endpoint does not prove that txAdmin is safely accessible. Test each path separately from an appropriate network.
Set host options at the correct configuration layer
Panel port, listening interface, txAdmin data path and related host behavior are set before FXServer starts. Use the TXHOST_* environment variables in the service definition, startup script or provider control panel. Setting those values inside server.cfg is too late because txAdmin has already initialized by then.
txAdmin version 8 documentation marks older ConVars named txAdminPort, txAdminInterface and txDataPath as deprecated. If an older installation still uses them, migrate to the current host-variable approach supported by your artifact and remove conflicting definitions after testing. Do not set both old and new forms to different values; that makes it difficult to tell which port or data path is active.
Apply a host-variable change safely
- Stop FXServer through txAdmin or the host service manager.
- Back up txData and record the current startup command, environment and working directory.
- Set the required
TXHOST_*value in the process environment, not inserver.cfg. - Start FXServer from the artifact directory and read the printed URL and data-path messages.
- Open the new panel address locally first, then test remote access through the intended firewall rules.
Review recipes before trusting them with production data
A recipe can be convenient, but it is executable automation. Review its source URL and every task before deployment. Pay particular attention to commands that download code, delete files, replace configuration or alter a database. A task that is harmless in an empty test directory can destroy a live resource set when run against production.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Clone or copy production files and databases before testing a recipe.
- Run the recipe in an isolated, empty directory first when its compatibility is uncertain.
- Compare the resulting resource list and configuration with the expected RedM framework requirements.
- Check external repository availability and rate limits before scheduling an unattended deployment.
- Record the artifact version, recipe revision and database schema version used for a successful deployment.
If a task fails, txAdmin’s first failed task is usually the most useful starting point. Later failures may be cascading symptoms rather than separate defects.
Security and backup practices
Protect credentials
- Keep the setup PIN, Cfx.re account session, server registration key, database password and txAdmin backup password private.
- Use individual staff accounts and least-privilege permissions; never share the master account.
- Restrict panel access by firewall, private network or VPN where possible instead of exposing TCP
40120to the entire internet. - Rotate a credential immediately if it appears in a log, screenshot, paste or public repository.
Back up both data areas
The server-data directory contains resources and game configuration, while txData contains txAdmin’s operational data. Back up both before changing recipes, moving hosts, altering environment variables or upgrading an installation. Include the database used by the framework in the same recovery plan; a file backup without a matching database backup can leave player data inconsistent.
Test restoration
A backup is useful only if it can be restored. Periodically stop a non-production copy, restore server-data, txData and the database, then start it with the recorded artifact and environment. Document the exact order so a future outage does not depend on one person remembering undocumented steps.
Troubleshoot common setup failures
The panel does not load
- Confirm FXServer is still running and that the console printed a URL without a fatal startup error.
- Try the local address and port shown by the console rather than assuming
http://localhost:40120. - Check the host firewall, cloud security rules and provider network policy for TCP access to the configured panel port.
- Verify that FXServer started from the extracted artifact directory and is using the intended environment variables.
- If the panel is bound only to a local interface, connect from the host itself or change the interface using the supported host setting, then restart.
The PIN is missing or no longer works
Stop the process, verify that you launched the current artifact without +exec server.cfg, and start it again from the correct directory. Read the newly printed PIN rather than reusing an old console line. If the installation was previously initialized, use the existing txAdmin account recovery path and protect the txData backup; do not delete txData simply to force a new setup without a recovery copy.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The game endpoint is unreachable
- Read the endpoint in
server.cfgand compare it with the provider-assigned port. - Allow both TCP and UDP for the configured game port when required by the host.
- Check NAT or port-forwarding rules for a self-hosted machine.
- Confirm that the server is listening on the intended interface and that no second process is using the port.
- Ask a player outside the host network to test; a local connection can succeed even when external forwarding is broken.
A recipe fails partway through
Open the deployment log and inspect the first failed task. Unavailable repositories, transient network errors, repository rate limits, invalid database credentials and insufficient filesystem permissions are common causes. Correct the underlying condition, restore the pre-deployment backup if files were modified, and rerun only after confirming whether the recipe is safe to resume. If the task made partial database changes, restore or reconcile the database before another attempt.
Resources fail after attachment
Check that txAdmin points to the same server-data folder and configuration file used by the previous startup command. Then inspect resource names, dependency order, missing artifacts and RedM game settings such as set gamename rdr3. Compare the attached configuration with the backup rather than guessing at individual lines.
Operate the server after setup
- Start the server from txAdmin and watch the console until the expected resources load without fatal errors.
- Connect with a test client and verify player joining, resource behavior, database writes and administrative actions.
- Create staff accounts and test each permission level with a non-owner account.
- Configure scheduled restarts only after confirming that the server and database shut down cleanly.
- Record the artifact version, recipe or existing-server path, panel port, game endpoint and backup locations.
- Schedule updates during a maintenance window, back up server-data, txData and the database first, and keep a rollback copy of the last working artifact.
For a managed host, also record which settings the provider controls: artifact updates, startup arguments, allocated ports, firewall rules, backups and access to txData. Ask the provider for its RedM-specific endpoint and txAdmin URL rather than assuming self-hosted defaults.
Quick Recap
Final pre-launch checklist
- FXServer starts from the intended artifact directory and txAdmin opens at the printed URL.
- The owner’s Cfx.re account is linked, the backup password is stored securely and no staff member uses the master login.
- The selected recipe was reviewed, or the existing server-data path was verified, with no unapproved production overwrite.
- RedM targeting is explicit, including the current
rdr3game setting and compatible enforced build where required. - The panel port and game endpoint are documented separately; firewall and provider rules match the actual values.
- Resources, dependencies, registration key and database settings are correct and secrets are private.
- Backups of server-data, txData and the framework database exist and a restoration procedure is documented.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
