Keep Game Server Online During Maintenance

This guide explains how to keep your community game server reachable and playable while you perform maintenance, such as updating maps, mods, or the server software itself. You’ll learn how to set up a secondary server, redirect players, and communicate effectively so your community stays engaged and doesn’t lose progress.

What You’ll Need

• Access to your game server’s control panel or command line (SSH, RCON, or web host).
• A second server (even a low-spec one) or the ability to run a separate instance on a different port.
• Basic knowledge of your game’s server configuration files (e.g., server.cfg, startup parameters).
• A way to edit text files on the server (FTP, file manager, or nano/vim).
• A communication channel for your community (Discord, forum, in-game announcement).

Step-by-Step

1. Plan the maintenance window. Choose a time when your player count is lowest (check your server logs or activity graph). Announce the window at least 24 hours in advance on your community channel.
2. Prepare the backup server. If you have a second server, install the same game and copy over the core configuration (but not the world data that will change). If you don’t, create a new instance on a different port (e.g., 27016 instead of 27015) on the same machine, if your hardware can handle it.
3. Set up a maintenance message. Configure the backup server to display a custom message like “Maintenance in progress – please check Discord for updates.” Most games support a motd (message of the day) or a custom server description.
4. Enable player redirection. Many games (Source engine, Unreal, etc.) support a sv_redirect or similar command that automatically sends players to another server when the main one goes down. Set this to the backup server’s IP and port. If your game doesn’t support auto-redirect, post the backup’s connection info in your community channel and on the main server’s MOTD.
5. Perform the maintenance on the main server. Shut down the main server, apply updates, change maps, or modify mods. Keep the backup running throughout.
6. Test the main server. Once maintenance is done, start the main server and join it yourself to verify everything works – connect, check for errors, and test core features.
7. Redirect players back. Remove the redirect or announce that the main server is back up. If you used a backup server, shut it down or leave it running for future use.
8. Post a summary. After the maintenance, share what was changed and any new features on your community channel. This builds trust and keeps players informed.

Common Mistakes

• Not testing the backup server. A backup that doesn’t start or crashes on join is worse than none. Always test it with a dummy client before the maintenance window.
• Forgetting to update the backup. If your backup runs an older version of the game, players might get version mismatch errors. Keep it updated alongside the main server.
• No communication. Players will panic if the server goes down without notice. Always announce the window and provide a place to check status.
• Changing too much at once. If you update mods and the game version simultaneously, it’s harder to isolate issues. Do one change at a time.
• Ignoring player data. If your maintenance involves world resets or character wipes, back up the data first and clearly state what will be lost.

Tips

• Use a separate port for the backup server (e.g., 27016) so you don’t have to change the main server’s port.
• Automate the redirect with a script that runs when the main server stops, if your game supports it.
• Keep a checklist of common maintenance tasks (config edits, mod updates, map rotations) to streamline future windows.
• Consider using a game server provider that offers rolling restarts or zero-downtime updates – some do, but it’s not universal.
• If you have a large community, create a dedicated #server-status channel on Discord and pin the maintenance schedule.

Troubleshooting

• Players can’t connect to the backup server. Check that the backup server is running, the port is open in your firewall, and the game version matches the client. Try connecting from a different network.
• Redirect not working. Ensure the redirect command is set correctly (IP and port) and that the backup server is actually up. Some games require the redirect to be set in the server’s startup parameters, not just the console.
• Backup server crashes on load. Check the server logs for missing files or incompatible mods. It might be that the backup is missing a required map or mod – copy it from the main server.
• Main server fails to start after maintenance. Revert the last change (e.g., undo a mod update or restore a config file from backup). Test with a minimal config to isolate the issue.
• Players lose progress on the backup. If the backup has a different world or database, players will see a different state. Make it clear that the backup is temporary and progress there won’t carry over.

Frequently Asked Questions

Can I keep the main server running during maintenance?

Sometimes, if the maintenance is just a map change or a config reload that doesn’t require a full restart. But for updates that change the server binary or core files, a restart is usually necessary. Use the backup server to cover that gap.

Do I need a second physical server?

No. You can run a second instance on the same machine if your CPU and RAM can handle it, or use a cheap VPS for the backup. The key is that it runs the same game and can accept players.

Will the redirect work automatically?

It depends on the game. Source engine games (CS:GO, TF2) support sv_redirect and will automatically move players when the server goes down. Other games may require a manual announcement or a mod. Check your game’s documentation.

What if my game doesn’t support redirect?

You can still keep players informed by setting a MOTD that shows the backup’s IP, or by using a community bot that posts the backup info when the main server goes offline. The backup server itself can be advertised in your Discord.

How long can maintenance take?

It’s best to keep it under 2 hours. If you need longer, consider splitting the maintenance into phases and using the backup server for the entire duration. Communicate the expected length clearly.

Should I back up player data before maintenance?

Yes, always. Even if you’re not planning to wipe, updates can corrupt data. Back up world files, databases, and configs to a safe location before starting.

Related

• Enable Drone Support in Space Engineers
• GoDaddy Dedicated Servers Retiring: What Customers Should Know
• Fix SMS Text Galaxy S7: 9 Working Solutions