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 Starbound server on your VPS and how to fix them quickly, from crashes to lag → Learn more
Running your own Starbound 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
C:\ZapX-GameServers\starbound\logs\server.log. Restarts after crashes are recorded in logs\supervisor.log.Starbound (starbound) - Start shortcut..pak files from server\mods\ to another folder and start the server without mods. If it runs reliably, add the mods back one at a time.Starbound (starbound) - 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 first place to check is the server output: if you set up Starbound using the Game Server Installer, you can find it at C:\ZapX-GameServers\starbound\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 your VPS’s Network Firewall. You can find out which ports Starbound needs in Starbound: Set up a server on your VPS. Also make sure no filters are enabled in the server list that might be hiding your server.
Start the server via Remote Desktop using the Starbound (starbound) - Start shortcut and monitor server.log. Common causes include an error in starbound_server.config (the file is JSON, so even a missing comma can cause a problem), a port already in use by another program, or insufficient memory. If you changed the configuration in server\storage\starbound_server.config, try reverting the change.
Nothing ends a good 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 start the server yourself.
An outdated server can cause crashes, unexpected behavior, or startup issues, and often prevents players from connecting with a newer game version. Updates aren’t installed automatically. Open the Game Server Installer again and select Starbound; it will then show Update. Alternatively, use the Starbound (starbound) - Update shortcut on your VPS. You’ll need to enter your Steam username and Steam password again, as the installer doesn’t save them.
Faulty or outdated mods are often the cause of crashes, especially after a game update. As a test, move the .pak files from server\mods\ to another folder and start the server without mods. If that fixes the issue, add the mods back one at a time, testing after each one. This will help you identify exactly which mod is causing the problem.
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 lead to higher resource usage and lag. Check the values in server\storage\starbound_server.config, such as the number of player slots. Stop the server before editing the file. You can change the server name, player slots, and port in the installer; it overwrites these settings every time it runs.
Starbound needs at least 4 GB of memory. The operating system and other programs on your VPS also need resources. You can check your VPS’s resource usage 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 that’s far from your players. First, check resource usage under Monitoring. If you suspect routing issues, see Identify network issues with WinMTR/MTR. If you’re still having trouble, 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 Starbound (starbound) - Backup shortcut to back up your worlds and settings as a ZIP file at any time, and use Starbound (starbound) - 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 backups, and restricted actions.
These steps should help you resolve the 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
