You decide which services we may enable for analytics, personalization, and external content.
We use cookies and similar technologies on our website to personalize content, embed external media, and better understand how individual areas are used.
Necessary cookies
These entries support essential functions such as security, stability, and form processing.
Optional sections
Your data may be processed with your consent or on the basis of legitimate interests. In the cookie settings, you can reject or explicitly allow each optional category.
Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.
You can reopen and change your selection at any time. · 1.0.2
The most common problems with your Nightingale server on a VPS and how to fix them quickly, from a long first startup to lag → Learn more
Running your own Nightingale server on a VPS is great fun, but it also means taking responsibility when something goes wrong. Crashes, lag, and configuration issues are common challenges that every server owner eventually encounters.
To help you spend less time troubleshooting, we’ll cover the most common problems here and show you how to fix them quickly on your VPS.
FAQ
C:\ZapX-GameServers\nightingale\logs\server.log. The game also writes to server\NWX\Saved\Logs\NWX.log. Restarts after crashes are logged in logs\supervisor.log.Nightingale (nightingale) - Start shortcut.Nightingale (nightingale) - Backup shortcut on your VPS. Your entire VPS is also backed up daily. With an active ZapX Pass, you can restore these backups yourself.Feedback
Was this article helpful?
Your feedback helps us prioritize and improve content.
0 of 0 Users found this article helpful.
Personal support
Need more help than the guide provides?
Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.
Navigation
The causes of server problems aren’t always immediately obvious. The best place to start is the server output: if you set up Nightingale using the Game Server Installer, you’ll find it at C:\ZapX-GameServers\nightingale\logs\server.log. The game itself also writes to server\NWX\Saved\Logs\NWX.log. The installer logs restarts after crashes in logs\supervisor.log.
If no one can connect, first check whether the server has finished starting. During the first startup in particular, it takes around 5 minutes to build its world. Only the Going ready line in NWX.log indicates that it’s accepting players. Then check that the ports are open in the Windows Firewall and your VPS’s network firewall. You can find the ports Nightingale needs in Nightingale: Set up a server on your VPS. It’s best to connect directly using the IP address and port.
Start the server via Remote Desktop using the Nightingale (nightingale) - Start shortcut, and monitor server.log. Common causes include a typo in ServerSettings.ini, a port already in use by another program, or insufficient memory. If you’ve changed the configuration, try reverting the change.
Nothing ends a good session faster than an unexpected crash. Possible causes include an outdated server version, corrupted server files, an overloaded VPS, or a misconfiguration. The installer automatically restarts your server after a crash. If it crashes several times in quick succession, the installer gives up. You’ll then need to fix the cause and restart the server yourself.
An outdated server can cause crashes or startup issues and often prevents players with a newer game version from connecting. Updates aren’t installed automatically. Open the Game Server Installer again and select Nightingale; it will then show Update. Alternatively, use the Nightingale (nightingale) - Update shortcut on your VPS.
If files are missing after an interrupted download, the server often won’t start properly. An update checks the server files through SteamCMD and downloads any missing or corrupted files again. Before doing this, back up your Realms using the Nightingale (nightingale) - Backup shortcut.
Problems such as lag or delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or additional content is overloading the system.
Check the values in server\NWX\Config\ServerSettings.ini. Stop the server before editing the file. Nightingale supports a maximum of six players.
Nightingale requires at least 7 GB of memory. The server uses a lot of memory while building the world. The operating system and other programs on the VPS also need resources. You can see how heavily your VPS is loaded in the ZapX dashboard under Monitoring. If memory or CPU usage is consistently maxed out, upgrading your VPS can help. Learn more in Upgrades, downgrades, renewals, and cancellations.
Ping spikes and lag are usually caused by limited VPS resources, a large number of players, or a server location far from your players. First, check the load under Monitoring. If you suspect routing issues, see Diagnosing network issues with WinMTR/MTR. If you still need help, contact our support team.
Game servers are occasionally targeted by DDoS attacks that flood the server with traffic. Your VPS is protected by our DDoS protection. You can see past attacks in the DDoS Manager for your VPS in the ZapX dashboard, if it’s available at your location. If you suspect an attack is causing problems, contact our support team.
Regular backups can save you a lot of stress. Use the Nightingale (nightingale) - Backup shortcut to back up your Realms, characters, and settings as a ZIP file whenever you like. Use Nightingale (nightingale) - Restore to restore them. In addition, your entire VPS is backed up automatically every day. With an active ZapX Pass, you can restore these backups yourself and create your own. Learn more in Daily backups, restoring, and restricted actions.
These steps should help you solve your problem. If they don’t, don’t hesitate to contact our support team: simply create a support chat in your ZapX customer account. We’re here for you every day and will be happy to help! 🙂
© 2026 ZAP-Hosting GmbH
Preferred source on Google
