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 DDraceNetwork server on a VPS and how to fix them quickly, from crashes to lag → Learn more
Running your own DDraceNetwork 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
logfile. In the example configuration, this is autoexec_server.log.myServerconfig.cfg and custom maps regularly. Your entire VPS is also backed up daily, and 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: the server displays its output in the window or terminal and also writes it to the file specified by logfile (in the example configuration, autoexec_server.log). To access it, connect to your VPS via Remote Desktop or SSH.
If your server doesn’t appear in the server list, first check that 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 the ports DDraceNetwork needs, see DDraceNetwork: Set up a server on your VPS. Your server will only appear in the public list if sv_register 1 is set. Also, set sv_port explicitly; otherwise, the server will choose an available port between 8303 and 8310. Make sure there are no filters enabled in the server list that hide your server.
Start DDNet-Server again and monitor the output. Common causes include a typo in your configuration, a map that can’t be found, or a port that’s already in use by another program. If you changed the configuration, try reverting the change temporarily.
Nothing brings a great session to an end faster than an unexpected crash. Causes can include an outdated server version, faulty mods, an overloaded VPS, or a misconfiguration. If a server you set up manually crashes, it won’t restart automatically unless you’ve set up an auto-start option or script yourself.
An outdated server can cause unexpected behavior and often prevents players with newer versions from using all the features. Updates aren’t installed automatically. Download the new version from ddnet.org and replace the server files. Your settings in myServerconfig.cfg will be preserved.
If you use mods or plugins, they’re a common cause of crashes, especially after a game update. Try disabling additional content and starting with a minimal configuration. If that fixes the problem, add the content back one step at a time and test after each step. This will help you identify exactly what’s causing the issue.
Issues like lag or delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or mods overload the system.
Unsuitable settings can increase resource usage and cause lag. Check the values in your myServerconfig.cfg, such as sv_max_clients. Restart the server after making changes.
The operating system and other programs on the VPS also need resources. You can check how heavily your VPS is being used in the ZapX dashboard under Monitoring. If the memory or CPU 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 resource usage under Monitoring. If you suspect routing issues, see 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 problems, contact our support team.
Regular backups can save you a lot of stress. Back up your myServerconfig.cfg and custom maps 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, restoring data, and restricted actions.
These steps should help you solve your issue. If they don’t, feel free 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
