Your RedM setup needs two working connections: txAdmin for administration and the RedM client for gameplay. A reachable administration page does not yet prove that the game server is running. Complete a simple base installation and test joining before adding a framework or custom resources.
Prepare before ordering
You need an up-to-date, legitimately purchased PC copy of Red Dead Redemption 2 and the client from redm.net. Create an account at Cfx.re too. Under Registration Keys, generate a registration key for your server.
Keep the key private. Remove it when copying console output into a support ticket later. Review the offered SupremeTier configuration and price when ordering, then enter the key in the provided field. Your intended player count is also subject to Cfx.re's current licensing requirements; an available slot selection does not replace them.
Open administration through the additional port
After provisioning, find the additional port under Players & Access → Ports in the panel. The other important entry is Game (connection). Keep the two separate:
| Connection | Address to use |
|---|---|
| txAdmin in a browser | IP address and additional port, as shown in startup output |
| RedM client | Address and port from Game (connection) |
The server console lists the administration address at All ready! Please access:. It also shows the PIN for initial registration. Use the actual address and protocol it provides. For a direct HTTP connection, the address could look like http://203.0.113.10:30124/. Replace all these example values with your panel details.
If the page does not load, compare its port and protocol with the console first. A running panel status at this stage can refer only to the txAdmin process.
Complete txAdmin through the game launch
- Enter the console PIN and choose Link Account. Sign in to Cfx.re and confirm the link.
- Set a separate administration password. Do not reuse one from another service, especially over a direct HTTP connection.
- Name the server. Under Popular Recipes, choose a simple RedM recipe. Before using a framework recipe, check its requirements, such as a database.
- Accept the suggested target directory under
txDataand open the Recipe Deployer. - Check the registration key before Run Recipe. The order value provides a suggestion; enter it if the field is empty.
- Wait for deployment to finish and complete Next, followed by Save & Run Server.
The system supplies the game port and purchased slot limit. Do not try to bypass that limit by entering different configuration values.
Next, open Live Console. Server license key authentication succeeded. Welcome! confirms successful key validation. If it fails, inspect sv_licenseKey in the server.cfg actually in use, available through CFG Editor. Changing the key field in panel variables later does not automatically rewrite that file.
Test joining before adding resources
Launch RedM on your computer, open the client console with F8 and enter connect Address:Port. Use the value under Game (connection). A syntax example is connect 203.0.113.10:30123.
If joining fails, first confirm that Save & Run Server completed and Live Console shows a started game server. Then compare the game port. Neither an assumed default port nor the txAdmin port is a substitute.
Add a resource to the working installation
Back up the working setup before changing it. Extract the resource on your computer first. Its actual directory must contain fxmanifest.lua directly. An extra nested folder can stop the server from recognising it.
Upload through Files & Worlds → Import & Migration, or use SFTP. In the file manager, check that it sits in the resources directory of the server folder txAdmin uses. Check current upload limits in the panel.
In the associated server.cfg, add, for example, ensure beispiel when the resource folder is named beispiel. To test immediately, run these in txAdmin's Live Console:
refresh
ensure beispiel
restart beispiel restarts that individual resource. Restarting the game server reloads the saved server.cfg.
Before installation, check that the author supports RedM. The manifest must support the intended game type, which is rdr3 for RedM. Merely renaming a GTA-only gta5 resource does not turn it into a RedM version. Follow each project's own installation instructions for VORP Core or RSG-Core.
Troubleshoot from the last successful step
If a resource does not start, check its folder name and manifest first. Then read its first error in Live Console, for example a missing dependency. Change one resource at a time and test again.
For help, send support the last successful step and the first related error message. Remove credentials. A full screenshot without timing context makes the investigation harder.