Read server logs and console

Logs are the first source of truth when a server misbehaves. Reading them methodically saves a lot of time.

Cause / The problem

A server that crashes, lags or refuses connections almost always leaves a trace in its logs. But those logs are buried in noise, and you need to know where to look and what to take from them.

Solution

1. Open the live console in the panel (Console tab). You see real-time output and can type commands (depending on the game).
2. Check the log files via the Files tab or over SFTP. Common locations: logs/latest.log (Minecraft), RustDedServer.log (Rust), ShooterGame/Saved/Logs (ARK). Look inside the game folder.
3. Search for errors: open the file and look for the keywords ERROR, FATAL, Exception, crash, failed. Jump to the end of the file first, then walk backwards.
4. Note the timestamp of the incident and match it against the logs at the same moment: the cause is often there, not at the moment of the crash.
5. Read the stack trace: the first line names the error, the following lines show the call stack. The most useful block is often the first one that references your code or your plugins, not library entries.
6. Isolate the culprit: if several plugins run, disable them one by one and see whether the error disappears.
7. Share logs with support cleanly: copy the section around the error (20 lines before/after), not the whole file. State the time of the problem.

Avoid pasting logs in public that contain IPs, tokens or passwords — redact them first.