Module A5 · Operate, secure, and fix errors

Read your errors: console, txAdmin, and F8

Every server owner hits errors. The ones who stay calm are not smarter. They just know where to look and how to read what they find. An error is not the server being broken at random. It is the server telling you exactly what went wrong and, usually, exactly where. This lesson makes that text readable. Once it is, most problems fix themselves in minutes.

You'll learn: The three places FiveM shows errors, how to read any error down to the resource, file, and line, and why a client error and a server error never show up in the same place.
Time: ~14 minutes
You need: A running server you can restart, and a script that is currently erroring (or one you can break on purpose to practice).
You'll learn: The 3 error surfaces -> the anatomy of an error line -> why client and server errors are separate -> a calm routine for turning any error into a fix.

BEFORE YOU START

The three places errors show up

This is the single idea that unlocks debugging. FiveM has three error surfaces, and each shows a different kind of error. If you look in the wrong one, you will swear there is no error at all.

Where	How you open it	What it shows
Server console	txAdmin -> Live Console	Errors from server-side code, resources failing to start, database errors, and the boot log.
txAdmin panel	The txAdmin web page	The same Live Console, plus resource status, player logs, and crash/restart events over time.
F8 client console	Press F8 in game	Errors from client-side code: the part of a script running on a player's own PC, and NUI (interface) errors.

Keep reading the full lesson

Still ahead in this lesson

Why client and server errors are separate
How to read any error
A calm routine for any error
Where to go next