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 Hurtworld server on a VPS—and how to fix them quickly, from crashes to lag → Find out more
Running your own Hurtworld 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 eventually.
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
-logfile when starting the server—in our guide, this is gamelog.txt in the server folder.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 writes its output to the file you specify with -logfile when you start it—in our guide, this is gamelog.txt in the server folder. Connect to your VPS using Remote Desktop or SSH to access it.
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 your VPS’s network firewall. You can find out which ports Hurtworld needs in Hurtworld: Set up a server on your VPS. In addition to the game port, the query port (12881 by default) must also be open, or the server won’t appear in the list. Also make sure that no filters in the server list are hiding your server.
Start the server using your startup command (start.bat or ./Hurtworld.x86_64 on Linux) and monitor gamelog.txt. Common causes include a typo in the startup command or autoexec.cfg, 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 resolves the issue.
Nothing ends a good session faster than an unexpected crash. Causes can include an outdated server version, faulty mods, an overloaded VPS, or a configuration error. If you set up a server manually, it won’t restart automatically after a crash unless you’ve configured an auto-start or script yourself.
An outdated server can cause crashes and often prevents players from connecting with a newer game version. Updates aren’t installed automatically. 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 additional content and starting with a minimal configuration. If the problem goes away, add the content back one item at a time and test after each step. This will help you identify exactly 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 mods overload the system.
Unsuitable settings can increase resource usage and cause lag. Check the values in your startup command and in autoexec.cfg, such as maxplayers. Restart the server after making changes.
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 is consistently maxed out, upgrading your VPS can help. Find out more in Upgrades, downgrades, renewals, and cancellations.
Ping spikes and lag are usually caused by limited VPS resources, a high player count, 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 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. Stop the server and 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. Find out more in Daily backups, restoring, 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 for you every day and will be happy to help! 🙂
© 2026 ZAP-Hosting GmbH
Preferred source on Google
