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 StarMade server on a VPS and how to fix them quickly, from crashes to lag → Learn more
Running your own StarMade 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 will encounter at some point.
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\starmade\logs\server.log. Restarts after crashes are logged in logs\supervisor.log.StarMade (starmade) - Start shortcut.StarMade (starmade) - 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 StarMade using the Game Server Installer, you can find it at C:\ZapX-GameServers\starmade\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. To do this, check server.log. Then check that the ports are open in the Windows Firewall and the network firewall for your VPS. You can find out which ports StarMade needs in StarMade: Setting 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 via Remote Desktop using the StarMade (starmade) - Start shortcut and monitor server.log. Common causes include a typo in server.cfg, a port already in use by another program, or not enough memory for Java. If you changed the configuration in server\StarMade\server.cfg, try reverting the change.
Nothing ends a great session faster than an unexpected crash. Possible causes include an outdated server version, 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, unexpected behavior, or startup problems, and often prevents players with a newer game version from connecting. Updates aren’t installed automatically. Open the Game Server Installer again and select StarMade; it will show Update. Alternatively, use the StarMade (starmade) - Update shortcut on your VPS. You’ll need to enter your Steam username and Steam password again; the installer doesn’t save them.
StarMade runs on Java and can only use as much memory as specified under Memory (GB) during installation. If you leave the field empty, it uses around 60% of your VPS’s memory. As your universe grows, that may not be enough. Run the installer again with a higher value, and make sure to leave enough memory for Windows.
Issues such as lag or delays often occur when the configuration isn’t suitable or the VPS doesn’t have enough resources.
Unsuitable settings can increase resource usage and cause lag. Check the values in server\StarMade\server.cfg, such as the number of player slots (MAX_CLIENTS). Stop the server before editing the file. You can change the server name and player slots through the installer; it overwrites these settings every time it runs.
StarMade requires at least 4 GB of memory. 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 memory or CPU usage is consistently maxed out, upgrading your VPS may help. Learn 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 How to identify 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 problems, contact our support team.
Regular backups can save you a lot of stress. Use the StarMade (starmade) - Backup shortcut to save your universe and settings as a ZIP file whenever you like, and use StarMade (starmade) - 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, restoring, and locked 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 for you every day and happy to help! 🙂
© 2026 ZAP-Hosting GmbH
Preferred source on Google
