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 problems with your Staxel server on a VPS and how to fix them quickly, from startup issues to lag → Learn more
Running your own Staxel server on a VPS is a lot of fun, but it also means taking responsibility when something goes wrong. Crashes, lag, and configuration problems are common challenges that every server owner eventually encounters.
To help you spend less time troubleshooting, we’ll show you the most common problems and how to fix them quickly on your VPS.
FAQ
bin\\Staxel.ServerWizard.exe or bin\\Staxel.Server.exe and watch the server window. If Staxel.Server can’t be started, verify the files using the SteamCMD command from the installation instructions (validate).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 problems aren’t always immediately obvious. The best place to start is the server output: the server window shows you what it’s doing. Connect to your VPS using Remote Desktop to view it. For instructions on setting up your server, see Staxel: Set up a server on your VPS.
If your server doesn’t appear in the server list, first check that it’s running and set to Public. Your players can also connect directly using the IP address and port, without using the server list. Then check that the game port (default 38465/TCP) is open in your operating system’s firewall and your VPS’s network firewall. Also make sure no filters are enabled in the server list that might hide your server.
Start the server manually using bin\\Staxel.ServerWizard.exe or bin\\Staxel.Server.exe and watch the server window. If Windows says that Staxel.Server can’t be started, verify the files using the SteamCMD command from the installation instructions (validate). Common causes include a typo in your startup parameters or the Server Wizard, a port already in use by another program, or insufficient memory. If you’ve changed the configuration, try reverting the change to see if that fixes the problem.
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. To get your server running again after a crash, restart it—for example, using the task in Task Scheduler. Otherwise, always shut it down with Ctrl+C and wait for it to save.
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. Stop the server and run the same SteamCMD command you used during installation. You’ll need to sign in again with the Steam account that owns Staxel.
Crashes are often caused by faulty or outdated mods and add-ons, especially after a game update. Try disabling any additional content and starting with a minimal configuration. If the problem goes away, add the content back step by step, testing after each change. This will help you identify what’s causing the issue.
Problems such as lag or delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or add-ons are overloading the system.
Unsuitable settings can lead to higher resource usage and lag. Check your settings in the Server Wizard or your startup parameters, such as the Player Limit. Restart the server after making a change.
The amount of memory and CPU your Staxel server needs depends on the number of players and your settings. The operating system and other programs on the VPS also need resources. You can see 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 large number of players, or a server location far from your players. First, check usage under Monitoring. If you suspect routing problems, see Diagnose network issues with WinMTR/MTR. If you still need help, contact our support team.
Game servers are sometimes 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. Before updates, back up the installation folder containing your worlds, ideally with the server stopped. In addition, your entire VPS is automatically backed up daily. 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 problem. If they don’t, don’t hesitate to contact our support team: just 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
