FiveM Server Hosting

Choose a host based on real performance measurements, region, management effort and backups—not on a fixed “player capacity” advertised for a particular CPU or RAM amount. Resource load varies widely between a vanilla FiveM server and a heavily customized QBCore , ESX  or Qbox server.

Want a containerized installation? See Run a FiveM Server Using Docker. For the standard setup use FiveM Quickstart with txAdmin.

1. Choose a hosting model

Cloud providers may charge separately for outbound bandwidth, IP addresses, snapshots, block storage and protection. Compare the complete monthly cost, not only the headline VM price.

For managed game hosting, follow the official Cfx.re game server hosting provider guide , or the current hosting-provider listings linked by Cfx.re. Check provider and platform policies before purchasing.

2. Compare providers without relying on obsolete prices

These companies sell infrastructure that can be used to host a supported FXServer installation. They are not an endorsement or a claim that a specific plan is suitable for a fixed number of players.

Prices, model names, CPU generations and available regions change frequently. Do not rely on old recommendations such as Hetzner CX11/CPX31/AX41 or OVH “Starter” at historically quoted prices; check official provider pages at purchase time. Price does not guarantee latency or stable resource performance.

3. Size by workload, not marketing player counts

Use these as initial test allocations, then benchmark your actual resources:

These numbers are planning examples, not official minimums or slot guarantees. The CPU’s single-thread performance often matters more than a high total thread count. Test under peak realistic concurrency and use Performance Monitoring.

Choose a server region near most players. Check latency and packet loss from multiple relevant networks, not just a provider’s ping from your home connection.

4. Server, database and security requirements

• Use a supported 64-bit Windows or x86-64 Linux FXServer artifact from Cfx.re Server Download . macOS has no supported native server artifact.
• For Legacy vs Enhanced, use the correct platform package and verify resource compatibility. See Legacy vs Enhanced.
• Keep the game port 30120 TCP and UDP reachable by intended players. If you change the port, update both the config and firewall accordingly.
• Restrict txAdmin port 40120 TCP to VPN, SSH tunnel, trusted management IPs or the host’s authenticated panel.
• Obtain a Cfx.re server registration key ; keep it private and use sv_licenseKey in the selected profile.
• The basic CFX server recipe does not require a database. Framework-based persistence normally requires MariaDB/MySQL with a dedicated, least-privilege database user.
• Require SSH keys or a properly protected Windows management path; avoid running game resources as root.
• Arrange for off-server backups of txData, resources/config and any separate SQL database. Test a full restore before launch.

5. Set up a Linux VPS safely

The following example assumes you have provisioned a Linux x86-64 VM, connected as an account with sudo, and understand the provider’s firewall/security-group controls. It installs only base utilities—not an outdated or hard-coded artifact build.

sudo apt update
sudo apt install -y curl git xz-utils ca-certificates
 
# Create a dedicated unprivileged service account.
sudo useradd --create-home --shell /bin/bash fivem
 
# Prepare separate artifact and data directories.
sudo mkdir -p /opt/fivem/server /opt/fivem/txData
sudo chown -R fivem:fivem /opt/fivem

Next:

1. Download Recommended from the official FXServer artifact selector  (correct platform/OS); extract it into /opt/fivem/server.

2. Run run.sh as the fivem user without +exec server.cfg for the txAdmin first-run flow.

3. Link your Cfx.re account and create a backup password in txAdmin, then choose the CFX Default recipe for a first test.

4. Generate a registration key at the Cfx.re Portal, run the recipe and start the server.

5. Allow the game port in both the host and provider firewalls. For UFW that is already enabled:

   Copy code

   sudo ufw allow 30120/tcp
   sudo ufw allow 30120/udp
   sudo ufw status

6. Leave txAdmin’s public port blocked. Use a private VPN or an SSH tunnel to administer it.

7. Test connection from a Windows FiveM client using F8: connect YOUR_SERVER_IP:30120.

Do not enable UFW remotely before explicitly allowing your existing SSH port, or you risk locking yourself out. Service management/systemd depends on your chosen deployment layout; see the full txAdmin quickstart before enabling a boot-time service.

6. Measure and validate a production candidate

Test the actual target framework with the resources and database you intend to run:

1. Correctness: resources load, characters spawn, data survives reconnect and restarts.
2. Capacity: realistic peak players, resource load, server-thread time, CPU headroom, memory, disk and database latency.
3. Network: a second external network can join via TCP/UDP 30120, with acceptable packet loss.
4. Reliability: provider maintenance response, recovery procedure, DDoS handling and backup/restore time.
5. Security: txAdmin isn’t publicly accessible, game secrets aren’t in Git, and access is limited to authorized administrators.

Do not rely on unverified, provider-specific “benchmarks” without their exact workload, tests and dates. A generic CPU score does not tell you how your FiveM scripts behave.

7. Migrate an existing server

1. Inventory artifact build, framework versions, server.cfg, resources, database, user uploads and KVP/state files.
2. Make a complete off-server backup and test recovery.
3. Provision the target server and apply firewall/SSH restrictions.
4. Restore into a staging profile and database, with secrets managed separately.
5. Validate joins, player identity, inventory, economy, voice and persistence.
6. Schedule a short maintenance window to stop writes, capture final data and switch the player endpoint.
7. Monitor and keep the previous installation available for a documented rollback. Do not run both installations against the same writable production database during the cutover.

Related documentation

• How to Create a FiveM Server
• Server Requirements
• Server Networking
• Cfx.re Artifacts and Updates
• txAdmin Security
• Backups and Restoration