1. Match the plan to your project
Decide which framework and additional resources you will use. Plan CPU, RAM and storage for that workload. A plan alone cannot guarantee a fixed player count. Compare Ryzen VPS and FiveM / RedM offers, and read the RAM planning guide.
2. Prepare the operating system and access
Select the installation method for your operating system from the official Cfx.re server documentation. Update the system and, where possible, run the game server as a separate user without general administrator privileges. Back up existing data before changing an installation.
3. Use official server files
Download FXServer files only through the official download links for your chosen installation method. Check recommended builds and dependencies there. txAdmin is already included with FXServer; do not download a supposedly required extra package from an unknown source.
4. Start and configure txAdmin
Follow the txAdmin documentation. Linux uses the supplied run.sh; Windows uses FXServer.exe. For the initial txAdmin monitor-mode start, do not add a +exec argument. Open the address shown in the console and follow the setup dialog.
Protect administrative access: the default txAdmin web port is 40120/TCP, but your configured port may differ. Restrict access to authorised users and suitable network access paths. Do not unnecessarily expose administrative interfaces to the entire internet. Never put licence keys, PINs or credentials in public screenshots or tickets.
5. Check registration and the recipe
Create the required registration key in the official Cfx Portal and enter it only in the designated field. Check account permissions and licence terms yourself. Start with a manageable recipe, review its content and prerequisites, and then add resources. Use the official txAdmin setup guide for the exact steps.
6. Test connectivity deliberately
Match configured game ports against firewall and protection rules. An administrative port is not necessarily a game port. Test the base server from another internet connection first and check the console if it fails. The official Vanilla guide includes an example configuration.
7. Add resources gradually
Add extensions one at a time and test each change. Monitor CPU, RAM and application logs. Store backups separately from the running server and test restoration. For help, send MYPS support a sanitised error, the installation step and software details, not secrets.
