How to fix common FiveM console errors: a practical debug guide

The FiveM console is the starting point for any serious debug session. It accumulates error messages in real time — some critical, some silent — and ignoring those lines is the fastest path to an unstable server. Experienced owners read the console every time they bring up a new resource; beginners only look when a player complains on Discord.

This guide covers the most common errors that show up in the console of a production FiveM server: script errors, missing dependencies, invalid manifests, database failures and framework problems. For each error we show how to identify the real cause and apply a definitive fix — not just silence the message.

Estimated reading and execution time: 25 to 40 minutes, depending on how many resources you need to audit.

Prerequisites

Before starting the debug session you need access to the server and the ability to restart resources individually.

How to read a console error message

Every FiveM error line follows a predictable pattern. Learning to decode these messages saves hours of trial and error.

The general structure is: color prefix (^1 red, ^3 yellow), error type, affected resource, file and line, description. A real example:

[       script:my_script] SCRIPT ERROR: @my_script/server/main.lua:42: attempt to index a nil value (local 'player')
> CreatePlayer (@my_script/server/main.lua:42)
> handler (@my_script/server/events.lua:18)

The first line tells you the resource (my_script), the file (server/main.lua), the line (42) and the type (attempt to index a nil value). The lines starting with > are the stack trace — read top-down to follow the chain of calls that led to the error.

Inverted stack traces

FiveM lists the most recent frame first (the opposite of what Python or Node do). The line that fired the error is the first >, the function that called it comes next, and so on until the root event.

Error 1: SCRIPT ERROR — attempt to index a nil value

The most common error on FiveM servers, especially after framework updates or custom script changes.

RegisterServerEvent('myresource:save')
AddEventHandler('myresource:save', function(data)
    local player = ESX.GetPlayerFromId(source)
    player.setMoney(data.amount)
end)

RegisterServerEvent('myresource:save')
AddEventHandler('myresource:save', function(data)
    local player = ESX.GetPlayerFromId(source)
    if not player then
        print(('[myresource] Player %s not found, event ignored'):format(source))
        return
    end
    player.setMoney(data.amount)
end)

restart myresource

Error 2: Could not find dependency X for resource Y

This appears when a resource’s fxmanifest.lua declares a dependency on another resource that isn’t started or doesn’t exist on the server.

Could not find dependency oxmysql for resource es_extended.
Couldn't start resource es_extended.

ls resources/ | grep oxmysql

ensure oxmysql
ensure es_extended
ensure esx_menu_default
ensure my_scripts

Error 3: Couldn’t load resource manifest

The server found the resource folder but failed to parse fxmanifest.lua. Typically a syntax error or invalid version.

fx_version 'cerulean'
game 'gta5'

author 'your_name'
description 'resource description'
version '1.0.0'

server_scripts {
    'server/*.lua'
}

client_scripts {
    'client/*.lua'
}

Error 4: Database connection failed (oxmysql)

Database errors show up as [oxmysql] [ERROR] Connection refused or Access denied for user. Each subtype has a distinct cause.

Connection refused

MySQL isn’t accepting connections on the configured host/port.

# Confirm MySQL is running
systemctl status mysql

# Test connectivity manually
mysql -h 127.0.0.1 -u fivem -p fivem_db

If MySQL runs in a separate Docker container, the host in the connection string must be the container name, not localhost.

Access denied

Wrong credentials in server.cfg:

set mysql_connection_string "mysql://fivem:[email protected]:3306/fivem_db?charset=utf8mb4"

Special characters in the password (@, #, /) need to be URL-encoded. The password p@ss#1 becomes p%40ss%231. Encoding errors are a frequent cause of “Access denied” even with the correct password.

Pool timeout

[oxmysql] [ERROR] Pool is closed means connections were dropped (MySQL restart, server timeout). Restart the resource:

restart oxmysql

To prevent it, configure wait_timeout in MySQL to a value higher than your server’s query interval.

Error 5: Resource X failed to start

A generic startup failure. The real cause is in the lines immediately above the message.

[script:my_resource] Error loading script server/main.lua in resource my_resource: server/main.lua:1: unexpected symbol near '<'
Failed to load script server/main.lua.
[c-scripting-core] Failed to start resource my_resource

luac -p server/main.lua

Verification

After applying fixes, confirm the console is clean by running this verification sequence.

restart all

con_miniconChannels script:*

Troubleshooting

Error persists after restarting the resource

The resource may have a file cache. Stop it completely, delete the cache/ folder at the server root and bring it up again:

stop my_resource
# stop the server
rm -rf cache/
# start the server
ensure my_resource

Console fills with identical errors every second

A loop is firing the error every tick. Identify the resource from the first line of the error and stop it immediately:

stop resource_name

Investigate the code offline before bringing it back up — leaving it running in a loop can tank performance for the entire server.

Error with no stack trace

Native client errors (rendering, scaleform) often don’t carry a trace. Run profiler record 500 in the server console and open the profile at localhost:30120/profiler to see which resource was active at that moment.

Next steps

With the console clean, consider the next levels of server hardening:

• Configure log rotation via sv_logFile to preserve error history across restarts and make retroactive debugging easier
• Add continuous profiler monitoring during peak hours to detect resources that degrade silently without firing any error
• Document applied fixes in a per-resource CHANGELOG — when the problem returns six months from now, the history saves hours
• Establish a review process for fxmanifest and dependencies before pushing any new resource to production

If you’re running a FiveM server in production, a Hostini VPS with dedicated game hosting gives you isolated resources, low latency to Brazil and console access through a pre-configured txAdmin — without competing for CPU with other servers on the same node.