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 DeadPoly server on a VPS and how to fix them quickly, from crashes to lag → Learn more
Running your own DeadPoly server on a VPS is a lot of fun, but it also means taking responsibility when things go 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 cover the most common issues and how to fix them quickly on your VPS.
FAQ
C:\ZapX-GameServers\deadpoly\logs\server.log. Restarts after crashes are logged in logs\supervisor.log.DeadPoly (deadpoly) - Start shortcut.DeadPoly (deadpoly) - Backup shortcut on your VPS to back up your world and Game.ini. 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 DeadPoly using the Game Server Installer, you’ll find it at C:\ZapX-GameServers\deadpoly\logs\server.log. The installer logs restarts after crashes in logs\supervisor.log.
If your server doesn’t appear in the server list, first check that it’s running and has finished starting up. Check server.log; startup takes 2 to 3 minutes. Then check that the port is open in the Windows Firewall and in your VPS’s network firewall. You can find out which port to use in DeadPoly: Set up a server on your VPS. Special characters in the server name can also prevent it from appearing in the list.
Start the server via Remote Desktop using the DeadPoly (deadpoly) - Start shortcut and monitor server.log. Startup takes 2 to 3 minutes. Common causes include a typo in Game.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, changed game 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 need to fix the cause and start the server yourself.
An outdated server can cause crashes, unexpected behavior, 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 DeadPoly; it will then show Update. Alternatively, use the DeadPoly (deadpoly) - Update shortcut on your VPS.
Crashes after a change are often caused by additional or modified files in the server folder, especially after a game update. Try removing any additional content and starting with a minimal configuration. If the issue goes away, add the changes back one at a time and test after each step. This helps you pinpoint what’s causing the problem.
Issues such as lag or delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or too many players are online at once.
Unsuitable settings can lead to higher resource usage and lag. Check the values in server\DeadPoly\Saved\Config\WindowsServer\Game.ini, such as the player slots. You can change the server name, player slots, and game mode through the installer, which overwrites them each time it runs.
DeadPoly requires at least 7 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. Learn more in Upgrade, downgrade, renewal, and cancellation.
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 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 occasionally 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 DDoS Manager for your VPS in the ZapX dashboard, 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 DeadPoly (deadpoly) - Backup shortcut to save your world and Game.ini as a ZIP file at any time, and use DeadPoly (deadpoly) - Restore to restore them. 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. Learn more in Daily backups, restoration, and restricted actions.
These steps should help you resolve 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
