How to read your server logs and fix a crash ?
Logs and crash
When the server does not stay online, the log tells you why. This guide shows where to read it and the errors we see most often.
Where the logs are
- Panel console — live output while the process is running
- FTP — game log files (`latest.log`, `ShooterGame.log`, `console.log`, `FXServer.log`, …)
Download the file after a crash. The process is already dead, so the console tab may be empty.
Common crash causes
- Out of memory (OOM) — the process was killed. Lower slots, remove a leaky plugin, or upgrade the offer.
- Port already in use — do not set a custom IP or port. The panel assigns them. Reboot once; if it persists, open a ticket.
- Workshop timeout / missing item — a Workshop ID is invalid or the collection is private.
- Missing map — `server.cfg` or the start map points at a file that is not in `maps/`.
- Addon / plugin version — the addon was built for another game build. Remove it and reboot.
What to send in a ticket
Paste a short excerpt: the last 30–50 lines around the error, the software name, and what you changed just before the crash. Do not paste passwords, RCON secrets, or the whole 20 MB log.