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 Subsistence server on a VPS and how to fix them quickly, from crashes to lag → Learn more
Running your own Subsistence 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 sooner or later.
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\subsistence\logs\server.log. Restarts after crashes are logged in logs\supervisor.log.Subsistence (subsistence) - Start shortcut.Subsistence (subsistence) - 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 are not always immediately obvious. The best place to start is the server output: if you set up Subsistence using the Game Server Installer, you’ll find it at C:\ZapX-GameServers\subsistence\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. Check server.log to confirm. Then check that the ports are open in the Windows Firewall and your VPS’s network firewall. The ports required by Subsistence are listed in Subsistence: Set up a server on your VPS. Also make sure there are no active filters in the server list that are hiding your server.
Start the server using Remote Desktop and the Subsistence (subsistence) - Start shortcut, then monitor server.log. Common causes include a typo in UDKDedServerSettings.ini, a port already in use by another program, or insufficient memory. If you’ve changed the configuration in server\UDKGame\Config\UDKDedServerSettings.ini, try reverting the change.
Nothing ends a good session faster than an unexpected crash. Causes can include an outdated server version, a VPS under heavy load, 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 issues, and often prevents players with a newer game version from connecting. Updates aren’t installed automatically. Open the Game Server Installer again and select Subsistence; it will then show Update. Alternatively, use the Subsistence (subsistence) - Update shortcut on your VPS.
The installer rewrites the server name, passwords, and player slots in UDKDedServerSettings.ini every time it runs, including during an update. So change these values in the installer, not in the file. The installer also manages the query port, so only change it using the Query Port field.
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\UDKGame\Config\UDKDedServerSettings.ini. Stop the server before editing the file. Change the server name, passwords, and player slots in the installer, as it rewrites these values every time it runs.
Subsistence requires at least 4 GB of memory. The operating system and other programs on the VPS need additional resources. You can check how heavily your VPS is loaded under Monitoring in the ZapX dashboard. If the memory or CPU 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 the load under Monitoring. If you suspect routing issues, see Identify network issues with WinMTR/MTR. If you still need help, 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. Use the Subsistence (subsistence) - Backup shortcut to back up your world and settings as a ZIP file at any time, and the Subsistence (subsistence) - Restore shortcut 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, restores, and blocked 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
