This guide covers common issues and solutions for Nightingale dedicated servers hosted with Legion Hosting, including crashes, connection problems, performance optimization, and save recovery. For initial server setup and configuration, see Nightingale Server Setup Guide.
Server Crashes
Server crashes can have multiple causes. Start by checking the GPanel console for error output, then work through the following common causes.
Checking Logs
- In GPanel, go to the Console tab and scroll up to find error messages that appeared before the crash.
- Check the server's log files through the Files tab. Look for a
LogsorSaved/Logsdirectory containing timestamped log files. - The most recent log file will contain crash details, stack traces, and error messages that help identify the cause.
Out of Memory
- Nightingale can be memory-intensive, especially with many explored realms and built structures.
- Check GPanel's resource usage graphs to see if the server is hitting its RAM limit.
- If memory is consistently maxed out, consider upgrading your server plan. Open a support ticket to discuss options.
- Reducing
MaxPlayerscan lower memory usage, as each player's data and loaded areas consume additional RAM.
Proton/Wine Compatibility (Linux Servers)
Nightingale's dedicated server may run under Proton or Wine on Linux-based hosting. Compatibility issues can cause crashes or unexpected behavior.
- Check the console for Proton-related error messages on startup.
- If the server crashes immediately on start with compatibility errors, open a support ticket so our team can check the Proton configuration.
- Some game updates may temporarily break Proton compatibility until the compatibility layer is updated.
Corrupted Save Data
- If the server crashes during world load, the save data may be corrupted.
- Try restoring from a backup (see the Save Recovery section below).
- If no backup is available, you may need to delete the save directory and start a fresh world.
Crash on Startup After Update
- Game updates can sometimes introduce bugs that affect dedicated servers.
- Check the official Nightingale community channels (Steam forums, Discord) for known issues with the latest update.
- Try restarting the server — some update-related issues resolve after a clean restart.
- If the crash persists, open a support ticket with the error messages from the console.
Connection Problems
If players cannot connect to your server, work through these common causes:
Server Not Fully Started
- Verify the server is online and fully started in GPanel. The console should show a message indicating the server is ready for connections.
- If the server is stuck in a loading state or restarting in a loop, check the console for errors.
Version Mismatch
- The server and all connecting players must be running the same version of Nightingale.
- When the game updates, restart your server so SteamCMD downloads the latest version.
- Players should update their game through Steam before attempting to connect.
- The console may display version information on startup — compare this with the client version.
Incorrect IP or Port
- Confirm the player is using the correct IP address and port from GPanel's Network tab.
- See How to Find Your Server IP and Port for detailed instructions.
- Ensure the player is connecting to the game port, not the query port.
Password Issues
- If the server has a password set, make sure the player is entering it correctly (passwords are case-sensitive).
- To remove the password, clear the
PASSWORDstartup variable and restart.
Server Full
- If the server has reached the max player limit, additional players cannot join until someone disconnects.
- Increase
MAX_PLAYERin the Startup tab if you need more slots (may require more server resources). Note that increasing past 6 is unsupported.
Firewall and Port Configuration
- On Legion Hosting, firewall and port allocation are handled automatically by GPanel. You should not need to configure firewall rules manually.
- If you suspect a port issue, verify the port shown in GPanel's Network tab matches what the server is listening on in the console output.
- If players behind restrictive networks (corporate, school) cannot connect, they may need to use a VPN.
Performance Issues
If players experience lag, rubber-banding, or the server responds slowly, try the following optimizations:
Too Many Players
- Nightingale is designed for smaller multiplayer groups. Performance degrades as player count increases.
- If you are experiencing lag with many players, consider lowering
MAX_PLAYERin the Startup tab. - Each additional player adds load for character data, loaded realm chunks, and network synchronization.
Realm Complexity
- Large built structures and extensively modified realms increase the server's processing load.
- If a specific realm causes lag when entered, the builds in that realm may be overly complex.
- Encourage players to keep builds within reasonable sizes and avoid excessively complex contraptions.
Resource Usage
- Check GPanel's resource usage graphs for CPU and RAM consumption.
- If CPU is consistently above 90%, the server is overloaded. Reduce player count or consider a plan upgrade.
- If RAM usage is near the limit, the server may start swapping to disk, which causes severe performance drops.
- Contact support via a support ticket to discuss upgrading if resource limits are consistently being hit.
Save Corruption and Recovery
Save corruption can occur due to crashes, power loss, or bugs. Here is how to diagnose and recover.
Symptoms of Corruption
- Server crashes during world load with file read errors.
- Players spawn in unexpected locations or with missing inventory.
- Built structures or explored realms are missing after a restart.
- Console shows errors about invalid or unreadable save data.
Restoring from a Backup
- Stop the server in GPanel.
- Navigate to the save directory via the Files tab.
- Rename the current (corrupted) save folder to something like
SaveBackup_corruptedso you can attempt recovery later if needed. - Upload your backup save files to the original save directory path.
- Start the server. It should load the restored save.
Preventing Corruption
- Create regular backups, especially before game updates.
- Always stop the server cleanly through GPanel rather than letting it crash or force-stopping it.
- Avoid editing save files manually unless you know exactly what you are doing.
- Set up scheduled restarts in GPanel to periodically save and restart cleanly, reducing the window for corruption.
Game Updates Breaking the Server
Nightingale is an actively developed game, and updates can occasionally cause issues with dedicated servers.
After an Update
- Restart your server in GPanel. SteamCMD will automatically download the latest server files.
- If the server fails to start after the update, check the console for new error messages.
- Review the game's patch notes for any changes to server configuration or new requirements.
- Some updates may change config file formats or add new required settings. Compare your existing config with any example configs provided by the developers.
Rollback Not Possible
- SteamCMD always installs the latest version. You cannot roll back to a previous game version on the server.
- Players must also update their clients to match the server version.
- If an update introduces game-breaking bugs, monitor the official Nightingale channels for hotfixes, which are typically released quickly.
Admin and Host Controls
Nightingale's admin and host controls allow the server operator to manage players and the world.
Available Controls
- Kick players — Remove disruptive players from the server.
- Ban players — Permanently prevent specific players from joining.
- Server password — Set or change the server password at any time via GPanel startup variables.
- Admin commands — Check the console and game documentation for available server commands. These may change with updates.
Quick Reference: Common Issues
| Problem | Likely Cause | Solution |
|---|---|---|
| Server crashes on start | Corrupted save or failed update | Check logs, restore backup, or delete save for fresh world |
| Players cannot find server in browser | Server not fully started or query port issue | Wait for full startup, use direct connect as fallback |
| Players get "version mismatch" | Server or client not updated | Restart server (triggers SteamCMD update), update client |
| Severe lag for all players | Server overloaded (CPU/RAM) | Reduce MaxPlayers, check resource usage, consider upgrade |
| Lag in specific realm only | Complex builds in that realm | Simplify builds or avoid that realm |
| Player progress/builds missing | Save corruption or wrong save loaded | Restore from backup |
| Server stuck downloading on every start | SteamCMD validation issue | Open a support ticket |
Related Articles
- Nightingale Server Setup Guide — Initial setup, configuration, and connection instructions
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
- Server Startup Guide — General guide for starting any game server on Legion Hosting
Need More Help?
If you continue to experience issues with your Nightingale server, our support team is available to assist. Open a ticket at legionhosting.net/submitticket.php with your server IP, a description of the problem, and any relevant error messages from the GPanel console.