Skip to content
Mamba Host Docs

FiveM Setup

Launch a FiveM roleplay server on Mamba Host in minutes. All plans include txAdmin, full FTP/SFTP access, automatic backups, DDoS protection, and priority ticket routing on Premium tiers.

Before You Begin

Section titled “Before You Begin”
  • Active FiveM license key from https://keymaster.fivem.net tied to your Cfx.re account.
  • Chosen framework (ESX, QBCore, vRP, or custom) with config files and SQL seed data.
  • Resource pack list (scripts, cars, MLOs, clothing, UI packages) plus dependencies.
  • Optional DNS record (e.g., cityrp.example.com) pointing to your server for friendly connection strings.
  • Discord server + webhook ready if you plan to sync whitelist, bans, or announcements.

Plan Sizing

Section titled “Plan Sizing”
PlanResourcesPlayer TargetIdeal Use
Starter3 GB RAM / 1 vCPU16–24 playersBeta tests, whitelist-only servers
Pro5 GB RAM / 1.5 vCPU32–48 playersEstablished RP communities with moderate scripts
Premium8 GB RAM / 2 vCPU64–96 playersHeavy economies, custom cars/MLOs, priority support

Upgrade when CPU exceeds ~80% during peak hours, or when restart times climb beyond 2 minutes due to resource load.

1. Provision the Server

Section titled “1. Provision the Server”
  1. Sign in at https://panel.mambahost.com → Create Server → select FiveM.
  2. Choose plan/region and deploy. Builds finish in under two minutes on Dell PowerEdge R630 nodes (dual E5-2680v4, NVMe).
  3. Copy the txAdmin URL + login details displayed in the console.
  4. Enable backups and schedule daily snapshots before making big content changes.

2. First Login & Hardening

Section titled “2. First Login & Hardening”
  • Set a strong txAdmin password on first login.
  • Rotate the auto-generated SFTP password (Account → Security) and create per-staff panel accounts with least privilege.
  • Enable automatic backups, restarts, and update reminders via the panel scheduler.
  • Lock down RCON (if enabled) and document port usage (30120–30199 by default).

3. txAdmin Onboarding

Section titled “3. txAdmin Onboarding”
  1. Open the txAdmin URL and follow the wizard.
  2. Select Existing Recipe (ESX/QBCore) or Custom Template for bespoke frameworks.
  3. Enter your FiveM license key and server name.
  4. Configure project path and owner identifiers.
  5. Start the FXServer instance and confirm logs show no missing resources.

4. Framework & Resource Installation

Section titled “4. Framework & Resource Installation”
  • ESX: Upload ESX base files to /resources, import SQL schema, configure server.cfg orders, and set database credentials in es_extended, esx_addonaccount, etc.
  • QBCore: Upload /qb-core and dependencies (qb-menu, qb-target, qb-inventory), run migrations, and update server.cfg.
  • vRP/Custom: Drop resources under /resources, ensure fxmanifest versions match, and keep dependencies grouped.
  • Database: Request MySQL/MariaDB (included). Store credentials via env vars and configure mysql_connection_string or oxmysql.
  • Load order rule: frameworks → dependency libs (ox_lib, PolyZone) → job scripts → assets (cars/MLOs) → dev/test scripts.

5. Resource Deployment

Section titled “5. Resource Deployment”
  1. Upload scripts/MLOs/vehicles via SFTP to /resources.
  2. Add ensure <resource> entries to server.cfg in dependency order.
  3. Use txAdmin live console + resmon to catch missing dependencies or heavy scripts.
  4. Schedule restarts (every 6–12 hours) via txAdmin Tasks to clear memory.
  5. Offload static assets (UI images, audio) to CDN storage for faster downloads.

6. Enable OneSync Infinity

Section titled “6. Enable OneSync Infinity”
  • Set onesync on (or onesync legacy) in server.cfg.
  • Add sets onesync_enableInfinity 1 for Infinity mode.
  • Adjust player slots in txAdmin (Settings → FXServer → Player Slots).
  • Monitor CPU/RAM via panel graphs; scale up once Infinity + resource load pushes CPU above 80%.

7. Performance Playbook

Section titled “7. Performance Playbook”
  • Remove idle resources instead of leaving them stopped—each ensure adds load.
  • Use /tx perf and txAdmin Performance tab to monitor tick rate.
  • Store persistent data in MySQL rather than JSON to reduce disk IO.
  • Use sv_master1 "" for staging servers to keep them private.
  • Regularly benchmark with profiling tools (Cfx profiler, resmon) after major script drops.

8. Operations & Monetization

Section titled “8. Operations & Monetization”
  • Schedule weekly maintenance windows; snapshot resources + SQL beforehand.
  • Follow Cfx.re monetization terms—use compliant Tebex stores or approved equivalents.
  • Sync whitelist/bans with Discord bots hosted on Mamba Host for faster moderation.
  • Track key metrics (average players, retention, queue time) and feed them into marketing automations (see docs/N8N_MARKETING_AUTOMATION.md).
  • Document onboarding for staff: txAdmin access, resource deployment, incident response.

9. Scaling Strategies

Section titled “9. Scaling Strategies”
ScenarioApproach
Need more than 96 slotsSplit into multiple “district” servers (North/South), share economy via MySQL
Multi-framework testingClone server, change framework in staging, run load tests
Regional expansionRequest EU/West Coast DCs (beta) and direct players with DNS (e.g., la.cityrp.gg)
High availabilityMaintain hot standby container synced nightly via SFTP/rsync

10. Troubleshooting

Section titled “10. Troubleshooting”
  • Players can’t connect: Ports 30120–30199 are open; confirm player ISP/firewall settings or Cloudflare Spectrum config if proxying.
  • Stuck on loading screen: Verify CDN assets, clear cache folders, ensure sv_hostname and banner URLs are valid, and check loadscreen resources.
  • txAdmin red, panel green: Restart via txAdmin only to avoid double restarts.
  • Resource crashes on start: Check console for missing dependencies or fxmanifest typos; load resources one at a time to isolate issues.
  • Database locked: Confirm credentials, reduce connection pools, avoid migrations during peak hours.
  • Voice issues (mumble/pma-voice): Ensure proper ports, dependencies (mumble-voip, rp-radio) match versions, and network jitter is low.
Section titled “Helpful Links”