Skip to content

FiveM Server Hosting

This guide covers setting up and managing FiveM hosting products in Mamba Panel for your customers.

FiveM is a popular multiplayer modification for GTA V, commonly used for roleplay servers. Mamba Panel provides:

  • Automated server provisioning via Pterodactyl
  • txAdmin integration for server management
  • Support for ESX, QBCore, and custom frameworks
  • MySQL database provisioning

Navigate to Products → Game Servers → Create Plan and configure:

SettingStarterProPremium
RAM3 GB5 GB8 GB
CPU1 vCPU1.5 vCPU2 vCPU
Storage20 GB40 GB80 GB
Player Estimate16-2432-4864-96
MySQLOptionalIncludedIncluded
Suggested Price$8.49/mo$14.99/mo$24.99/mo

Use the FiveM Pterodactyl egg with txAdmin support:

  1. Configure egg in Settings → Integrations → Pterodactyl → Eggs
  2. Map FiveM products to the appropriate egg
  3. Configure default startup parameters
  4. Set txAdmin as default server management interface

Starter (16-24 players):

  • Small communities, beta testing
  • Light scripts, minimal MLOs
  • Development/testing environments

Pro (32-48 players):

  • Established RP communities
  • Moderate script load
  • Standard framework (ESX/QBCore)

Premium (64-96+ players):

  • Large communities
  • Heavy economies, custom cars/MLOs
  • OneSync Infinity support

Customers need before setup:

  • FiveM license key from https://keymaster.fivem.net
  • Cfx.re account linked to license
  • Framework choice (ESX, QBCore, vRP, custom)
  • Resource pack (scripts, vehicles, MLOs)
  1. Customer purchases FiveM hosting plan
  2. Mamba Panel provisions server via Pterodactyl
  3. Customer receives:
    • txAdmin URL and initial credentials
    • SFTP access for file uploads
    • MySQL credentials (if included)
    • Server connection info

Guide customers through:

  1. Access txAdmin — Open URL from portal, log in
  2. Run setup wizard — Configure server identity
  3. Enter license key — From Cfx.re Keymaster
  4. Select template:
    • ESX Legacy
    • QBCore
    • Custom/Blank
  5. Configure project path — Usually /home/container/server-data
  6. Set owner identifiers — Discord ID, license, Steam
  7. Start FXServer — Monitor console for issues
  1. Download ESX base files
  2. Upload to /resources/[esx]
  3. Import SQL schema to MySQL
  4. Configure server.cfg:
ensure es_extended
ensure esx_menu_default
ensure esx_menu_dialog
ensure esx_menu_list
  1. Update database connection in es_extended/config.lua
  1. Download QBCore framework
  2. Upload to /resources/[qb]
  3. Run database migrations
  4. Configure server.cfg:
ensure qb-core
ensure qb-multicharacter
ensure qb-spawn
ensure qb-inventory
  1. Set mysql_connection_string in server.cfg

For MySQL connection string:

set mysql_connection_string "mysql://user:pass@host:3306/database?charset=utf8mb4"

Configure oxmysql or mysql-async as the database driver.

Recommend this order in server.cfg:

# 1. Core/Framework
ensure es_extended OR ensure qb-core
# 2. Dependencies
ensure ox_lib
ensure PolyZone
# 3. Job scripts
ensure esx_jobs
# 4. Vehicles/MLOs
ensure custom_cars
# 5. UI/HUD
ensure custom_hud
  1. Upload via SFTP to /resources/[category]/
  2. Add ensure [resource_name] to server.cfg
  3. Restart server or use /refresh + /start [resource]
  4. Monitor console for errors

For larger servers, enable OneSync:

In server.cfg:

set onesync on
set onesync_enableInfinity 1

Adjust player slots in txAdmin settings.

# server.cfg optimizations
sv_maxClients 64
set sv_enforceGameBuild 2699
sv_scriptHookAllowed 0
sets sv_projectName "Server Name"

Use txAdmin and resmon for performance:

  • Monitor tick time (should be < 16ms)
  • Track resource CPU usage
  • Identify heavy scripts
  1. Remove unused resources — Don’t just stop, delete ensure lines
  2. Optimize database queries — Index frequently queried columns
  3. Reduce sync frequency — For non-critical data
  4. Use streaming — For custom vehicles and MLOs
  5. Cache data — Reduce repeated database calls

Configure schedules for:

  • Daily server files backup
  • Database dumps (mysqldump)
  • Pre-update snapshots

Recommend to customers:

  • Schedule 4-6 hour restarts to clear memory
  • Weekly maintenance windows for updates
  • Pre-announce downtime to players
  1. Keep offline backups of:
    • server-data directory
    • MySQL database exports
    • Resource configurations
  2. Document custom configurations
  3. Test restore procedures periodically
IssueCauseResolution
Can’t connectWrong IP, server not startedCheck portal status, verify IP:port
Stuck loadingResource error, asset issuesCheck txAdmin console, clear cache
txAdmin red, panel greenFXServer crashedRestart via txAdmin, check logs
Database errorsWrong credentials, connection limitVerify mysql_connection_string
Missing vehicles/MLOsNot streaming correctlyCheck manifest files, stream folder
Voice not workingWrong pma-voice configVerify dependencies and ports

Recommend upgrades when:

  • Average CPU > 80%
  • RAM usage approaching limit
  • Player count hitting cap
  • Restart times > 2 minutes

For large communities needing multiple servers:

ServerPurpose
MainPrimary RP server
TestDevelopment/staging
EventsSpecial events
BackupHot standby

Share database across servers for unified economy/characters.

Remind customers about:

  • Cfx.re monetization guidelines
  • Tebex compliance for donations
  • Asset licensing (vehicles, MLOs)
  • Copyright considerations
  • Understand txAdmin basics
  • Know common FiveM errors
  • Recognize resource conflicts

Provide links to: