Skip to content

Game Server Troubleshooting

Use this guide when any hosted title (Minecraft, FiveM, Rust, CS2, Arma, Squad, Pavlov, etc.) misbehaves. Work through the sections in order and escalate to support with the requested data when needed.

SymptomLikely CauseFix
Players can’t connectLocal ISP/firewall blocking game ports, wrong IP/port, DDoS mitigation trippedVerify the IP/port from the panel, ensure router/ISP allows UDP/TCP on the required ports, confirm no Geo/IP blocks, check https://status.mambahost.com
Server not visible in browser listsServer still booting, wrong query port, using private flagAllow up to 5 minutes after restart, confirm query port matches the game’s default, disable private/hidden flags if you want public listing
Panel shows online but game unreachableGame process hung, txAdmin/HC crashedRestart via the in-game control tool first (txAdmin, RCON); if still stuck, use panel restart and review logs
  • High CPU: Reduce tickrate/view distance, disable idle resources/plugins, or upgrade tier. For Rust/FiveM, profile scripts (resmon, Oxide diagnostics).
  • High RAM: Remove unused mods, ensure backups don’t run during peak, and consider larger plan tiers when RAM exceeds 75%.
  • Disk usage spikes: Rotate logs, clean old backups, and offload large files (demos, replays) to object storage.
  • Latency/Ping: Run the status speed test, confirm players connect to the closest region, and remove heavy middleware (vpn/proxy) when taking connections.
  • Upload failures / 413 errors: Use SFTP (port 2022) for files >100 MB. Ensure local client uses binary mode for archives.
  • Corrupted configs: Version control files locally; re-upload clean copies if the panel editor introduced encoding issues.
  • Permissions errors: Ensure uploaded files inherit container user ownership (default). Re-upload via SFTP rather than using root-owned archives.
  • Backups not running: confirm scheduler tasks are enabled and time zones match expectations.
  • Restarts overlapping events: stagger scheduled tasks and avoid chaining mission restarts with heavy backup jobs.
  • Wipe tasks skipped: double-check command syntax (bpwipe, app_update, etc.) and that tasks are assigned to the proper container.
  • Panel Console: First stop for stack traces, plugin errors, or startup failures.
  • Game-specific logs: e.g., /oxide/logs/ (Rust), /csgo/logs/, /txData/ (FiveM), /SquadGame/Saved/Logs/.
  • External tools: resmon (FiveM), net_graph (CS2), Spark/Timings (Minecraft), Arma rpt logs (.rpt in profiles dir).
  • Attach relevant log excerpts when opening support tickets.
  • Rotate panel/SFTP/RCON passwords quarterly or when staff changes.
  • Use per-user panel accounts with least privilege.
  • For DDoS/attack suspicion, check https://status.mambahost.com; open support ticket if ports show abnormal traffic despite mitigations.

Provide the following for faster resolution:

  1. Server name + panel UUID.
  2. Timeline of events and recent changes (mods, configs, wipes).
  3. Logs/stack traces.
  4. Player counts, regions affected, and reproduction steps.
  5. Actions already taken (restarts, rollbacks).

Email support@mambahost.com or open a Discord ticket with the info above. For critical outages (production Premium plans), tag the on-call role in Discord after filing a ticket.