When a game server stops or misbehaves, the answer is almost always in its log. Server log shows it to you in the panel, so you don't have to connect with Remote Desktop and dig for the file.
Open the log
- Open Game installs.
- On your game's card, click Server log.
After a few seconds you see the last 400 lines of the log, scrolled to the newest. Errors are shown in red and warnings in yellow, so problems stand out.
- Refresh reads the log again.
- Copy log copies everything shown, ready to paste into a support ticket or send to your developer.
Which log does it show?
- FiveM and RedM: txAdmin's server log (
fxserver.login thetxDatafolder). - Minecraft:
logs\latest.log. - BeamMP:
Server.log. - Your own servers: the newest
.logfile in the server's folder.
The top of the box shows the file's full path and when it was last written to.
Reading it
- Start at the bottom. That's what happened most recently.
- Look for red lines just before the server stopped. In FiveM,
SCRIPT ERRORlines name the resource that failed. Restart or remove that resource in txAdmin. - If you're not sure what you're looking at, click Copy log and open a ticket. We'll take a look.
Good to know
- The panel only reads the log. It never changes or deletes it.
- If no log is found, the server probably hasn't run yet, or (for your own servers) writes its log somewhere else.