Common FiveM server errors and how to fix them

Most FiveM server problems give themselves away in a single line of output. Here you'll find the most common messages exactly as you'll see them, with the cause and how to fix it. Search by the error text (Ctrl+F).

Where to look for errors#

Read from the first error. Later errors are often just its consequences. Yellow and red lines are warnings and errors.

Could not authenticate server license key or no license key was specified#

Cause: the server doesn't have a valid license key. Either it didn't get one at all, or the key is invalid, deactivated or was copied incorrectly.

Fix: check the sv_licenseKey line in the server.cfg the server actually loads, and the key variable in the Settings tab. On the Cfx.re Portal (opens in a new window), check that the key's status is Active. Detailed steps: FiveM license key.

Couldn't find resource …#

Cause: the server doesn't know a resource with the name from ensure. The folder name doesn't match (-main, capital letters), fxmanifest.lua is one level deeper, or you uploaded the script while the server was running without the refresh command.

Fix: rename the folder exactly to the name in ensure and check that fxmanifest.lua is directly inside it. Then type refresh and ensure <NAME> in the console, or restart the server. See FiveM resources.

Could not find dependency … for resource …#

Cause: the script needs another resource (a library, a framework) that isn't on the server.

Fix: install the resource named first in the message and put its ensure above the script in server.cfg. The message Could not start dependency … means the dependency exists but crashed itself. Find its error in the console.

Couldn't start resource …#

Cause: the resource exists but didn't start. The real reason is in the lines right above this message: a missing dependency, an unmet condition (OneSync, game build, server version) or a license error for a paid script.

Fix: fix the cause from the previous lines and start the resource again with ensure <NAME>.

SCRIPT ERROR: @…/….lua:…: …#

Cause: an error in the script's code. The message includes the resource, the file, the line number and a description, for example attempt to index a nil value. Most often it's the wrong framework setting in config.lua, a missing database table, or an older script version than the framework expects.

Fix: check config.lua (the right framework), import the script's SQL and update both the script and the framework. If the error appeared after you edited a file, revert the edit.

You lack the required entitlement to use …#

Cause: a paid script protected by Asset Escrow was bought on a different Cfx.re account than the one the server's license key belongs to.

Fix: use a license key from the same account you bought the script with, or transfer the script on the Cfx.re Portal. Then restart the server.

Failed to verify protected resource …#

Cause: the files of an encrypted script were damaged in transfer or are missing, most often the .fxap file.

Fix: upload the whole resource again, including the .fxap file and hidden files (those starting with a dot).

Unable to establish a connection to the database (…)!#

Cause: oxmysql couldn't connect to the database. The code in parentheses tells you why:

Fix: correct set mysql_connection_string in server.cfg following Database for FiveM. Once it's fixed, the console shows Database server connection established!.

The server isn't in the server list or shows as “private”#

Cause: an active sv_master1 "" line, missing sets sv_projectName or sets sv_projectDesc, the server isn't reachable from outside, or it's only been a short time since startup.

Fix:

1. Check that you can connect to the server directly: in the game, press F8 and type connect <IP_ADDRESS>:<PORT> (address from the Network tab).
2. Comment out the sv_master1 "" line with #.
3. Add sets sv_projectName "…" and sets sv_projectDesc "…".
4. Wait up to 8 minutes after startup.

You can also check the server with the CFX Resolver tool. Details in the server.cfg guide.

Connection rejected by server: Client/Server game build revision mismatch#

Cause: the player's game and the server have different game build revisions. Typically shortly after a GTA V or FiveM update.

Fix: update the server artifacts (guide). The player can switch the Update Channel in the FiveM client (gear icon › Game) to the channel that matches the server. Often you just need to wait until the update reaches everyone.

Players get stuck on the loading screen when connecting#

Cause:

• an error in the multicharacter script or the database (the character doesn't load),
• a large number of models to download (cars, clothing, maps) or slow downloading,
• the first connection after a change to sv_enforceGameBuild (DLC is downloading),
• a loading screen script that never shuts down.

Fix: look in the server console and in the player's F8 console to see where loading stopped. With a framework, check the database connection. On Qbox with a custom multicharacter, set setr loadscreen:externalShutdown false. Try temporarily turning off large car and clothing packs and see whether players get further.

The connection ends with a timeout (timed out) or connection refused#

Cause:

• the port in endpoint_add_tcp and endpoint_add_udp doesn't match the port in the Network tab (common after deploying a txAdmin recipe, which writes the default 30120),
• the server didn't fully start (didn't load server.cfg, no resources are running),
• the server is overloaded (CPU or RAM at the limit) or is crashing right now,
• on your own VPS, a firewall is blocking the port.

Fix: compare the port in server.cfg with the Connection address line. In the console, check that the resources started (Started resource …). Check RAM and CPU usage below the console. On a VPS, allow the port for both TCP and UDP in the firewall (firewall).

Server artifact version is outdated (EOS or EOL warning)#

Cause: the server is running an old FXServer build. Artifacts older than 3 months can't be joined from the server list.

Fix: update the artifacts to the Recommended channel (guide).

Native … is not supported, Error parsing script or Failed to load script#

Cause: the script or framework uses functions your server version doesn't know.

Fix: update the artifacts to Recommended. If that's not enough, to Latest.

txAdmin reports a server crash or freeze and restarts it#

Cause: the server crashed or stopped responding. txAdmin starts it again on its own. Most often it's a script error (an infinite loop, a large database query), not enough RAM, or a newly installed resource.

Fix:

1. In txAdmin, open Live Console and System › Console Log and find the last errors before the crash.
2. Check RAM usage below the console in the customer area. If it stays at the limit, remove resources or move to a bigger plan (Change plan tab).
3. If the crashes started after installing or updating a script, turn the script off (comment out its ensure) and see whether the crashes stop.

## [txAdmin CFG validator]: … in server.cfg#

Cause: txAdmin commented out a line that isn't allowed in server.cfg and wrote the reason after the colon. Most often:

• onesync MUST only be set in the txAdmin settings page. – with txAdmin, OneSync is set in Settings › FXServer.
• you MUST NOT start/stop/ensure txadmin resources. – delete the ensure monitor line (txAdmin starts on its own).
• the … port … is dedicated for txAdmin and CAN NOT be used for FXServer. – endpoint_add_* has the txAdmin port. Put the game port from the Network tab there.

Fix: fix the line according to the reason and delete the commented-out line.

Your config file does not specify a valid endpoints for FXServer to use.#

Cause: server.cfg is missing the endpoint_add_tcp and endpoint_add_udp lines, or they have a different port.

Fix: add both lines with the port from the Network tab at the top of server.cfg:

endpoint_add_tcp "0.0.0.0:<PORT>"
endpoint_add_udp "0.0.0.0:<PORT>"

Replace <PORT> with the number after the colon in the Connection address line.

You can't set more than 48 slots#

Cause: more than 48 players requires an Element Club Argentum subscription on the Cfx.re Portal. The subscription alone doesn't raise the slot count.

Fix: after buying the subscription, increase sv_maxclients in server.cfg (on a server without txAdmin, possibly the slots variable in the Settings tab) and restart the server. More than 64 slots requires OneSync on.

server thread hitch warning: timer interval of … milliseconds#

Cause: one server tick took longer than 150 ms and the server “hitched”. This is normal at startup and while resources load. Frequent messages while running mean some script is doing heavy work all at once (large database queries, loops over all players or entities). Similar messages exist for the network (network thread) and sync (sync thread) threads.

Fix: find the culprit with the profiler: in the server console, profiler record 500, and when it's done, profiler saveJSON profil.json. Download the file in the Files tab and open it in Chrome's developer tools (Performance tab). Then optimize, update or replace the script. Checking CPU usage below the console also helps.

Warning: sending large event … (… bytes). This may cause performance issues. Consider using latent events instead.#

Cause: a script sends a large amount of data to players at once in a single event. This can cause lag and disconnects for players.

Fix: find out from the event name which script it is and report it to the author. Large data should be sent with latent events, which send it in chunks.

Could not contact the server browser#

Cause: the server can't reach the Cfx.re services that run the server list. An occasional message is harmless; if it keeps repeating, the server will drop out of the list.

Fix: restart the server. If the message keeps coming back, contact us. On your own VPS, check that your firewall or DDoS protection lets through the Cfx.re addresses from static.cfx.re/ips.txt (opens in a new window).

Can't restart a stopped resource.#

Cause: you used restart on a resource that isn't running.

Fix: use ensure <NAME>. It starts a resource that isn't running and restarts one that is.

Warning Resource … does not specify an fx_version in fxmanifest.lua.#

Cause: an older script doesn't have an fx_version line in its manifest.

Fix: add fx_version 'cerulean' and game 'gta5' at the top of fxmanifest.lua. A script with __resource.lua instead of fxmanifest.lua is very old; look for a newer version.

A car or model doesn't load in the game#

Cause: the model name in the command or script doesn't match the name in vehicles.meta, the resource with the model isn't running, the data_file lines are missing from the manifest, or the model requires a higher game build.

Fix: check in the console that the resource with the model is running (Started resource …). Find the exact model name (modelName) in vehicles.meta and use it for spawning. Check that the manifest contains data_file for vehicles.meta (FiveM resources).

If it still doesn't work: when to contact support#

Contact us (contacts) when:

• the console in the customer area doesn't load or the Start and Restart buttons don't respond,
• the server doesn't start even with the basic txAdmin recipe and no extra scripts,
• players can't reach the port even though server.cfg matches the Network tab,
• you need SFTP access for large files.

Send us the service name or ID, when the problem happened, the exact error text (copied from the console) and what you changed last. Never send your license key or database password.

Further reading#

• FiveM: Server Issues (opens in a new window)
• FiveM: Resource FAQ (opens in a new window)
• FiveM: Server Commands (opens in a new window)