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
AnalyticsMarketingPersonalizationExternal media
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 Last Oasis server on a VPS and how to fix them quickly, from crashes to lag → Learn more
10 November 20264 min read0 Views0 helpful
Introduction
Running your own Last Oasis 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 at some point.
To help you spend less time troubleshooting, we’ll show you the most common issues here and how to fix them quickly on your VPS.
FAQ
Frequently asked questions
Check the server output (using the -log startup parameter) and the MyRealm dashboard, which shows all the servers in your Realm.
Check the Customer Key and Provider Key in the startup file, make sure your Realm is saved and the Oasis is activated, and confirm that the ports are open in the Windows Firewall and your VPS’s network firewall.
In the ZapX dashboard, check under Monitoring whether your VPS’s memory or CPU is maxed out, and reduce the player count or number of mods if needed. If that doesn’t help, upgrading your VPS is the simplest option.
Each server needs its own values for -identifier, -port, and -QueryPort, as well as its own resources. Check usage in the dashboard under Monitoring.
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
Last Oasis
Issues and solutions
The causes of server issues are not always immediately obvious. The best place to start is the server output: Start the server with the -log parameter, as shown in the official startup command, and monitor its output. You can also see whether the server has connected to your Realm in the MyRealm dashboard. To do this, connect to your VPS using Remote Desktop.
General
Server not visible
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 the Windows Firewall and the network firewall for your VPS. See Last Oasis: Set up a server on your VPS for the ports Last Oasis requires. In MyRealm, check that your Realm is saved and the Oasis is activated. For -OverrideConnectionAddress, enter your VPS’s public IP address. Also make sure there are no filters active in the server list that could be hiding your server.
Server won’t start
Start the server using your startup file (for example, server1.bat) and monitor the output. Common causes include an incorrect or missing -CustomerKey or -ProviderKey, a Realm without an active Oasis, a port already in use by another server, or insufficient memory. If you’re running multiple servers, each one needs its own values for -identifier, -port, and -QueryPort.
Crashes
Nothing ruins a good session faster than an unexpected crash. Possible causes include an outdated server version, faulty mods, an overloaded VPS, or a misconfiguration. If you set up a server manually, it won’t restart automatically after a crash unless you’ve configured an autostart or script yourself.
Keep your server up to date
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 instructions again.
Faulty mods
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 issue goes away, add the content back one step at a time and test after each step. This helps you identify exactly what’s causing the problem.
Performance
Issues such as lag or delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or mods are overloading the system.
Poor server configuration
Unsuitable settings can lead to higher resource usage and lag. Check the player slots (-slots, which the developers recommend keeping at 100 or fewer) and your Realm settings in MyRealm. Restart the server after making changes.
Not enough VPS resources
The operating system and other programs on your VPS also need resources, in addition to the server. If you’re running multiple Oases on one VPS, each server needs its own resources. You can check how heavily your VPS is being used in the ZapX dashboard under Monitoring. If the memory or CPU is consistently maxed out, upgrading your VPS may help. Learn more in Upgrade, Downgrade, Renewal, and Cancellation.
Network
Ping spikes, lag, and network delays
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 resource usage under Monitoring. If you suspect routing issues, see Identify network issues with WinMTR/MTR. If you still need help, contact our support team.
DDoS and other network threats
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 issues, contact our support team.
Preventive measures
Regular backups can save you a lot of stress. Back up the server folder regularly, especially your startup files (*.bat). 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. Learn more in Daily backups, restoration, and restricted actions.
Conclusion
These steps should help you resolve your 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 for you every day and happy to help! 🙂
Server hosting from €2.49 / month, online instantly, DDoS protection included.