Skip to content
Mamba Panel Docs

Game Server Troubleshooting

Reference this guide when customers report game server issues. Organized by symptom category for quick diagnosis.

Connection Issues

Section titled “Connection Issues”

Players Can’t Connect

Section titled “Players Can’t Connect”
SymptomPossible CauseResolution
Connection timed outServer not runningCheck portal status, start server
Connection refusedWrong IP/portVerify connection details in portal
Server not in browserStill booting, private modeWait 5 minutes, check server flags
Kicked immediatelyWhitelist, ban, version mismatchCheck server logs, verify client version

Diagnostic Steps

Section titled “Diagnostic Steps”
  1. Verify server is running — Check portal status indicator
  2. Check connection info — Confirm IP:port from portal
  3. Review firewall — Ports should be open automatically
  4. Test locally — Try connecting from same network
  5. Check game version — Client and server must match

Network Troubleshooting

Section titled “Network Troubleshooting”

If connection issues persist:

  1. Customer should try:

    • Flush DNS (ipconfig /flushdns on Windows)
    • Disable VPN temporarily
    • Try different network

  2. Check server side:

    • Verify allocations in Pterodactyl
    • Check for DDoS mitigation triggers
    • Review node network status

Performance Problems

Section titled “Performance Problems”

High Latency/Lag

Section titled “High Latency/Lag”

Symptoms:

  • Rubber-banding
  • Delayed actions
  • High ping reported

Solutions:

  1. Check server location vs player location
  2. Reduce tick rate if applicable
  3. Optimize heavy scripts/plugins
  4. Upgrade plan for more resources
  5. Check node network status

Low TPS/Tick Rate

Section titled “Low TPS/Tick Rate”

Common in: Minecraft, FiveM, Rust

Causes:

  • CPU overload
  • Heavy plugins/scripts
  • World size/complexity
  • Memory pressure

Solutions:

  1. Profile with game-specific tools:
    • Minecraft: /spark profiler, Timings
    • FiveM: resmon, txAdmin performance
    • Rust: Oxide diagnostics
  2. Identify heavy operations
  3. Optimize or remove problematic addons
  4. Upgrade plan resources

Memory Issues

Section titled “Memory Issues”

Symptoms:

  • Server crashes
  • “Out of memory” errors
  • Degrading performance over time

Solutions:

  1. Check current memory usage in portal
  2. Review memory allocation vs plan limit
  3. Schedule regular restarts to clear memory
  4. Identify memory leaks in plugins/mods
  5. Upgrade plan if consistently near limit

Server Won’t Start

Section titled “Server Won’t Start”

Immediate Crash (Exit Code 1)

Section titled “Immediate Crash (Exit Code 1)”

Causes:

  • Configuration error
  • Missing dependencies
  • Corrupted files

Diagnostic steps:

  1. Check console output for error message
  2. Review recent changes (configs, plugins, updates)
  3. Try starting with minimal configuration
  4. Restore from last known working backup

Exit Code 137 (OOM Kill)

Section titled “Exit Code 137 (OOM Kill)”

Server ran out of memory:

  1. Reduce startup memory allocation
  2. Remove heavy plugins/mods
  3. Upgrade plan for more RAM
  4. Check for memory leaks

Exit Code 0 (Clean Exit)

Section titled “Exit Code 0 (Clean Exit)”

Server exited normally but shouldn’t have:

  1. Check if startup command is correct
  2. Verify game files aren’t corrupted
  3. Review configuration for auto-stop settings

Game-Specific Issues

Section titled “Game-Specific Issues”

Minecraft

Section titled “Minecraft”
IssueCauseFix
Chunk errorsCorruptionDelete region files or restore backup
Plugin conflictsIncompatible versionsCheck plugin compatibility matrix
Forge/Fabric crashMod conflictsReview crash log, remove conflicting mods
World not loadingWrong level-nameCheck server.properties

FiveM

Section titled “FiveM”
IssueCauseFix
Infinite loadingResource errorCheck txAdmin console for errors
txAdmin won’t startPort conflict, config errorVerify ports, reset txAdmin
Database errorsConnection string wrongCheck mysql_connection_string
Resources not loadingManifest error, dependency missingCheck fxmanifest.lua, load order

Rust

Section titled “Rust”
IssueCauseFix
EAC kicksEAC configurationVerify EAC settings
Wipe issuesIncomplete wipeDelete all map/save files
Plugin errorsOxide version mismatchUpdate Oxide, check plugin compatibility

ARK/Other

Section titled “ARK/Other”
IssueCauseFix
Mods not downloadingSteam Workshop issuesForce mod update, verify IDs
Save corruptionImproper shutdownRestore backup, enable autosave
Admin commands failNot configuredAdd Steam IDs to admin config

File & Upload Issues

Section titled “File & Upload Issues”

Upload Failures

Section titled “Upload Failures”
ErrorCauseFix
413 Request Too LargeFile too big for web uploadUse SFTP instead
Permission deniedWrong file ownershipRe-upload via SFTP
Connection timeoutSlow connectionUse reliable network, compress files

Corrupted Configs

Section titled “Corrupted Configs”

Prevention:

  • Use proper text editors (not Word)
  • Version control important configs
  • Backup before editing

Recovery:

  1. Restore from backup
  2. Download fresh default config
  3. Manually fix syntax errors

SFTP Connection Issues

Section titled “SFTP Connection Issues”
IssueFix
Connection refusedVerify port (usually 2022), check credentials
Authentication failedReset password in portal
TimeoutCheck firewall, try different client

Backup & Restore

Section titled “Backup & Restore”

Backup Failures

Section titled “Backup Failures”

Causes:

  • Storage limit reached
  • Server running during backup
  • File locks

Solutions:

  1. Check storage usage
  2. Stop server before manual backup
  3. Verify backup schedule configuration

Restore Issues

Section titled “Restore Issues”
  1. Verify backup integrity before restore
  2. Stop server completely
  3. Choose correct restore options
  4. Restart and verify

Scheduled Tasks

Section titled “Scheduled Tasks”

Tasks Not Running

Section titled “Tasks Not Running”
  1. Verify schedule is enabled
  2. Check cron expression syntax
  3. Confirm timezone settings
  4. Review task execution logs

Tasks Running Wrong Time

Section titled “Tasks Running Wrong Time”
  1. Verify timezone configuration
  2. Check cron expression (minute/hour order)
  3. Account for DST if applicable

When to Escalate

Section titled “When to Escalate”

Infrastructure Issues

Section titled “Infrastructure Issues”

Contact support when:

  • Multiple customers affected
  • Node-level problems suspected
  • Network issues beyond customer control
  • Hardware failures

Information to Collect

Section titled “Information to Collect”
Server Information:
- Server name and ID
- Game type and version
- Plan tier


Issue Details:
- When it started
- What changed recently
- Error messages/logs


Troubleshooting Done:
- Steps already taken
- Results of each step

Quick Reference

Section titled “Quick Reference”

Check Server Status

Section titled “Check Server Status”
  1. Portal → Server → Status indicator

View Console/Logs

Section titled “View Console/Logs”
  1. Portal → Server → Console

Restart Server

Section titled “Restart Server”
  1. Portal → Server → Restart button

Access Files

Section titled “Access Files”
  1. Portal → Server → File Manager
  2. Or via SFTP (port 2022)

Restore Backup

Section titled “Restore Backup”
  1. Portal → Server → Backups
  2. Select backup → Restore
Section titled “Related Documentation”