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 open.mp server on a VPS and how to fix them quickly, from startup errors to lag → Learn more
Running your own open.mp 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 eventually encounters.
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
C:\ZapX-GameServers\openmp\logs\server.log. Restarts after crashes are recorded in logs\supervisor.log.open.mp (openmp) - Start shortcut.open.mp (openmp) - 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 often not immediately obvious. The best place to start is the server output: if you set up open.mp with the Game Server Installer, you can find it at C:\ZapX-GameServers\openmp\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 that the gamemode loaded without errors. Check server.log for this. Also make sure that announce and enable_query are set to true in config.json. Then check that the ports are open in the Windows firewall and your VPS’s network firewall. For the ports open.mp needs, see open.mp: Set up a server on your VPS. Also make sure there are no active server list filters hiding your server.
Start the server using the open.mp (openmp) - Start shortcut over Remote Desktop and monitor server.log. Common causes include an error in config.json (such as a missing comma), a gamemode listed in pawn.main_scripts that isn’t present as an .amx file in the gamemodes folder, an incompatible plugin, or a port already in use by another program. If you’ve made any changes, try reverting them.
Nothing ends a good session faster than an unexpected crash. Causes may include an outdated server version, faulty scripts or plugins, an overloaded VPS, or a misconfiguration. The installer automatically restarts your server after a crash. If it crashes several times in a short period, the installer gives up. You’ll then need to fix the cause and start the server yourself.
Updates aren’t installed automatically. Open the Game Server Installer again and select open.mp. It will show Update and install the latest version of open.mp. Alternatively, use the open.mp (openmp) - Update shortcut on your VPS. After an update, check that your plugins are still compatible with the new version.
Crashes are often caused by faulty or outdated scripts and plugins. Try disabling additional filterscripts and plugins in config.json and start with the default gamemode. If the issue goes away, add them back one at a time and test after each step. This helps 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 additional content is overloading the system.
Unsuitable settings can lead to higher resource usage and lag. Check the values in server\config.json, such as the player limit (max_players) and number of NPCs (max_bots). Stop the server before editing the file. However, lag in open.mp is often caused by the gamemode itself, for example, timers that run too frequently.
open.mp requires at least 2 GB of RAM. The operating system and other programs on the VPS need additional resources. You can see how heavily your VPS is being used under Monitoring in the ZapX dashboard. If RAM or CPU usage is consistently maxed out, upgrading your VPS may help. Learn more in Upgrade, downgrade, renewal, and cancellation.
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 usage under Monitoring. If you suspect routing issues, see How to identify network issues with WinMTR/MTR. If you still need help, 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. Use the open.mp (openmp) - Backup shortcut to back up config.json, bans.json, your gamemodes, filterscripts, script data, and plugins as a ZIP file at any time. Use open.mp (openmp) - Restore 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 backups. Learn more in Daily backups, restoring data, and restricted actions.
These steps should help you resolve your 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
