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 One Hour One Life server on a VPS and how to fix them quickly, from login errors to lag → Find out more
Running your own One Hour One Life 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 show you the most common issues and how to fix them quickly on your VPS.
FAQ
screen or tmux session. If it’s running as a systemd service, you can find the output with journalctl.requireTicketServerCheck.ini to 0. Also check the password and address, make sure the port is correct, and confirm that the server and game are on the same version.git pull --tags in each of the minorGems, OneLife, and OneLifeData7 directories, then rebuild the server in the OneLife/server directory with make.maxPlayers.ini if needed. If that doesn’t help, upgrading your VPS is the easiest option.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.
Zappy knows this guide and answers you right in the chat.
Navigation
The causes of server issues are often not immediately obvious. The best place to start is the server output: Start the server in a screen or tmux session so you can view its output in the console at any time. If it’s running as a systemd service, you can find the output with journalctl. For instructions on setting up the server, see One Hour One Life: Set up a server on your VPS.
Players connect directly to your own server using the customServerAddress.ini and customServerPort.ini files. If this doesn’t work, first check that the server is running and that your players have the correct address and port. Then check that the port from port.ini (8005/TCP by default) is open in your operating system’s firewall and in your VPS’s network firewall.
From the OneLife/server directory, start the server manually with ./OneLifeServer and watch the output. If linked game data (such as objects or transitions) is missing, repeat the linking steps from the installation guide. Common causes include a typo in a file in the settings directory, a port that’s already in use by another program, or insufficient memory. If you’ve changed the configuration, try reverting the change temporarily.
By default, the server checks logins against the official ticket server (requireTicketServerCheck.ini). For a private server, the developer sets this value to 0 in their test script. If you require a password (requireClientPassword.ini), it must exactly match clientPassword.ini in your players’ serverPassword.ini file. The server and game should also be on the same version.
Nothing ends a good session faster than an unexpected crash. Causes can include an outdated server version, faulty mods, an overloaded VPS, or a misconfiguration. To make sure your server starts back up automatically after a crash, you can run it as a systemd service with automatic restart enabled.
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. Stop the server, run git pull --tags in the minorGems, OneLife, and OneLifeData7 directories to get the latest version, then rebuild the server with make.
Crashes are often caused by faulty or outdated mods and extensions, 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 step at a time, testing after each step. This will help you pinpoint the cause.
Issues such as lag or delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or extensions are overloading the system.
Unsuitable settings can increase resource usage and cause lag. Check the values in the OneLife/server/settings/ directory, such as the maximum number of players in maxPlayers.ini. Each file should contain exactly one value. Restart the server after making a change.
The amount of memory and CPU your One Hour One Life 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 can 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 Diagnosing 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. Before updating, back up the OneLife/server directory, which contains your settings and world. 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. Find out more in Daily backups, restores, and restricted actions.
These steps should help you resolve your issue. If they don’t, feel free to contact our support team: Just 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
