Logs / FiveM
Share a FiveM log and find script errors
Paste the console of your FiveM server or the txAdmin log and share the link with your dev team. The analysis assigns every SCRIPT ERROR to the resource it comes from and shows resources that won't start or are missing a dependency – for ESX, QBCore and custom scripts.
Where do I find the log?
txAdmin: Live console- In txAdmin under “Live Console” you see the running output. Select it, copy it, paste it in above.
txData/<profile>/logs/- txAdmin saves the server output as fxserver.log (with older versions next to it). You can drag the file straight into the field.
Console in the panel- Without txAdmin, everything is in the panel console. At Nexthosting, you share it with “Share log” in one click.
F8 console in game- You can see client-side errors in game with F8. The file for them is at %localappdata%/FiveM/FiveM.app/logs/.
What the analysis detects for FiveM
- SCRIPT ERROR with file and line, assigned to the resource
- Resources that won't start (“Couldn't start resource”)
- Missing dependencies (“Could not find dependency … for resource …”)
- Invalid or missing license key (sv_licenseKey)
- Port in use, crashes and out-of-memory errors
Common FiveM errors and how to fix them
Questions about FiveM logs
- How do I share a FiveM log?
- Copy the output from the txAdmin live console or open fxserver.log, paste it in above and save. The link is then in your clipboard and can go straight into a ticket or your Discord.
- Is my license key shared?
- No. sv_licenseKey, RCON passwords, Discord webhooks, API keys and IP addresses are masked before saving.
- What does “SCRIPT ERROR: @resource/…” mean?
- The @ stands for the resource, followed by the file and line where the script stopped. The message after it says what went wrong – usually a value is missing (nil) because a dependency isn't loaded or the database wasn't ready yet.
- Does this work with RedM too?
- Yes. RedM uses the same server (FXServer) and the same messages.