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 Broke Protocol server on your VPS and how to fix them quickly, from crashes to lag → Learn more
Running your own Broke Protocol 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 typical challenges that every server owner encounters at some point.
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
Server.bat (Windows), or in the screen session for ./start.sh (Linux).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 aren’t always immediately obvious. The best place to start is the server output: check the output that appears after starting the server with Server.bat (Windows) or ./start.sh (Linux). On Linux, it runs in a screen session. Connect to your VPS via Remote Desktop or SSH to access it.
If your server doesn’t appear in the server list, first check that it’s running and has finished starting. Then check that the ports are open in your operating system’s firewall and in your VPS’s network firewall. Find out which ports Broke Protocol requires in Broke Protocol: Set up a server on your VPS. If everything is configured correctly, your server will appear in the server list with a “+”. Also allow pings (ICMP), otherwise the list won’t show a ping. Make sure there aren’t any active filters in the server list hiding your server.
Start the server with Server.bat (Windows) or ./start.sh (Linux) and monitor the output. The first time a map starts, the server generates a NavMesh, which takes about 5 to 10 minutes and isn’t an error. Common causes of actual startup issues include a syntax error in settings.json or groups.json, a port that’s already in use, or not enough memory. On Linux, screen must also be installed.
Nothing ends a great session faster than an unexpected crash. Possible causes include an outdated server version, faulty mods, an overloaded VPS, or a configuration issue. If you set up the server manually, no one will automatically restart it after a crash unless you’ve set up an automatic startup process or script yourself.
An outdated server can cause crashes and prevent players with a newer game version from connecting. Updates aren’t installed automatically. Download the new version from brokeprotocol.com, back up your configuration files, and replace the remaining server files.
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 problem goes away, add the content back one step at a time, testing after each step. This will help you identify exactly what’s causing the issue.
Issues such as lag or delays often occur when the configuration isn’t suitable, the VPS doesn’t have enough resources, or mods overload the system.
Unsuitable settings can lead to higher resource usage and lag. Check the values in settings.json, such as the player slots (Players) and the content transfer rate (maxTransferRate). Stop the server before editing the file.
The developer recommends around 3 to 4 GB of memory for a Broke Protocol server. 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 remains maxed out, upgrading your VPS can help. Find out 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 resource usage under Monitoring. If you suspect routing issues, Diagnose network issues with WinMTR/MTR can help. If you’re still having trouble, 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 issues, contact our support team.
Regular backups can save you a lot of stress. Back up the server folder regularly, especially settings.json, groups.json, and your text files. 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. Find out more in Daily backups, restoration, and restricted actions.
These steps should help you resolve your issue. If they don’t, don’t hesitate to contact our support team: simply create a support chat in your ZapX customer account. We’re here for you every day and will be happy to help! 🙂
© 2026 ZAP-Hosting GmbH
Preferred source on Google
