If your game server is down, won't start, or keeps crashing, there can be many reasons. The important thing is not to try restarting it right away, but to check the log file first. It usually contains error messages that explain exactly why the server crashed. If you restart the server immediately, a new log file will be created and the old one will be deleted. Unfortunately, you won't be able to see any errors after that.
Not every outage is caused by your server. If a host or the network at a location goes down, several servers are usually affected at the same time. Typical signs include the server not starting at all, the console and log file remaining empty, or the server appearing online in the web interface but being unreachable in-game.
In that case, check our status page first. You can also get outage notifications for your locations sent directly to you; see Set up notifications.
Don't reset anything during an outage: Don't restore a backup or reinstall the server while there's an outage. This won't solve the problem and could cost you your data. Once the outage has been resolved, your server will usually work as usual again.
You can easily open the log file from the menu on the left.
Then you can view it by clicking the green eye icon. Make sure you always open the latest log file.
You can identify it by its date or name.
Once you've opened it, check it for errors (errors usually contain words like "Error", "Cant find", or "Couldnt load"). The most important lines are the ones just before the crash.
A typical example is a FiveM server with an incorrect server license key: the log file reports a license key error, and the server stops starting.
You can then search for the error on Google, for example, to see if it's known. This is usually a quick way to find the cause.
If you can't find anything about the error, you can send it to us as text or a screenshot in Live Chat.
Unfortunately, this can happen too. If the log file is empty, it couldn't be created because the server crashed immediately or was deleted by a restart. In that case, your only option is to try restarting the server and hope the error appears again or the server starts working again.
A typical scenario: you click Start, the server gets stuck on “Initializing” or goes back offline after a few seconds. The most common reasons are:
- Missing or incompatible mods and plugins: This is the most common cause. A dependency (a mod required by another mod) is often missing, or a mod isn't compatible with your server version. The log usually names the mod. Upload the missing mod using SFTP or remove the mod you added most recently.
- An error in a configuration file: After you change the config, even an invalid value or typo can stop the server from starting. Undo your last change.
- After a game update: Mods, plugins, or your world may no longer be compatible with the new version. Update them or wait until compatible versions are released.
- Installation or update still in progress: Don't start the server while an installation or update is running. Otherwise, game files may be missing. The first start after installation may also take a little longer.
- Invalid license key or server token: Games that require their own key won't start without a valid one.
- Changed ports: If you changed the ports in the configuration file, the web interface may remain stuck on “Initializing” even though the server is running. Use the ports assigned to your server during setup.
The most important rule: undo your last change first, then test only one thing at a time.
- Memory or CPU at its limit: Check your server's resource usage. If the RAM is full, the server crashes and is automatically restarted. If the CPU is under constant load, the server lags. ZapX won't suspend your server for this; it is only stopped automatically when its storage space is 95% full. See Fixing lag, CPU, and RAM issues to find and resolve the cause.
- Crashes at regular intervals (e.g. every 5–10 minutes): This usually points to a script, mod, or plugin with a memory leak. Disable mods one at a time until the crashes stop.
- Crashes as soon as someone joins: The game save is often corrupted, or a mod is faulty. Restoring a backup from before the problem usually helps.
- Only the game crashes, not the server: If the server keeps running and only your game crashes, the cause is usually your game or modpack version. It must match the server version exactly.
- Server is consistently underpowered: If your server regularly reaches its limits with your mods and players, an upgrade/downgrade to more RAM or CPU can help.
- Rule out an outage: Check the status page.
- Save the log file: Open the current log file and copy the last error lines before restarting.
- Identify your last change: What did you change most recently (mod, plugin, config, game update)? Undo that change first.
- Test mods and plugins individually: Disable them one at a time or in small groups, and restart after each change.
- Check resource usage: Is the RAM full, or is the CPU constantly at its limit?
- Restore a backup: If none of this helps, restore a backup from before the problem (see below).
- Contact support: Send us the error lines as text, tell us what you changed last, and include the time of the crash.
FiveM has a few common causes that you can check right away. You can also find an overview under FiveM: Common issues.
- License key: In
server.cfg, check thatsv_licenseKeywas copied in full and begins withcfxk_(all lowercase). See Add your own license key for instructions on adding your own key. - Resources: The server will stop starting if a resource is missing, duplicated, or missing its
fxmanifest.lua. Comment out resources inserver.cfgone at a time to find the faulty one. The name afterstartmust exactly match the folder name; see Installing resources. Resources that the system identifies as dangerous are automatically disabled; see Resource contains prohibited logic. - Database: If the log reports database connection errors (e.g. with oxmysql), go to Configuration, click Reconfigure MySQL connection string under Actions, and restart the server. Learn more under Fixing database connection issues.
- Find errors in txAdmin: The Live Console in txAdmin displays errors and warnings in real time; see txAdmin interface.
- Spikes in resource usage: Use the profiler to find resources that are slowing down the server. Enter
profiler record 100in the Live Console, followed byprofiler view. Resources above 6 ms are suspicious; see Using the profiler. - Clear the cache: As a last step, you can clear the cache; see Clear the cache.
If you haven't found a solution on Google or in Live Chat, you have 2 options. The first is to start a support chat and leave the server as it is so support can investigate it more closely.
The second option is to restore a backup or reinstall the server.
We automatically back up your game server every day. With your ZapX Pass, go to Backups on the left and restore the latest backup using Restore (the arrow icon). Your server should then work as usual again. Find the individual steps under Backups.
Start the reinstallation by clicking the Reinstall button under Actions on the overview page. This resets the entire server to its original state—all server data, such as worlds, configurations, plugins, and mods, will be deleted. Learn more under Server reset.
Unfortunately, this is the worst-case scenario. The only option left is to have support investigate the server via support chat, since this indicates a more serious problem. We'll do everything we can to resolve it as quickly as possible so you can use your service as usual again.
If your server keeps crashing because it regularly reaches its limits with your mods and players, an upgrade/downgrade is usually the long-term solution.