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 Nienix server on a VPS and how to solve them quickly, from missing game sessions to lag → Learn more
Running your own Nienix 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 solve them quickly on your VPS.
FAQ
Logs\log.txt (Linux: Logs/log.txt). Older logs are stored alongside it as log.1.txt, log.2.txt, and so on.start command. Use stats to check whether a session is running, and make sure the port shown by config is open in the firewalls.2320610). Updates aren’t installed automatically.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 often not immediately obvious. The best place to start is the server output: the Nienix Dedicated Server writes its log to Logs\log.txt (Linux: Logs/log.txt) in the server folder. You can also see what the server is doing in its console window. For instructions on setting up the server, see Nienix: Set up a server on your VPS.
If your server doesn’t appear in the game, first check whether it’s running and whether a game session is active. After startup, the server only loads its content; a session starts only when you run the start command (or add start to your init_commands.txt). Use stats to check whether a session is running. Then check that the port shown by the config command is open in your operating system’s firewall and in your VPS’s network firewall. Also make sure there aren’t any filters enabled in the server list that are hiding your server.
Start the server manually from the server folder (NienixDedicatedServer.exe or ./NienixDedicatedServer) and check the output in the console and in log.txt. Common causes include a typo in your init_commands.txt, 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 issue.
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 have your server restart automatically after a crash, you can run it as a systemd service with automatic restarts on Linux. On Windows, you’ll need to restart it manually after a crash.
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 and run the same SteamCMD command you used during installation (App ID 2320610).
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 issue goes away, add the content back one piece at a time and test after each step. This helps you pinpoint what’s causing the problem.
Issues like lag or delays often occur when the configuration isn’t right, the VPS doesn’t have enough resources, or extensions are overloading the system.
Incorrect settings can lead to higher resource usage and lag. Use the config command to check the current values, such as the maximum number of players (max_players) or the number of bots (bots_auto, clear_bots), and adjust them in your init_commands.txt if needed.
How much memory and CPU your Nienix 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 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. Learn more in Upgrades, downgrades, renewals, and cancellations.
Ping spikes and lag are usually caused by limited resources on the VPS, a high number of players, or a server location 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 sometimes targeted by DDoS attacks, which flood the server with traffic. Your VPS is protected by our DDoS protection. You can see 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. Back up the server folder before updates, especially your init_commands.txt. 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, restores, and restricted actions.
These steps should help you solve the issue. 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 for you every day and happy to help! 🙂
© 2026 ZAP-Hosting GmbH
Preferred source on Google
