Skip to content

Common Issues

📊 Check Service Status First: Before troubleshooting your specific server, check our Service Status Page to see if there are any ongoing platform issues that might be affecting your server.

If there’s a known issue affecting multiple servers, wait for the all-clear before troubleshooting individual server problems.

First, verify the server status in your control panel:

  1. Platform Status: Check status.gamelords.gg for system-wide issues
  2. Server State: Check if server shows as “Starting”, “Stopped”, or “Error”
  3. Console Output: Look for error messages in the console
  4. Resource Usage: Verify sufficient RAM and storage
  5. Recent Changes: Consider any recent configuration modifications

Error: “Failed to bind to port” or “Address already in use”

Solutions:

  • Change server port in configuration
  • Wait 5-10 minutes if recently stopped
  • Contact support if port conflicts persist
  • Check for multiple server instances

Error: “Invalid configuration” or parsing errors

Solutions:

  • Validate configuration file syntax
  • Check for missing quotation marks or brackets
  • Restore from backup configuration
  • Use default configuration as baseline

Error: “Out of memory” or performance warnings

Solutions:

  • Upgrade server plan for more RAM
  • Reduce max players or world size
  • Remove resource-heavy mods or plugins
  • Optimize server settings

Error: “Missing required files” or crash on startup

Solutions:

  • Verify game files through control panel
  • Reinstall server if files are corrupted
  • Check for recent game updates
  • Restore from backup if available
  1. Server Status: Ensure server is online and running
  2. IP Address: Verify correct IP and port
  3. Firewall Issues: Check local firewall settings
  4. Network Problems: Try from different network

Minecraft:

  • Version mismatch between client and server
  • Whitelist enabled (players not added)
  • Server in offline mode
  • Incorrect port (default: 25565)

Rust:

  • BattlEye or EAC authentication issues
  • Server wipe in progress
  • Queue system full
  • Client verification problems

ARK:

  • Password protection enabled
  • Mod synchronization required
  • Character transfer restrictions
  • Server not responding to queries
  1. Server Location: Choose server closest to players
  2. Internet Connection: Check local network quality
  3. Peak Hours: Consider time-based traffic patterns
  4. ISP Routing: Some routes may be suboptimal
  • Reduce max players if overloaded
  • Optimize game settings for performance
  • Remove laggy plugins or mods
  • Monitor resource usage
  1. Check Console: Look for crash or error patterns
  2. Resource Monitoring: Watch CPU, RAM, and storage
  3. Plugin Problems: Disable problematic modifications
  4. Network Stability: Monitor for connection drops
  • Update game client to latest version
  • Verify game file integrity
  • Reset network adapter settings
  • Try different connection methods
  1. Reduce Entity Count: Limit spawned objects/NPCs
  2. Lower View Distance: Decrease render distance
  3. Optimize Plugins: Remove or update heavy plugins
  4. Map Optimization: Choose less complex maps

Minecraft:

view-distance=8
simulation-distance=6
entity-activation-range.animals=16
entity-activation-range.monsters=24

Rust:

fps.limit 30
server.tickrate 20
spawn.max_density 0.5

CS2:

fps_max 300
sv_maxrate 786432
sv_mincmdrate 64
sv_maxcmdrate 128
  1. Monitor Usage: Check RAM consumption over time
  2. Memory Leaks: Look for gradually increasing usage
  3. Restart Schedule: Implement regular restarts
  4. Optimize Settings: Reduce memory-intensive features
  • Survival Games: Limit building complexity and entity counts
  • FPS Games: Reduce player count or map complexity
  • Sandbox Games: Implement cleanup systems
  • RPG Games: Manage NPC spawns and world persistence
  1. SSD vs HDD: Upgrade to SSD storage if available
  2. File Organization: Keep server files organized
  3. Cache Management: Clear unnecessary cache files
  4. Defragmentation: Regular maintenance (HDD only)
  • FastDL: Set up fast download servers
  • Compression: Use compressed files where possible
  • CDN: Consider content delivery networks
  • Local Caching: Enable client-side caching
  • Corrupted chunks: Delete and regenerate affected areas
  • Missing biomes: Check world generation settings
  • Lag spikes: Reduce pre-generation or chunk loading
  • Border issues: Verify world border settings
Common Conflict Patterns:
- Economy plugins interfering with each other
- Permission plugins causing command failures
- Chat plugins conflicting with moderation tools
- World management plugins overlapping features
  • Use Paper instead of Vanilla for better performance
  • Implement view distance optimization
  • Configure entity activation ranges
  • Set up automatic restarts
  • Map corruption: Backup before wipes
  • Player data loss: Separate map and blueprint wipes
  • Mod compatibility: Update mods after wipes
  • Save timing: Coordinate wipes with player activity
Common Plugin Problems:
- Economics plugins causing money duplication
- Teleportation plugins breaking PvP balance
- Admin tools being accessible to players
- Performance plugins causing crashes
  1. Immediate Action: Stop server immediately
  2. Backup Restoration: Use most recent valid backup
  3. Storage Check: Verify storage device health
  4. Prevention: Enable automatic backups
  • Load Order: Ensure proper mod loading sequence
  • Version Matching: Keep mods updated together
  • Conflict Resolution: Test mod combinations
  • Fallback Plan: Maintain mod-free backup

Source Engine Games (CS2, TF2, GMod, L4D2)

Section titled “Source Engine Games (CS2, TF2, GMod, L4D2)”
Common SourceMod Issues:
- Plugin compilation errors
- Database connection failures
- Admin permission conflicts
- Map change problems
  • Regular map changes help prevent buildup
  • Monitor plugin memory usage
  • Disable problematic plugins
  • Restart server during low activity periods
  1. Strong Passwords: Use complex RCON passwords
  2. Regular Changes: Update passwords periodically
  3. Access Logs: Monitor admin command usage
  4. Privilege Levels: Use minimal required permissions
  • Anti-cheat: Enable appropriate anti-cheat systems
  • IP Banning: Block problematic addresses
  • Hardware Bans: Use HWID bans when available
  • Community Reporting: Enable player reporting systems

Game Lords provides DDoS protection, but you can enhance it:

  1. Rate Limiting: Configure connection rate limits
  2. Query Limits: Restrict server query frequency
  3. Connection Limits: Set maximum simultaneous connections
  4. Whitelist Mode: Temporary protection during attacks
// Example rate limiting configurations
sv_max_queries_sec 3
sv_max_queries_window 30
sv_max_queries_global 60
sv_maxrate 80000
  • Backup Systems: Regular automatic backups
  • Permission Systems: Proper role-based permissions
  • Activity Logging: Track player actions
  • Rollback Tools: Quick restoration capabilities
  • Active Admins: Regular admin presence
  • Reporting Systems: Easy player reporting
  • Clear Rules: Published and enforced guidelines
  • Appeal Process: Fair punishment review system
  • Server corruption or crashes
  • Griefing or vandalism
  • Accidental deletions
  • Plugin or mod failures
  1. Stop Server: Always stop before restoration
  2. Backup Current: Save current state (even if corrupted)
  3. Select Restore Point: Choose appropriate backup
  4. Verify Restoration: Test server after restoration
  5. Player Communication: Inform players of any data loss
  1. Identify Corruption: Check file sizes and timestamps
  2. Partial Recovery: Attempt to recover readable portions
  3. Backup Sources: Check multiple backup locations
  4. Professional Recovery: Contact support for critical data
  • Multiple Backups: Keep several backup copies
  • Regular Testing: Verify backup integrity
  • Off-site Storage: Store backups separately
  • Automated Systems: Use automated backup solutions
  1. Error Messages: Complete error text and codes
  2. Server Logs: Recent console output and log files
  3. Configuration Files: Current server settings
  4. Steps to Reproduce: Detailed problem recreation steps
  5. Timeline: When the problem started occurring
  • Safe Mode: Start server with minimal configuration
  • Plugin Isolation: Disable all plugins/mods
  • Default Settings: Test with default configuration
  • Alternative Methods: Try different approaches
  • Critical Issues: Server completely down
  • Security Problems: Active attacks or breaches
  • Data Loss: Corrupted or missing critical files
  • Payment Issues: Billing or subscription problems
  • Performance Issues: Optimization needs
  • Configuration Help: Setup assistance
  • Plugin Problems: Modification troubleshooting
  • General Questions: Feature inquiries
  • Official Forums: Game developer communities
  • Reddit Communities: r/AdminCraft (Minecraft), r/playrust (Rust), etc.
  • Discord Servers: Real-time community help
  • YouTube Tutorials: Video guides and tutorials
  • Admin Tools: Server management software
  • Monitoring Services: Uptime and performance tracking
  • Knowledge Bases: Comprehensive documentation
  • Professional Services: Paid consultation available

Remember: Most issues have been encountered before. If you can’t find a solution in this documentation:

🎫 Create a Support Ticket: For personalized assistance, visit help.gamelords.gg to submit a detailed ticket. Include:

  • Your server details and game type
  • Steps you’ve already tried
  • Screenshots or error messages
  • When the issue started

💬 Join Our Discord: Connect with our community and support team for real-time help

📧 Emergency Contact: For critical server issues, reach us at support@gamelords.com

Our support team typically responds to tickets within 2-4 hours during business hours and can provide remote assistance when needed.