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 Never Split the Party server on your VPS and how to fix them quickly, from crashes to lag → Learn more
Running your own Never Split the Party 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 cover the most common issues here and show you how to fix them quickly on your VPS.
FAQ
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 most important place to look is the server output: check the output in the window or terminal where the server is running. The example scripts from the wiki delete old log files every time the server restarts. To do this, connect to your VPS using Remote Desktop or SSH.
If your server doesn’t appear in the server list, first check whether it’s running and has finished starting up. Then check that the ports are open in your operating system’s firewall and in your VPS’s network firewall. For information about the ports Never Split the Party requires, see Never Split the Party: Set up a server on your VPS. Each server uses three consecutive UDP ports, starting with the value of -port; all three must be open. Also make sure there are no filters enabled in the server list that hide your server.
Start the server using your startup command or script and watch the output. Common causes include a port that’s already in use by another program, a port number that’s too low on Linux (use ports starting at, for example, 17000), or insufficient memory.
Nothing ends a good session faster than an unexpected crash. Possible causes include an outdated server version, faulty mods, an overloaded VPS, or a misconfiguration. If you set up a server manually, no one will restart it automatically after a crash unless you’ve configured an autostart or script yourself. Note: The server intentionally shuts down on its own after about 2.5 to 3 hours. This isn’t a crash; a restart loop will start it again automatically.
An outdated server often prevents players from connecting with a newer version of the game. If you’re using the restart loop from our guide, the server updates itself every time it restarts. Otherwise, stop the server and run the SteamCMD command from the installation guide again.
If you use mods or plugins, they’re a common cause of crashes, especially after a game update. Try disabling any additional content and starting with a minimal configuration. If the issue goes away, add the content back one item at a time, testing after each change. This will help you pinpoint what’s causing the problem.
Issues such as lag or delays often occur when the configuration isn’t right, the VPS doesn’t have enough resources, or mods are overloading the system.
Running too many servers on one VPS can increase resource usage and cause lag. If you’re running multiple instances, check that your VPS has enough resources for all of them.
The operating system and other programs on your VPS also need resources in addition to the server. You can check how heavily your VPS is being used in the ZapX dashboard under Monitoring. If memory or CPU usage stays at capacity, 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 that’s far from your players. First, check resource usage under Monitoring. If you suspect routing issues, see How to diagnose network issues with WinMTR/MTR. If you’re still having trouble, contact our support team.
Game servers are sometimes targeted by DDoS attacks that 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. Copy the server folder to a safe location regularly. 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 backups. Learn more in Daily backups, restores, 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 are happy to help! 🙂
© 2026 ZAP-Hosting GmbH
Preferred source on Google
