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 issues with your No One Survived server on a VPS and how to fix them quickly, from lost progress to lag → Learn more
Running your own No One Survived server on a VPS is a lot of fun, but it also means taking responsibility when something goes wrong. Crashes, lag, and configuration issues are common challenges that every server owner encounters sooner or later.
To help you spend less time troubleshooting, we’ll show you the most common issues and how to fix them quickly on your VPS.
FAQ
C:\ZapX-GameServers\no-one-survived\logs\server.log. Restarts after crashes are recorded in logs\supervisor.log.No One Survived (no-one-survived) - Start shortcut.No One Survived (no-one-survived) - 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 issues aren’t always immediately obvious. The best place to start is the server output: if you set up No One Survived with the Game Server Installer, you’ll find it at C:\ZapX-GameServers\no-one-survived\logs\server.log. The installer records restarts after crashes in logs\supervisor.log.
If your server doesn’t appear in the server list, first check whether it’s running and has finished starting up. Check server.log to confirm. Try connecting directly using the IP address and port. Then check that the ports are open in the Windows Firewall and your VPS’s Network Firewall. You can find out which ports No One Survived needs in No One Survived: Set up a server on your VPS. Also make sure there aren’t any filters enabled in the server list that are hiding your server.
Start the server using the No One Survived (no-one-survived) - Start shortcut via Remote Desktop and monitor server.log. Common causes include a typo in Game.ini or Engine.ini, a port already in use by another program, or insufficient memory. If you’ve changed the configuration, try reverting the change to see if that fixes the issue.
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 configuration error. The installer automatically restarts your server after a crash. If it crashes several times within a short period, 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. Create a backup first, because the server will stop immediately when the update begins. Then reopen the Game Server Installer and select No One Survived; it will show Update. Alternatively, use the No One Survived (no-one-survived) - Update shortcut on your VPS.
No One Survived only saves progress through its own autosave feature. If the server is stopped, restarted, or crashes, anything since the last autosave is lost. This isn’t an issue with your server. Create a backup before planned stops and updates, and use No One Survived (no-one-survived) - Restore to restore an earlier save if needed.
Issues like lag or delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or additional content overloads the system.
Unsuitable settings can increase resource usage and cause lag. Check the settings in server\WRSH\Saved\Config\WindowsServer\Game.ini, such as player slots and zombie settings. Stop the server before editing the file.
No One Survived needs at least 6 GB of memory. The operating system and other programs on the VPS need additional resources. You can check how heavily your VPS is being used in the ZapX dashboard under Monitoring. If memory or CPU usage is consistently maxed out, upgrading your VPS can help. Find out more in Upgrades, downgrades, renewals, and cancellations.
Ping spikes and lag are usually caused by limited VPS resources, a high number of players, or a server location far from your players. First, check resource usage under Monitoring. If you suspect routing issues, see Diagnose network issues with WinMTR/MTR. If you still need help, contact our support team.
Game servers are sometimes targeted by DDoS attacks, which flood the server with traffic. Your VPS is protected by our DDoS protection. You can view past attacks in the ZapX dashboard under your VPS’s DDoS Manager, if it’s available at your location. If you suspect an attack is causing issues, contact our support team.
Regular backups can save you a lot of stress. Use the No One Survived (no-one-survived) - Backup shortcut to save your world and server settings as a ZIP file at any time, and No One Survived (no-one-survived) - Restore to restore them. Always create a backup before an update, as the server will stop without saving. Your entire VPS is also backed up automatically every day. With an active ZapX Pass, you can restore these backups yourself and create your own. Find out more in Daily backups, restoring data, and restricted actions.
These steps should help you solve your issue. If they don’t, don’t hesitate to contact our support team: simply start a support chat in your ZapX customer account. We’re here every day and happy to help! 🙂
© 2026 ZAP-Hosting GmbH
Preferred source on Google
